From: David Newall <davidn@davidnewall.com>
To: David Wilson <mcs6502@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is the best way to identify a new x86 processor that does not implement the CPUID instruction?
Date: Tue, 05 Aug 2008 18:56:45 +0930 [thread overview]
Message-ID: <48981CD5.5090106@davidnewall.com> (raw)
In-Reply-To: <3666888f0808050008h38e11737k8e6cb9c4c85aa457@mail.gmail.com>
David Wilson wrote:
> I recently bought a Norhtec MicroClient JrSX which uses the Vortex86sx
> System on Chip processor (see http://vortex86sx.com/ for more
> details). This is identified as a Cyrix 486SLC by the Linux kernel due
> to the lack of a CPUID instruction.
Consider creating a new boot-time parameter to identify it.
next prev parent reply other threads:[~2008-08-05 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 7:08 What is the best way to identify a new x86 processor that does not implement the CPUID instruction? David Wilson
2008-08-05 9:26 ` David Newall [this message]
2008-08-06 2:33 ` Jike Song
2008-08-06 12:12 ` Bill Davidsen
2008-08-08 11:00 ` Andi Kleen
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=48981CD5.5090106@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcs6502@gmail.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