26 Oct
2007
26 Oct
'07
4:41 p.m.
From: Timur Tabi [mailto:timur@freescale.com] Just to be clear, backing out f82b3b6304b620ef7e28bfaa1ea887a2ad2fa325 and e9514751cfa5cce61ea699fa0d3eb37898a5eeb5 makes malloc work, but breaks the command line?
I think both will work, because one of those commits sets gd->reloc_off to 0 and that is what breaks everything. I need try ry it again to make sure.
I had to disable CONFIG_RELOC_FIXUP_WORKS in include/common.h for my CPU to get it to work.
Does disabling that make everything work?
Yes, as far as I can tell. I could successfully download and run a kernel uImage.