From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: How to know PCI configuration
Date: Wed, 18 Aug 2004 14:17:34 +0200 [thread overview]
Message-ID: <20040818121734.GH16935@lug-owl.de> (raw)
In-Reply-To: <55ee29e00408180259a005ed0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
On Wed, 2004-08-18 15:29:43 +0530, Sudheer Vutukuru <sudheer.vutukuru@gmail.com>
wrote in message <55ee29e00408180259a005ed0@mail.gmail.com>:
> I want to know clock speed and width of PCI can any one tell me how
> can i find that
>
> 00:00.0 Host bridge: Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge (rev 01)
> Subsystem: Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
See, it's 66MHz flag is negated, so this is a 33MHz device. However, I
don't know right now how to check for 64bit bus access...
> Latency: 0
> Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
> Capabilities: <available only to root>
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 --]
prev parent reply other threads:[~2004-08-18 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 9:59 How to know PCI configuration Sudheer Vutukuru
2004-08-18 12:17 ` Jan-Benedict Glaw [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=20040818121734.GH16935@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.