From: Dominik Kubla <dominik.kubla@uni-mainz.de>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Jack Hammer <jhammer@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: Slot Number Question
Date: Tue, 16 Jan 2001 00:47:54 +0100 [thread overview]
Message-ID: <20010116004754.A14902@uni-mainz.de> (raw)
In-Reply-To: <OF164CE1E4.54391C01-ON852569D5.0067049B@raleigh.ibm.com> <Pine.LNX.3.95.1010115145101.2779A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1010115145101.2779A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Mon, Jan 15, 2001 at 03:22:58PM -0500
On Mon, Jan 15, 2001 at 03:22:58PM -0500, Richard B. Johnson wrote:
>
> In any case, there is no way to correlate the device number with a
> PC connector slot just as there is no way to find out which of the
> 4 INT lines go to these connectors. The BIOS vendor only knows for
> sure, and since BIOSes are not updated as often as boards, even the
> BIOS is often incorrect.
Well actually there seems to be a way to do this. Quoting "System Management
BIOS Reference Specification" v2.3.1 (p.51):
3.3.10 System Slots (Type 9)
The information in this structure defines the attributes of a system
slot. One structure is provided for each slot in the system.
And later in table 3.3.10.5 (p.53):
Identifies the value present in the Slot Number field of the PCI Interrupt
Routing Table entry that is associated with this slot, in offset 09h [...]
Software can determine the PCI bus number and device associated with the
slot by matching the "Slot ID" to an entry in the routing table... and
ultimately determine what device is present in that slot.
Right now Linux' SMBIOS implementation use only the first 3 tables to determine
the manufacturer of system and BIOS to blacklist known buggy APM/ACPI
implementations. Since i have the SMBIOS specs at hand i will have a lot.
Is there a PCI spec available on the net? www.pcisig.org asks for a password
when you try to download the specs... (don't you just love "secret" standards?)
Yours,
Dominik Kubla
--
Sign me!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-15 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 19:03 Jack Hammer
2001-01-15 20:22 ` Richard B. Johnson
2001-01-15 23:47 ` Dominik Kubla [this message]
2001-01-16 1:15 ` Richard B. 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=20010116004754.A14902@uni-mainz.de \
--to=dominik.kubla@uni-mainz.de \
--cc=jhammer@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®