Dear Simon, In message <capnjgz1x+ant6x4c0d6zcob3vvvvm1abudkrcgkxg122f8x...@mail.gmail.com> you wrote: > > > I don't think this is as it should be. Any frame buffer that actually > > gets used as such should be located in the memory area specifically > > allocated for this purpose using lcd_setmem(). This is especially > > important when you load a splash screen image and intend to display it > > flicker-free when booting an OS. If you use malloc() or memalign(), > > it will be memory in the malloc arena, which gets overwritten when an > > OS boots, resulting in a corrupted display. > > > > Note: I added Anatolij, our video custodian to the Cc: list. > > OK, well in that case we should deprecate this business of using a > separate memory buffer as a frame buffer, and make people uncompress > the BMP to the normal frame buffer. It would simplify a few things and > I doubt there would be a speed penalty (or at least it could be > corrected by decompressing directly to the frame buffer).
Agreed - thanks! Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de All he had was nothing, but that was something, and now it had been taken away. - Terry Pratchett, _Sourcery_ _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
