From: "Bruce Ashfield" <bruce.ashfield@windriver.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Can we get rid of zImage this time?
Date: Mon, 11 Jun 2007 22:20:19 -0400 [thread overview]
Message-ID: <3bd6b93c0706111920p36d866a6m18915696fd386473@mail.gmail.com> (raw)
In-Reply-To: <466DE04C.4020303@zytor.com>
On 6/11/07, H. Peter Anvin <hpa@zytor.com> wrote:
> I brought this up a few years ago, and had it shot down, because of a
> few poorly substantiated claims of zImage-only machines; those claims
> really need to be debugged since they might indicate A20-related failures.
These beasts are still alive and kicking. I boot a handful of
arm and ppc boards on a frequent basis that are zImage
only. The kicker is I don't have the bootloader source for
most of them, so changing to a different image format is
tough at best.
Not a vote one way or the other, just some observations
from my day to day.
Bruce
>
> Anyway...
>
> Can we please kill zImage? In addition to be completely useless for
> modern kernels, it causes unnecessary complexity in boot loaders.
>
> -hpa
> -
> 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/
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
next prev parent reply other threads:[~2007-06-12 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 23:52 H. Peter Anvin
2007-06-12 2:20 ` Bruce Ashfield [this message]
2007-06-12 6:14 ` H. Peter Anvin
2007-06-12 12:57 ` Bruce Ashfield
2007-06-12 21:59 ` Krzysztof Halasa
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=3bd6b93c0706111920p36d866a6m18915696fd386473@mail.gmail.com \
--to=bruce.ashfield@windriver.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®