linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Holzt <kju@fqdn.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Bugs in 2.4.0-ac2 in ppc
Date: Fri, 5 Jan 2001 21:06:28 +0100	[thread overview]
Message-ID: <20010105210627.D1095@fqdn.org> (raw)


While trying to compile LinuxPPC 2.4.0-ac2 for an embedded PPC i found
three problems:

 - function set_pgdir disappeared somewhere late in the 2.4.0test
   series. I had to copy the source from an older kernel to get the
   kernel to compile.


 - In ac2 the following source in asm-ppc/mmu_context.h is removed:

   #ifdef CONFIG_8xx
   extern inline void mmu_context_overflow(void)
   {
       atomic_set(&next_mmu_context, -1);
   }
   #endif

   When compiling on for a 8xx this leads to errors due to nonexisting
   function mmu_context_overflow.


 - And third the worst problem: Since one of the latest test series
   kernels i'm unable to use modules:

   For all modules i try i get unresolved symbols - for trivial functions:

   bash-2.03# insmod ./loop.o
   ./loop.o: unresolved symbol memset
   ./loop.o: unresolved symbol int_control_R58a1efa3
   ./loop.o: unresolved symbol __copy_tofrom_user_Re410a3dd
   ./loop.o: unresolved symbol memcpy
   ./loop.o: unresolved symbol strncpy_R328a05f1


As i'm no kernel-developer, i'm not subscribed to this list. So if
replying, please make a courtesy-copy to me privately. I really would like
to see these problems fixed. Thanks.


--
Greetings
Michael

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-01-05 20:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 20:06 Michael Holzt [this message]
2001-01-06 17:45 ` Bugs in 2.4.0-ac2 in ppc Tom Rini
2001-01-06 23:09 ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010105210627.D1095@fqdn.org \
    --to=kju@fqdn.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).