Le 04/10/2010 18:31, Stefan Roese a écrit :
On Monday 04 October 2010 17:24:09 Albert ARIBAUD wrote:
Excellent work! Congratulations!
Thanks, but I'd suggest to wait for congrats until ethernet works -- tough I've got a clue, I think; it may have to do with the core activating its caches and the driver doing DMA. :)
Yes. Very likely a aching problem and not an relocation issue. With D-cache enabled some IO drivers might have some problems. This will also be a problem with for example USB support.
... and that is a new proof that assumption is the mother of all screw-ups.
It was not a question of caching; it was a question of trashing the address of gd passed from board_init_f() through relocate_code() to board_init_r(), and all code before the marvell ethernet driver not relying on gd anought to break.
Patches to follow right away as an RFC.
Amicalement,