From: Roger Heflin <rheflin@atipa.com>
To: Madhukar Mythri <madhukar.mythri@wipro.com>
Cc: Erik Mouw <erik@harddisk-recovery.com>, linux-kernel@vger.kernel.org
Subject: Re: How to read BIOS information
Date: Tue, 09 May 2006 09:44:21 -0500 [thread overview]
Message-ID: <4460AAC5.8090703@atipa.com> (raw)
In-Reply-To: <4460273E.5040608@wipro.com>
Madhukar Mythri wrote:
> Erik Mouw wrote:
>
>> On Mon, May 08, 2006 at 08:58:51PM +0530, Madhukar Mythri wrote:
>>
>>
>>> I forgot mention, that my Kernel is NONSMP based kernel....
>>>
>>
>> Then your application can't use HT anyway, so why bother?
>>
>>
>> Erik
>>
>>
>>
> 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?
>
>
Each motherboard/bios *VERSION* can and sometimes does change the location
of the internal bits that define what and where each bios setting is.
I know upgrading major bios version on a motherboard will often leave
the motherboard needing a full cmos clear because what the bits mean
changed and the new usage of the bits does not allow the motherboard
to post.
I don't believe that they actually document the internal settings, and
even if they did, the number of motherboard/bios combinations is way
too high for it to work easily.
This is why there (in general) are no programs that change the bios
settings from the OS, there is no general solution that works for all,
and there are too many combinations, and too little documentation.
Roger
next prev parent reply other threads:[~2006-05-09 14:44 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
2006-05-09 13:18 ` Madhukar Mythri
2006-05-09 14:44 ` Roger Heflin [this message]
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=4460AAC5.8090703@atipa.com \
--to=rheflin@atipa.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=madhukar.mythri@wipro.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