From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: zImage not supported for 2.2.20?
Date: 28 Dec 2001 10:36:44 -0800 [thread overview]
Message-ID: <a0ie3s$s71$1@cesium.transmeta.com> (raw)
In-Reply-To: <4.3.2.7.2.20011228124704.00abba70@192.168.124.1> <20011228121228.GA9920@emma1.emma.line.org> <4.3.2.7.2.20011228124704.00abba70@192.168.124.1> <4.3.2.7.2.20011228173505.00aa3da0@192.168.124.1>
Followup to: <4.3.2.7.2.20011228173505.00aa3da0@192.168.124.1>
By author: Roy Hills <linux-kernel-l@nta-monitor.com>
In newsgroup: linux.dev.kernel
>
> Unfortunately, I need to use zImage on my Tecra. I know that zImage is
> old, and I've heard that support for it will eventually be withdrawn, but I
> don't really have much alternative right now unless there is a patch which
> works around the Tecra's buggy A20 handling.
>
I believe this is now a myth. Toshiba's weird A20 problems should
have been worked around for a long, long time; and I believe the
latest set of changes in 2.4 should make that thouroughly complete.
In fact, if your bzImages don't work either, I suspect your problems
isn't at all one of zImage vs bzImage but that there is a separate bug
that's biting you independently.
> Does anyone know the status of zImage format in modern kernels?
> Is it _supposed_ to be supported under 2.2.recent? How about 2.4.recent?
>
> I guess that, if zImage is supposed to be supported, then I have a
> genuine bug. However, if zImage support has officially been
> dropped, then it's a different matter - in this case, the only bug
> would be that the Makefile should issue a sensible message when you
> try to "make zImage" rather than producing a kernel that won't work.
zImage format will probably be removed in the 2.5 series. It's
virtually impossible to fit a practical 2.4 kernel within the zImage
size limits.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-12-28 18:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 10:18 zImage not supported for 2.2.20? Roy Hills
2001-12-28 12:12 ` Matthias Andree
2001-12-28 12:26 ` bug reports for CML2? rpjday
2001-12-28 12:39 ` André Dahlqvist
2001-12-28 13:11 ` zImage not supported for 2.2.20? Roy Hills
2001-12-28 13:35 ` Matthias Andree
2001-12-28 14:32 ` Petri Kaukasoina
2001-12-28 20:13 ` Wolfgang Erig
2001-12-29 2:23 ` H. Peter Anvin
2002-01-01 15:16 ` Wolfgang Erig
2001-12-28 17:44 ` Roy Hills
2001-12-28 18:19 ` Alan Cox
2001-12-28 20:36 ` Petri Kaukasoina
2001-12-29 2:25 ` H. Peter Anvin
2001-12-29 2:58 ` Alan Cox
2001-12-29 11:01 ` Petri Kaukasoina
2001-12-28 18:36 ` H. Peter Anvin [this message]
2001-12-28 19:04 ` Alan Cox
2001-12-28 18:42 ` H. Peter Anvin
2001-12-31 9:12 ` Roy Hills
2002-01-02 0:54 ` H. Peter Anvin
2001-12-31 12:16 ` Roy Hills
2001-12-31 13:06 ` Petri Kaukasoina
-- strict thread matches above, loose matches on Subject: below --
2001-12-28 21:06 Andries.Brouwer
2001-12-28 21:55 ` H. Peter Anvin
2001-12-28 23:57 ` Alan Cox
2001-12-29 0:01 Andries.Brouwer
2001-12-29 0:17 ` H. Peter Anvin
2001-12-29 0:20 ` 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='a0ie3s$s71$1@cesium.transmeta.com' \
--to=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