On Saturday 16 February 2008, Wolfgang Denk wrote: > 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.
right ... it isnt a big deal for us on Blackfin as people tend to have a ton of RAM compared to many boards, so the decompression areas need not overlap. > Unfortunaltely I don't know of an intelligent way to handle this > situation. I think I remember that RMK claims that the ARM kernel > uncompressor was really clever in this respect, but never found time > to check it. it'd be better moved to the actual decompression routines rather than top of bootm. and either check it before decompressing each chunk, or have a good heuristic to estimate things ... -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- 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
