From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Pentium IV-summary
Date: 8 Nov 2000 16:16:21 -0800 [thread overview]
Message-ID: <8ucqcl$p2b$1@cesium.transmeta.com> (raw)
In-Reply-To: <20001108214759.D17544@khan.acc.umu.se> <E13tdxo-0000W1-00@the-village.bc.nu>
Followup to: <E13tdxo-0000W1-00@the-village.bc.nu>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> > Is this revamp only for processors that actually support the
> > CPUID-instruction, or will you fix the CPU-detection for non-CPUID
> > processors too?! There are quite a few processors that can be detected
> > properly but aren't (for instance, IBM 486slc/slc2/slc3)
>
> Linus refused code to ident the ones that didnt matter because the code was
> (neccessarily) obscure, weird and didn't change anything but the string in
> procfs.
>
It should be a lot cleaner to do that kind of stuff -- if you feel
it's worth bothering to -- in my changed version. It's taking a bit
longer than I'd like, because I keep uncovering, ahem, "issues" with
the current code that can be easily fixed once one adds a real
framework for these things. I hopefully will have something RSN.
-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
-
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-09 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 20:14 Pentium IV-summary Frank Davis
2000-11-08 20:36 ` H. Peter Anvin
2000-11-08 20:47 ` David Weinehall
2000-11-08 22:45 ` Alan Cox
2000-11-09 0:16 ` H. Peter Anvin [this message]
2000-11-09 0:46 ` Prasanna P Subash
-- strict thread matches above, loose matches on Subject: below --
2000-11-08 20:14 Frank Davis
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='8ucqcl$p2b$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.