From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux C Programming <linux-c-programming@vger.kernel.org>
Subject: Re: Reading BIOS
Date: Thu, 25 Nov 2004 11:52:14 +0100 [thread overview]
Message-ID: <20041125105214.GF2067@lug-owl.de> (raw)
In-Reply-To: <1101371672.3795.36.camel@myLinux>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On Thu, 2004-11-25 14:04:32 +0530, Jagadeesh Bhaskar P <jbhaskar@hclinsys.com>
wrote in message <1101371672.3795.36.camel@myLinux>:
> Hi,
> Is it possible to probe for, say, ide controllers from the BIOS, CMOS
> information with a C program? Is there any documentation available
> regarding the same??
Well, you don't really want to fiddle with physical addresses from
within userspace programs while running a protected-mode operating
system:-)
If you only want to know the type of IDE controller, and if your
hardware wasn't build during stone age, it's probably as simple as
reading the IDE controller's PCI device IDs. There's a libpci available
for Linux which helps you doing this (because there are different access
methods for accessing the PCI busses).
'lspci' for example uses it, probably parsing lspci's output is just
enough for your job...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-25 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 8:34 Reading BIOS Jagadeesh Bhaskar P
2004-11-25 10:52 ` Jan-Benedict Glaw [this message]
2004-11-27 9:43 ` K. Anantha Kiran
2004-11-27 9:56 ` Jan-Benedict Glaw
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=20041125105214.GF2067@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).