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:42:17 -0800 [thread overview]
Message-ID: <a0iee9$s90$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.
>
Oh, by the way, the "I need to use zImage on my Tecra" thing is making
it work by the use of voodoo. It's rather unfortunate it worked on
some systems -- it's going to fail randomly on you anyway; it's just a
matter of which way the timings and cache items get jerked around.
I have asked Alan for more details on the workaround, but perhaps the
thing to do is to backport the latest 2.4 A20 code back to 2.2 and see
if that solves the *real* problem, so bzImage works.
I don't think there is any reason to believe zImage doesn't work
unless bzImage works on your system.
-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:42 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
2001-12-28 19:04 ` Alan Cox
2001-12-28 18:42 ` H. Peter Anvin [this message]
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='a0iee9$s90$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