[U-Boot-Users] Big Files?

Wolfgang,
I have a display driver that I would like to add to the 8610HPCD board port. The driver itself is pretty small (about 30K of source), but there is a logo bitmap file that can be used to display on the display as well. That file alone is about 160K even though it is a smallish bitmap (340 x 128 x 4bpp).
How would you like to handle this situation?
I could post the basic driver, code, of course. Should I do that, and throw it all into the -mpc86xx custodian tree along with the bitmap file? Or would you prefer to see a URL to some HTTP: site with it? Or an encoded gzip file on list?
Thanks, jdl

Dear Jon,
in message 1193692082.1462.28.camel@ld0161-tx32 you wrote:
I have a display driver that I would like to add to the 8610HPCD board port. The driver itself is pretty small (about 30K of source), but there is a logo bitmap file that can be used to display on the display as well. That file alone is about 160K even though it is a smallish bitmap (340 x 128 x 4bpp).
340x128x4 = 174,080 bit = 21,760 byte = 21.25 KiB. Where is the other 138 KiB of data coming from?
How would you like to handle this situation?
Like any other patch...
[I have to admit that I am not really happy to have such big image data in the public repo, but I probably have to keep my mouth shut because I did not notice when Stefan Roese sneaked in much bigger bitmap file :-( ]
I could post the basic driver, code, of course. Should I do that, and throw it all into the -mpc86xx custodian tree along with the bitmap file? Or would you prefer to see a URL to some HTTP: site with it? Or an encoded gzip file on list?
Submit the code as regular patch and the bit map file as part 2, gzipped.
Best regards,
Wolfgang Denk

Wolfgang Denk wrote:
Dear Jon,
in message 1193692082.1462.28.camel@ld0161-tx32 you wrote:
I have a display driver that I would like to add to the 8610HPCD board port. The driver itself is pretty small (about 30K of source), but there is a logo bitmap file that can be used to display on the display as well. That file alone is about 160K even though it is a smallish bitmap (340 x 128 x 4bpp).
340x128x4 = 174,080 bit = 21,760 byte = 21.25 KiB. Where is the other 138 KiB of data coming from?
unsigned int FSL_Logo_BMP[] = { 0x424d765c, 0x00000000,0x00007600,0x00002800,0x00006c01,0x00008000,0x00000100,0x04000000, 0x0000005c,0x0000130b,0x0000130b,0x00001000,0x00000000,0x00000402,0x04000d91, 0xbc000b51,0x67001536,0x9a000f2a,0x4b005050,0x50009090,0x90000c70,0x92002e2f,
Submit the code as regular patch and the bit map file as part 2, gzipped.
Sounds good!
Thanks, jdl
participants (2)
-
Jon Loeliger
-
Wolfgang Denk