[EMAIL PROTECTED] writes:
> for the different processors we are running. What I'm really doing is
> changing the memory map setup code so it can figure out it's memory map
> while it's executing rather than at compile time. This code compiles
> fine, but the kernel will not run at all. This is the kernel I traced
> down to not working once the MMU is enabled (i.e. I never make it past
> the MMU being enabled in head-armv.S).
I've done a major overhaul of the memory initialisation today in 2.3.18,
so it'll probably knock your changes out.
> I tried something someone else suggested, and that was to map in the
> page the kernel is executing when the MMU is enabled, but this didn't
> help. I'm running out of ideas. Anyone know where I should be
> looking?
It's very unlikely that this is a kernel problem. The kernel memory
initialisation code works reliably on a lot of NetWinders, RiscPCs,
EBSA285's and EBSA110's. It's well tested. I'd suggest checking out
either the way you're calling the kernel, or the hardware itself.
(btw, make sure that the caches are flushed before you enter the kernel
from your loader. This is an absolute MUST)!
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
