From: Roy Hills <linux-kernel-l@nta-monitor.com>
To: Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>,
linux-kernel@vger.kernel.org
Subject: Re: zImage not supported for 2.2.20?
Date: Fri, 28 Dec 2001 17:44:10 +0000 [thread overview]
Message-ID: <4.3.2.7.2.20011228173505.00aa3da0@192.168.124.1> (raw)
In-Reply-To: <20011228163250.A31791@elektroni.ee.tut.fi>
In-Reply-To: <4.3.2.7.2.20011228124704.00abba70@192.168.124.1> <4.3.2.7.2.20011228101818.00aaa2c0@192.168.124.1> <4.3.2.7.2.20011228101818.00aaa2c0@192.168.124.1> <20011228121228.GA9920@emma1.emma.line.org> <4.3.2.7.2.20011228124704.00abba70@192.168.124.1>
At 16:32 28/12/01 +0200, Petri Kaukasoina wrote:
>Hi, I used to make zImages, but for no specific reason. The last working
>version was 2.2.20pre3. 2.2.20pre5 gave Out of memory -- System halted. I
>reported it a few months ago:
>http://www.uwsg.iu.edu/hypermail/linux/kernel/0108.2/0363.html
>
>This was the only change then that looks like it:
>
>o Add support for the 2.4 boot extensions to 2.2 (H Peter Anvin)
So it looks like this is a real issue, and it's been tracked down to somewhere
between 2.2.20pre3 and 2.2.20pre5.
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.
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.
Regards,
Roy Hills
--
Roy Hills Tel: +44 1634 721855
NTA Monitor Ltd FAX: +44 1634 721844
14 Ashford House, Beaufort Court,
Medway City Estate, Email: Roy.Hills@nta-monitor.com
Rochester, Kent ME2 4FA, UK WWW: http://www.nta-monitor.com/
next prev parent reply other threads:[~2001-12-28 17:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 10:18 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 17:44 ` Roy Hills [this message]
2001-12-28 18:19 ` zImage not supported for 2.2.20? 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
2001-12-31 12:16 ` Roy Hills
2001-12-31 13:06 ` Petri Kaukasoina
2001-12-28 13:11 ` 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-31 9:12 ` Roy Hills
2002-01-02 0:54 ` H. Peter Anvin
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=4.3.2.7.2.20011228173505.00aa3da0@192.168.124.1 \
--to=linux-kernel-l@nta-monitor.com \
--cc=kaukasoi@elektroni.ee.tut.fi \
--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®