From: "J.A. Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86 cpu selection (first hack)
Date: Fri, 31 May 2002 01:15:19 +0200 [thread overview]
Message-ID: <20020530231519.GA5519@werewolf.able.es> (raw)
In-Reply-To: <20020530225015.GA1829@werewolf.able.es> <1022803536.12888.405.camel@irongate.swansea.linux.org.uk>
On 2002.05.31 Alan Cox wrote:
>On Thu, 2002-05-30 at 23:50, J.A. Magallon wrote:
>> - Make all and every cpu a checkbox, so you just say 'I want my kernel to
>> support this and that CPU'. This kills the problem of the ordering, and
>> adds one other advantage: you do not need to support intermediate CPUs,
>> like 'i want my kernel to run ok on pentium-mmx (my firewall) and on
>> p4 (my desktop). I will never run it on a PII, so do not include the
>> hacks for PII'. And of course, 'If I run my p-mmx capable on a friend's
>> PII and it eats his drive and burns his TV set, it is only _my_ fault'.
>
>How about
>
> 'Omit support for processors without an FPU'
> 'Omit support for processors without working WP (386, Nexgen)'
> 'Require the processor has a TSC'
>
>type questions ?
>
But that requires people to know many hardware details... How the h**l
do I know if my Transmeta or Cyrix or AMD has a TSC ?? Is that an intel
specific thing or x86 ?? I just want a kernel that
runs on my XXX brand 586. What is a TSC ??
I think it has to be done based on brand/model.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre9-jam1 #1 SMP jue may 30 00:48:49 CEST 2002 i686
next prev parent reply other threads:[~2002-05-30 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 22:50 [PATCH] x86 cpu selection (first hack) J.A. Magallon
2002-05-30 23:20 ` Jeff Garzik
2002-05-30 23:42 ` Dave Jones
2002-05-31 0:36 ` J.A. Magallon
2002-05-31 0:05 ` Alan Cox
2002-05-30 23:15 ` J.A. Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-31 0:07 Leif Sawyer
2002-05-31 0:12 ` Jeff Garzik
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=20020530231519.GA5519@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--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