From: Richard Mittendorfer <delist@gmx.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to read BIOS information
Date: Tue, 9 May 2006 14:51:57 +0200 [thread overview]
Message-ID: <20060509145157.19edab87.delist@gmx.net> (raw)
In-Reply-To: <44608B0D.3050300@stesmi.com>
Also sprach Stefan Smietanowski <stesmi@stesmi.com> (Tue, 09 May 2006
14:29:01 +0200):
> Alan Cox wrote:
> > On Maw, 2006-05-09 at 10:53 +0530, Madhukar Mythri wrote:
> >
> >> yeah, your are correct. but, the thing is my superiors want, even
> >if >kernel not reconize/use HT, we have to capture it from BIOS...
> >>Thats why i asked as, how to read BIOS information?
> >
> >
> > You ask the BIOS vendor for the exact board in question.
> >
> > If you want to ask the processor itself then you can use the model
> > specific registers. These are accessible via /dev/cpu/<cpuid>/msr so
> > you can perform the Intel recommended sequence for checking if the
> > processor has HT enabled.
> >
> > It might be simpler to look in /proc/cpuinfo if you just need the
> > basic information
>
> He's actually asking if the BIOS has turned on HT, not if some other
> means has...
>
> BUT, the only thing I can think of is turning OFF HT in the BIOS,
> reading the CMOS, storing it somewhere, turning ON HT, storing
> that somewhere and comparing them. Then he'll know that in his
> specific BIOS revision on his specific mainboard that bit is
> stored in one specific place and he can go from there.
>
> Messy, definately not recommended, stupid but hey, if the bosses
> ask for it and you gotta give it ..
>
> Just make triple sure you tell them that if you upgrade the BIOS
> the test might fail or if you change mainboard, etc.
IIRC the chipset should know about this?
Something like hex /sys/devices/pci0000:0/0000:00:00.0/config and
comparing registers with the chipset's datasheet?
> // Stefan
sl ritch
next prev parent reply other threads:[~2006-05-09 12:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 14:14 How to read BIOS information Madhukar Mythri
2006-05-08 14:36 ` Richard Mittendorfer
2006-05-08 14:54 ` Madhukar Mythri
2006-05-08 14:57 ` Richard Mittendorfer
2006-05-08 14:53 ` Arjan van de Ven
2006-05-08 15:04 ` Madhukar Mythri
2006-05-08 15:07 ` Avi Kivity
2006-05-08 15:15 ` Arjan van de Ven
2006-05-08 15:28 ` Madhukar Mythri
2006-05-08 15:27 ` Erik Mouw
2006-05-09 5:23 ` Madhukar Mythri
2006-05-09 5:37 ` Jan-Benedict Glaw
2006-05-09 9:57 ` Erik Mouw
2006-05-09 11:03 ` Alan Cox
2006-05-09 12:29 ` Stefan Smietanowski
2006-05-09 12:51 ` Richard Mittendorfer [this message]
2006-05-09 13:18 ` Madhukar Mythri
2006-05-09 14:44 ` Roger Heflin
2006-05-08 15:15 ` Michal Piotrowski
2006-05-08 15:43 ` linux-os (Dick Johnson)
2006-05-10 8:32 ` Dan Carpenter
2006-05-12 20:02 ` Arjan van de Ven
2006-05-08 15:16 ` linux-os (Dick 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=20060509145157.19edab87.delist@gmx.net \
--to=delist@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox