All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: John Clemens <john@deater.net>
Cc: Dave Jones <davej@suse.de>, <linux-kernel@vger.kernel.org>
Subject: Re: BIOS, Duron4 specifics...
Date: 13 Jul 2001 14:19:00 -0600	[thread overview]
Message-ID: <m1pub44m6j.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0107101222560.13575-100000@pianoman.cluster.toy>
In-Reply-To: <Pine.LNX.4.33.0107101222560.13575-100000@pianoman.cluster.toy>

John Clemens <john@deater.net> writes:

> On Tue, 10 Jul 2001, Dave Jones wrote:
> 
> > On Tue, 10 Jul 2001, John Clemens wrote:
> >
> > > I've got a new laptop with an AMD Duron in it, based on the Athlon4 core
> > > (PowerNow, SSE, hardware prefetch, etc.. Palomino core)..  However, it
> > > appears none of the useful features are enabled in the bios.  For example,
> > > Nowhere does it appear to enable SSE or the APIC.
> >
> > afair, the mobile Durons are not based upon the Athlon 4 core, and
> > hence won't have the features you mention. You can verify this with
> > my x86info tool which you can get from
> > ftp://ftp.suse.com/pub/people/davej/x86info/x86info-1.3.tgz
> 
> Actually, CPUID reports Family 6, Model 6, Rev2, which corellates directly
> to Athlon4/MP (Model 6) processors.  Whats surprising is that is doesn't
> report model 7, which AMD claims is supposed to be the mobile Duron ;)..
> make me wonder if it's really a neutered Athlon4.  Besides, I though the
> origional mobile durons (T-bird core, model 3) didn't even support
> powernow...?

To enable SSE you have to write a bit into a undocumented register.
For the APIC the procedure to enable it is the same as the P6 core.

Eric

  parent reply	other threads:[~2001-07-13 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10 15:28 BIOS, Duron4 specifics John Clemens
2001-07-10 15:43 ` Dave Jones
2001-07-10 16:32   ` John Clemens
2001-07-10 16:47     ` Dave Jones
2001-07-13 20:19     ` Eric W. Biederman [this message]
2001-07-10 15:56 ` Richard B. Johnson

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=m1pub44m6j.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=davej@suse.de \
    --cc=john@deater.net \
    --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.