In message 6.1.1.1.0.20050414175534.01eb8780@ptg1.spd.analog.com you wrote:
Sorry - I was not trying to make a bug report - just ask a quick question if anyone else had seen any issues with large (5.5Meg binary images) being turned into large (3Meg) gzip files.
Not on any of the platforms I have access to.
## Booting image at 20100000 ... Image Name: Blackfin Audio Created: 2005-04-12 19:53:31 UTC Image Type: Blackfin Linux Kernel Image (gzip compressed) Data Size: 2973852 Bytes = 2.8 MB Load Address: 00001000 Entry Point: 00001000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting Kernel at = 1000 Linux version 2.6.8.1 (dskocyp@linux) (gcc version 3.4.1) #2 Tue Apr 12 14:40:24 EDT 2005 Blackfin support (C) 2004 Analog Devices, Inc.
...
VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 40k freed (0xd6000 - 0xdf000) EXT2-fs error (device mtdblock0): ext2_check_page: bad entry in directory #173: rec_len is too small for name_len - offset6 Warning: unable to open an initial console. EXT2-fs error (device mtdblock0): ext2_check_page: bad entry in directory #174: unaligned directory entry - offset=0, inod1 Kernel panic: Attempted to kill init!
I don't see any U-Boot related problems in thi sreport.
Best regards,
Wolfgang Denk