The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Adam Jones <adam@yggdrasl.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel: padlock: VIA PadLock not detected.
Date: Tue, 23 May 2006 20:41:19 +0100	[thread overview]
Message-ID: <adam.20060523194119$0db7@samael.haus> (raw)
In-Reply-To: 20060523164634.GC9829@dantooine

In a futile gesture against entropy, markus reichelt wrote:

> I get the following message on a Nehemiah system. Any ideas about
> that?

> kernel: CPU0: Centaur VIA Nehemiah stepping 01
> kernel: padlock: VIA PadLock not detected
> 
> cat /proc/cpuinfo
[...]
> flags           : fpu de tsc msr cx8 mtrr pge cmov mmx fxsr sse
> fxsr_opt

I believe the padlock support was only added in later steppings of the
Nehemiah core.  My Nehemiah system here supports it:

cat /proc/cpuinfo 
processor       : 0
vendor_id       : CentaurHauls
cpu family      : 6
model           : 9
model name      : VIA Nehemiah
stepping        : 8
cpu MHz         : 997.000
cache size      : 64 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr cx8 sep mtrr pge cmov pat mmx fxsr sse rng rng_en ace ace_en
bogomips        : 2007.25

(Note the rng* and ace* flags)

According to a VIA press release here:
http://www.linuxdevices.com/sponsors/SP2782600871-NS4520757633.html
only stepping 8 or later CPUs support these instructions.
-- 
Adam Jones (adam@yggdrasl.demon.co.uk)(http://www.yggdrasl.demon.co.uk/)
.oO("It's not like it's sigfile fodder or anything..."                 )
PGP public key: http://www.yggdrasl.demon.co.uk/pubkey.asc


      reply	other threads:[~2006-05-23 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 16:46 kernel: padlock: VIA PadLock not detected markus reichelt
2006-05-23 19:41 ` Adam Jones [this message]

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='adam.20060523194119$0db7@samael.haus' \
    --to=adam@yggdrasl.demon.co.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