From: Christer Weinigel <wingel@hog.ctrl-c.liu.se>
To: robert@schwebel.de
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
jason@mugwump.taiga.com, anders@alarsen.net, rkaiser@sysgo.de
Subject: Re: [PATCH][RFC] AMD Elan patch
Date: Wed, 2 Jan 2002 21:47:41 +0100 (CET) [thread overview]
Message-ID: <20020102204741.3268F36F9F@hog.ctrl-c.liu.se> (raw)
In-Reply-To: <Pine.LNX.4.33.0201021457300.3056-100000@callisto.local> (message from Robert Schwebel on Wed, 2 Jan 2002 14:58:48 +0100 (CET))
In-Reply-To: <Pine.LNX.4.33.0201021457300.3056-100000@callisto.local>
Robert Schwebel wrote:
> True, but does "Family 4, Model 10" always mean "Elan SC410"? An official
> source from AMD would be great here. Is anybody from AMD on the list or
> does anybody have the address of a contact person?
It seems as if "Family 4, Model 10" isn't enought, but the Users
Manual describes how to detect an Elan SC4x0 Processor:
3.6 CPU CORE IDENTIFICATION USING THE CPUID INSTRUCTION
The ElanSC400 and ElanSC410 microcontrollers are the first members of
a new family of embedded devices. The CPUID instruction can be used to
identify a processor as belonging to this family.
The Am486 CPU core in the ElanSC400 and ElanSC410 microcontrollers is
the first CPU AMD has made with a write-back cache and no FPU, so
these tests should be sufficient to uniquely identify the family.
Using the CPUID instruction the microcontroller can be done with the
following steps, as shown in the code sample in Section 3.6.3:
* Make sure the manufacturer name is "AuthenticAMD".
* Make sure the device is described as a 486 SX1 with a write-back
cache.
If it passes all the tests it must be an ElanSC400 microcontroller or
derivative.
If it's worth it or not, I don't know, I'm just curious, it has been
years since I did anything with the Elan processor for real. :-)
/Christer
--
"Just how much can I get away with and still go to heaven?"
next prev parent reply other threads:[~2002-01-02 20:48 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 21:26 AMD SC410 boot problems with recent kernels Robert Schwebel
2001-12-21 22:09 ` H. Peter Anvin
2001-12-22 16:13 ` Robert Schwebel
2001-12-23 1:44 ` H. Peter Anvin
2001-12-23 9:45 ` Robert Schwebel
2001-12-23 10:19 ` H. Peter Anvin
2001-12-23 13:16 ` Christer Weinigel
2001-12-23 20:02 ` H. Peter Anvin
2001-12-30 22:02 ` Robert Schwebel
2001-12-30 23:15 ` H. Peter Anvin
2002-01-01 12:30 ` [PATCH][RFC] AMD Elan patch Robert Schwebel
2002-01-01 21:49 ` H. Peter Anvin
2002-01-01 23:27 ` Robert Schwebel
2002-01-01 23:38 ` H. Peter Anvin
2002-01-02 0:05 ` Dave Jones
2002-01-02 0:45 ` H. Peter Anvin
2002-01-02 13:49 ` Robert Schwebel
2002-01-02 14:03 ` Dave Jones
2002-01-02 16:10 ` Alan Cox
2002-01-02 22:40 ` H. Peter Anvin
2002-01-02 23:10 ` Alan Cox
2002-01-02 23:02 ` H. Peter Anvin
2002-01-02 23:50 ` Alan Cox
2002-01-03 9:04 ` Robert Schwebel
2002-01-02 23:56 ` Robert Kaiser
2002-01-03 0:10 ` Alan Cox
2002-01-03 8:52 ` Robert Schwebel
2002-01-02 16:06 ` Alan Cox
2002-01-02 16:56 ` Robert Schwebel
2002-01-02 17:26 ` Robert Schwebel
2002-01-02 23:06 ` Peter Wächtler
2002-01-02 23:21 ` H. Peter Anvin
2002-01-02 1:07 ` [RFC] Embedded X86 systems Was: " Christer Weinigel
2002-01-02 8:45 ` Alan Cox
2002-01-02 9:05 ` Christer Weinigel
2002-01-02 9:18 ` Alan Cox
2002-01-05 12:23 ` Eric W. Biederman
2002-01-02 0:06 ` Christer Weinigel
2002-01-02 0:48 ` H. Peter Anvin
2002-01-02 1:10 ` Christer Weinigel
2002-01-02 13:58 ` Robert Schwebel
2002-01-02 20:47 ` Christer Weinigel [this message]
2002-01-02 13:55 ` Robert Schwebel
2002-01-02 15:54 ` Robert Schwebel
2002-01-11 9:38 ` [PATCH] " Robert Schwebel
2002-01-21 7:28 ` New version of " Robert Schwebel
2002-01-21 20:44 ` Marcelo Tosatti
2002-01-24 8:09 ` Robert Schwebel
2002-01-24 8:39 ` Robert Schwebel
2002-01-23 10:28 ` [PATCH] " Robert Schwebel
2002-01-23 21:30 ` Marcelo Tosatti
2002-01-22 14:47 ` [PATCH][RFC] " Robert Schwebel
2002-01-22 18:01 ` Dave Jones
2002-01-22 22:55 ` New version of AMD Elan patch available Robert Schwebel
2002-02-01 22:01 ` Robert Schwebel
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=20020102204741.3268F36F9F@hog.ctrl-c.liu.se \
--to=wingel@hog.ctrl-c.liu.se \
--cc=anders@alarsen.net \
--cc=hpa@zytor.com \
--cc=jason@mugwump.taiga.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rkaiser@sysgo.de \
--cc=robert@schwebel.de \
--cc=wingel@t1.ctrl-c.liu.se \
/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