Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261369AbVECQ7e (ORCPT ); Tue, 3 May 2005 12:59:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261378AbVECQ7e (ORCPT ); Tue, 3 May 2005 12:59:34 -0400 Received: from fire.osdl.org ([65.172.181.4]:2485 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261369AbVECQ7a (ORCPT ); Tue, 3 May 2005 12:59:30 -0400 Date: Tue, 3 May 2005 09:59:13 -0700 From: "Randy.Dunlap" To: Wakko Warner Cc: linux-kernel@vger.kernel.org Subject: Re: zImage on 2.6? Message-Id: <20050503095913.1c9b62ba.rddunlap@osdl.org> In-Reply-To: <20050503163343.GC11937@animx.eu.org> References: <20050503012951.GA10459@animx.eu.org> <20050502193503.20e6ac6e.rddunlap@osdl.org> <20050503104503.GA11123@animx.eu.org> <20050503072626.3a3c7349.rddunlap@osdl.org> <20050503163343.GC11937@animx.eu.org> Organization: OSDL X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: SvC&!/v_Hr`MvpQ*|}uez16KH[#EmO2Tn~(r-y+&Jb}?Zhn}c:Eee&zq`cMb_[5`tT(22ms (.P84,bq_GBdk@Kgplnrbj;Y`9IF`Q4;Iys|#3\?*[:ixU(UR.7qJT665DxUP%K}kC0j5,UI+"y-Sw mn?l6JGvyI^f~2sSJ8vd7s[/CDY]apD`a;s1Wf)K[,.|-yOLmBl0 On Tue, 3 May 2005 06:45:03 -0400 Wakko Warner wrote: | > | > It's supported in arch/i386/Makefile (and some others). | > | > For i386, you'll need to disable enough (lots of) options to make the | > | > resulting output file small enough... | > | | > | The resultant bzImage is ~760kb. I compiled out everything I could, only | > | ram disk/initrd, and ext2 are compiled in. | > | | > | If you'd like to see the .config, I'll send it up. | > | > Are you saying that zImage still fails (image is too large?) ? | | Yes, I do recall it says "System is 724k". zImage failes. bzImage says | 724k as well and succeeds. The image size needs to be <= 0x7f000 (520192 bytes, 508 KB). (No, I don't know why, just that this is what is being enforced.) Just cut more out of the kernel image... | > I built one, but I wouldn't want to boot it. :) | > It looks like you would need to put almost everything into | > an initrd to make it usable. | | That was the idea in this. Once I get my stuff the way I want it, I'll | probably move on to using initramfs. My initrd is using ramdisk, my / is on | tmpfs and is populated by .tgz files on other media (The boot time is | generally short lived by design anyway) --- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/