From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Sven Koch <haegar@cut.de>
Cc: David Lang <david.lang@digitalinsight.com>,
"Jeff V. Merkey" <jmerkey@timpanogas.org>,
kernel@kvack.org, Martin Josefsson <gandalf@wlug.westbo.se>,
Tigran Aivazian <tigran@veritas.com>,
Anil kumar <anils_r@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: Installing kernel 2.4
Date: Tue, 07 Nov 2000 18:59:14 -0500 [thread overview]
Message-ID: <3A089752.505816BA@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0011080047260.10874-100000@space.comunit.de>
Sven Koch wrote:
>
> On Tue, 7 Nov 2000, David Lang wrote:
>
> > depending on what CPU you have the kernel (and compiler) can use different
> > commands/opmizations/etc, if you want to do this on boot you have two
> > options.
>
> Wouldn't it be possible to compile the parts of the kernel needed to
> uncompress and to detect the cpu with lower optimizations and then abort
> with an error message?
>
> "Error: Kernel needs a PIII" sounds much better than just stoping dead.
I agree... maybe we can solve this simply by giving the CPU detection
module the -march=i386 flag hardcoded, or editing the bootstrap, or
something like that...
Jeff
--
Jeff Garzik | "When I do this, my computer freezes."
Building 1024 | -user
MandrakeSoft | "Don't do that."
| -level 1
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 0:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 20:52 Installing kernel 2.4 Anil kumar
2000-11-07 20:59 ` Jeff V. Merkey
2000-11-07 21:39 ` Tigran Aivazian
2000-11-07 22:28 ` Martin Josefsson
2000-11-07 22:32 ` Jeff V. Merkey
2000-11-07 22:51 ` kernel
2000-11-07 23:10 ` Jeff V. Merkey
2000-11-07 23:57 ` Jeff Garzik
2000-11-08 0:01 ` Jeff V. Merkey
2000-11-08 0:10 ` Jeff Garzik
2000-11-08 0:12 ` Jeff V. Merkey
2000-12-10 8:22 ` Mark W. McClelland
2000-11-09 13:40 ` Alan Cox
2000-11-08 2:18 ` H. Peter Anvin
2000-11-08 7:35 ` Jeff V. Merkey
2000-11-08 0:54 ` Alan Cox
2000-11-08 3:31 ` Matthew Kirkwood
2000-11-08 0:11 ` David Lang
2000-11-07 23:39 ` Jeff V. Merkey
2000-11-07 23:51 ` Sven Koch
2000-11-07 23:59 ` Jeff Garzik [this message]
2000-11-08 0:18 ` David Relson
2000-11-08 0:23 ` Jeff V. Merkey
2000-11-08 0:50 ` Jeff Garzik
2000-11-08 0:52 ` Jeff V. Merkey
2000-11-08 0:49 ` Alan Cox
2000-11-08 0:47 ` Jeff V. Merkey
2000-11-08 0:57 ` Alan Cox
2000-11-08 0:54 ` Jeff V. Merkey
2000-11-07 22:52 ` J . A . Magallon
2000-11-07 22:54 ` J Sloan
-- strict thread matches above, loose matches on Subject: below --
2000-11-07 22:49 Bruce_Holzrichter
2000-11-07 23:24 davej
2000-11-07 23:37 ` Jeff V. Merkey
2000-11-07 23:47 ` Jeff V. Merkey
2000-11-07 23:59 ` Jeff V. Merkey
2000-11-08 0:51 ` David Lang
2000-11-08 0:10 ` Jeff V. Merkey
2000-11-08 3:39 ` davej
2000-11-08 4:41 ` Jeff V. Merkey
2000-11-08 3:57 ` davej
2000-11-08 12:05 ` Horst von Brand
2000-11-08 15:29 ` Eric W. Biederman
2000-11-08 16:51 ` James A. Sutherland
2000-11-08 17:36 ` George Anzinger
2000-11-08 19:43 ` James A. Sutherland
2000-11-08 20:32 ` George Anzinger
2000-11-08 22:01 ` James A. Sutherland
2000-11-09 13:25 ` David Woodhouse
2000-11-09 18:24 ` James A. Sutherland
2000-11-08 3:30 ` davej
2000-11-08 0:03 ` Jeff Garzik
2000-11-08 0:06 ` Jeff V. Merkey
2000-11-08 3:25 ` davej
2000-11-08 4:36 ` Jeff V. Merkey
2000-11-08 3:50 ` davej
2000-11-08 2:19 Marty Fouts
2000-11-08 2:25 Marty Fouts
2000-11-08 3:43 ` davej
2000-11-08 13:43 Jesse Pollard
2000-11-08 18:52 ` Jeff V. Merkey
2000-11-08 13:49 Bruce_Holzrichter
2000-11-08 15:10 ` davej
2000-11-08 19:16 ` Jeff V. Merkey
2000-11-08 19:19 David Feuer
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=3A089752.505816BA@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=anils_r@yahoo.com \
--cc=david.lang@digitalinsight.com \
--cc=gandalf@wlug.westbo.se \
--cc=haegar@cut.de \
--cc=jmerkey@timpanogas.org \
--cc=kernel@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
/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