On Aug 14, 2006, at 4:10 AM, Benjamin Heyne wrote: > And so it came to pass, that on Fri, 11 Aug 2006 23:37:25 -0500 > Milton Miller <miltonm at bga.com> wrote as thus: > >> On Mon Aug 7 2006 04:46:43 AM CDT, Benjamin Heyne wrote: >>> Peter Korsgaard <jacmet at sunsite.dk> wrote as thus: >>>>>>>>> "David" == David H Lynch <dhlii at dlasys.net> >>>> David> Have you tried 2.6.18.x to see if your stuff works with >>>> it >>> >>> Well, unfortunately I am still getting the inflate error >>> as soon as the image grows >2MB (about). Have you tried with >>> images of this size? If the image is smaller, everything works >>> fine... >> >> I think your kernel is growing larger than >> 4MB, which is the link address of the zImage. > > Well - That's exactly the case. But looking into misc-embedded.c, I > noticed > that the load address for gunzip is fixed to 0x400000...shouldn't this > be dependent on CONFIG_BOOT_LOAD_BOOL and CONFIG_BOOT_LOAD? > > I've changed the line to > > #ifdef CONFIG_BOOT_LOAD_BOOL > gunzip(0, CONFIG_BOOT_LOAD, zimage_start, &zimage_size); > #else > gunzip(0, 0x400000, zimage_start, &zimage_size); > #endif > > and now it seems to work fine for big images (if CONFIG_BOOT_LOAD > is set large enough of course...) - which wasn't the case before.
It shouldn't depend on CONFIG_BOOT_LOAD_BOOL. CONFIG_BOOT_LOAD is set all the time (the question is dependent on _BOOL not the variable and the default is used). milton
