On Sat 16 Feb 2008 18:06, Wolfgang Denk pondered: > In message <[EMAIL PROTECTED]> you wrote: > > we semi-frequently get users who try to boot an image on top of itself > and > > when when things crash, dont realize why. i put together this quick > little > > warning, but i'm guessing that Wolfgang's answer is "don't bloat the > code for > > stupid people" ... > > Indeed I reject the patch as is, but not because I think it would be > not useful, but rather because it is IMHO not correct. > > The thing is that images *may* overlap, at least a bit. When the de- > compressor is running, it starts from the beginning of the compressed > image and progrsses towards the end. The already preocessed parts of > the image are not neede dany longer - if they later get overwritten > by umcompressed code this does no hard. Problems arise only if the > write pointer catches up with the read pointer.
Hmm... I always thought that when decompressing a uImage, that the entry point was stored in the header, (at the beginning of the file) and was read after the decompression took place - is that wrong? -Robin ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
