Hi Jesse,
> 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?
Yes, it's still 0x00218000.
> 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.
Ok.
> If there
> is a driver that expects its registers to be in the power-on reset
> state, it may not work.
I don't know, but I think that the problem should arise when the kernel
loads the driver (I can't get any linux message). Please, correct me if
I'm wrong.
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/
|