From: "K. Anantha Kiran" <ananth@cse.iitk.ac.in>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Linux C Programming <linux-c-programming@vger.kernel.org>
Subject: Re: Reading BIOS
Date: Sat, 27 Nov 2004 15:13:01 +0530 [thread overview]
Message-ID: <41A84C25.9080707@cse.iitk.ac.in> (raw)
In-Reply-To: <20041125105214.GF2067@lug-owl.de>
Can anybody give references to interpret the output of *lspci* command
Thanks In Advance
K.Ananth
Jan-Benedict Glaw wrote:
>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
>
>
>
next prev parent reply other threads:[~2004-11-27 9:43 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
2004-11-27 9:43 ` K. Anantha Kiran [this message]
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=41A84C25.9080707@cse.iitk.ac.in \
--to=ananth@cse.iitk.ac.in \
--cc=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).