[EMAIL PROTECTED] wrote:
>
> Something else strange, and I'm not sure if I'm chasing two separate
> problems now. I had a kernel that would boot about 50% of the time, and
> the other 50% it would hang. I never really investigated this much to
> figure out what was going on. I am now modifying the kernel memory maps
> 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 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?
>
> unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
On kernels we've run on the EBSA-285 we actually added in lines of code
at the very beginning of head-armv.S. When we were using Angel to
download our code this was necessary as Angel was enabling the MMU.
Basically we just added lines to the start of head-armv.S to disable
IRQ/FIQs and the MMU and this solved the problems we were having on
bootup. I may be mixing problems up but I remember that someone
recently had a problem booting off of a Windriver boot loader - I
suspect the problem may be similar...
-Jon
--
Quackware, Inc. www.quackware.com
1875 Charleston Road, Mountain View, CA 94043
Ph (650) 316 3891 Cell (412) 298 5363
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
