I'm not sure what this could be. Where does 2.6 expect to be placed
in physical memory? Is it still 0x218000 like 2.4 or did they
change that?
What happens when using the bootload application is that it will
disable the MMU, disable DMA, disable the ethernet, move the bin
file to the specified physical address, and jump into it. If there
is a driver that expects its registers to be in the power-on reset
state, it may not work.
There is no restriction on kernel size. The only restriction is
there needs to be enough free memory to load the kernel in
userspace. On a 32MB board running nothing other than the kernel and
a shell, this usually means it needs to be 28MB or less.
//Jesse Off
--- In Marco Pracucci <>
wrote:
>
> Hi
>
> > Boot a compressed kernel image:
> > $ bunzip -c vmlinux.bin.bz2 | bootload -
>
> I have been able to boot an image of linux kernel 2.4.26, but I'm
not
> able to boot a kernel 2.6.18. The "linux boot loader" hungs after
the
> following messages:
> [...]
> valid: 000e6000:0
> valid: 000e7000:0
>
> Is there any restriction to the size of the kernel image (kernel
2.6 is
> bigger than 2.4)?
> Have you any idea / suggestion?
>
> Thanks,
> Marco Pracucci
>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|