From: Kronos <kronos@kronoz.cjb.net>
To: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@attila.bofh.it>, willy@w.ods.org
Subject: Re: i486 emu in mainline?
Date: Tue, 25 May 2004 19:21:02 +0200 [thread overview]
Message-ID: <20040525172102.GA3743@dreamland.darkstar.lan> (raw)
In-Reply-To: <20040522234059.GA3735@infradead.org>
Christoph Hellwig <hch@lst.de> ha scritto:
> --- kernel-source-2.6.6/arch/i386/Kconfig 2004-05-10 19:47:45.000000000 +1000
> +++ kernel-source-2.6.6-1/arch/i386/Kconfig 2004-05-10 22:21:08.000000000 +1000
> @@ -330,6 +330,41 @@
> This is really intended for distributors who need more
> generic optimizations.
>
> +config X86_EMU486
> + bool "486 emulation"
> + help
Hi,
what about adding an explicit dependancy from M386/M486? A kernel
compiled for 486 or higher won't boot on 386 anyway so the emulation
code would be useless.
diff -Nru a/arch/i386/Kconfig b/arch/i386/Kconfig
--- a/arch/i386/Kconfig 2004-05-25 19:07:16.000000000 +0200
+++ b/arch/i386/Kconfig 2004-05-25 19:10:59.000000000 +0200
@@ -332,6 +332,7 @@
config X86_EMU486
bool "486 emulation"
+ depends on M386 || M486
help
When used on a 386, Linux can emulate 3 instructions from the 486
set. This allows user space programs compiled for 486 to run on a
Signed-off-by: Luca Tettamanti <kronos@kronoz.cjb.net>
(just in case ;) )
Luca
--
Home: http://kronoz.cjb.net
Windows /win'dohz/ n. : thirty-two bit extension and graphical shell to
a sixteen bit patch to an eight bit operating system originally coded
for a four bit microprocessor which was written by a two-bit company
that can't stand a bit of competition.
next prev parent reply other threads:[~2004-05-25 17:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 23:40 Christoph Hellwig
2004-05-23 0:20 ` Rene Rebe
2004-05-23 7:13 ` Arjan van de Ven
2004-05-23 8:44 ` Willy Tarreau
2004-05-23 9:13 ` Arjan van de Ven
2004-05-23 9:48 ` Willy Tarreau
2004-05-23 9:58 ` Arjan van de Ven
2004-05-23 11:49 ` Helge Hafting
2004-05-23 9:20 ` Andrew Morton
2004-05-23 17:11 ` Brian Gerst
2004-05-24 2:47 ` Herbert Xu
2004-05-27 21:03 ` Pavel Machek
2004-05-23 8:29 ` Willy Tarreau
2004-05-23 11:08 ` Alan Cox
2004-05-23 11:57 ` Willy Tarreau
2004-05-23 13:15 ` Alan Cox
2004-05-24 15:17 ` Jan-Benedict Glaw
2004-05-24 17:41 ` Alan Cox
2004-05-25 9:36 ` Jan-Benedict Glaw
2004-05-25 13:48 ` Alan Cox
[not found] ` <20040523105130.GA588@samarkand.rivenstone.net>
2004-05-23 11:59 ` Willy Tarreau
2004-05-24 9:08 ` P
2004-05-23 15:18 ` Jeff Garzik
2004-05-23 21:14 ` Alan Cox
2004-05-24 12:28 ` Maciej W. Rozycki
2004-05-25 17:21 ` Kronos [this message]
2004-05-25 17:03 Albert Cahalan
2004-05-25 22:43 ` Alan Cox
2004-10-10 20:33 Nathanael Nerode
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=20040525172102.GA3743@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=hch@attila.bofh.it \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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®