* Thibaut Girka <t...@sitedethib.com> [2010-08-31 23:43]: > If you're talking about the discussion in #503292, then yes, s3c24xx was > decided.
Ok, that's fine then. > There is already basic (really basic, no display or even µSD) support in > mainline kernel, and the name is "GTA02". Ok. > > Why do you need to compress the kernel? It should be a zImage or > > LZMA-image already anywhere. > > Yeah, I know, that's a bit tricky (I commented it on the d-i target, but > I haven't sent it yet). > So, U-Boot have an image format called multi-file images. > But there is only one header for the whole image, and so, only one > compression method. > This compression method is used both to uncompress the kernel and as the > compression type of the initrd image. > If I don't compress the kernel and say "-C gzip", U-Boot will try to > uncompress the kernel, and will obviously fail (since the kernel is > executable and uncompress itself). > If I specify "-C none", it'll run the kernel just fine, but will fail to > tell the kernel that the initrd image is gzip-compressed... > So, the only way is to re-compress the kernel... We use multi-file images on the HP mv2120 and -C none works fine with a regular kernel/compressed initrd combination. Does u-boot actually need to tell the kernel that the ramdisk is compressed? AFAIK the kernel figures this out itself... but I don't have a Freerunner so I cannot verify this myself. Maybe you can test again if -C none works, but it it doesn't then I guess your patch is fine (but maybe with a comment). > > Will this actually boot on any Freerunner machines without the -p > > option you proposed in #584166? > > If you're lucky. > Indeed, the chances aren't negligible, maybe this bug will wait for > #584166. Ok, fine with me. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100914213858.gl5...@jirafa.cyrius.com
