From: Thomas Gleixner <tglx@linutronix.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: x86: removing zImage support?
Date: Wed, 11 Mar 2009 12:03:24 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0903111201430.29264@localhost.localdomain> (raw)
In-Reply-To: <20090311102439.GA32512@elte.hu>
On Wed, 11 Mar 2009, Ingo Molnar wrote:
> * H. Peter Anvin <hpa@zytor.com> wrote:
>
> > I'm thinking again about removing zImage support. An
> > "allnoconfig" kernel (with CONFIG_EMBEDDED=y to expose
> > additional knobs, and CONFIG_BINFMT_ELF=y so it can do
> > anything at all) is currently 487K on i386 -- very close to
> > the upper limit of 512K for zImage.
> >
> > Are there *any* residual users of this, or should I just push
> > a patch to remove it once and for all?
>
> Havent seen any zImage bugreport for years, so go for it. In the
> unlikely case of someone still relying on it and having a good
> use case we'll get a bugreport and can consider putting it back
> in.
I haven't seen any zImage for years in the embedded space either.
Go for it.
Thanks,
tglx
next prev parent reply other threads:[~2009-03-11 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 0:20 H. Peter Anvin
2009-03-11 1:15 ` Andi Kleen
2009-03-11 1:47 ` H. Peter Anvin
2009-03-11 10:24 ` Ingo Molnar
2009-03-11 11:03 ` Thomas Gleixner [this message]
2009-03-11 14:14 ` Woody Suwalski
2009-03-11 17:03 ` H. Peter Anvin
2009-03-11 17:39 ` Ian Campbell
2009-03-11 18:02 ` H. Peter Anvin
2009-03-11 18:06 ` [tip:x86/setup] x86: remove zImage support H. Peter Anvin
2009-03-12 17:45 ` Paul Bolle
2009-03-12 19:25 ` H. Peter Anvin
2009-03-12 19:28 ` H. Peter Anvin
2009-03-12 19:57 ` [tip:x86/setup] x86: remove additional vestiges of the zImage/bzImage split H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.0903111201430.29264@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome