All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Rajat Jain <Rajat.Jain@infogain.com>
Cc: linux-newbie@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Who decides PCI device number?
Date: Wed, 06 Aug 2008 19:49:13 +0200	[thread overview]
Message-ID: <4899E419.80507@keyaccess.nl> (raw)
In-Reply-To: <C86899CCB10A6C4E93D5978DCB232D4B09002FD5@GDCMX01.igglobal.com>

On 06-08-08 07:54, Rajat Jain wrote:

> In the PCI addess (domain + PCI bus num + PCI Device num + function num)
> of a PCI device, who decides the PCI device number assigned to a PCI
> device? 
> 
> - Is it hard wired for a particular PCI slot? (So that any PCI card
> plugged into this slot will always have a particular PCI device number).

Yes, for a definition of "hard-wired" which if I'm not mistaken (which I 
might be, but believe I remember reading that once) includes the 
possibility for busses to change numbering depending on bridge detection 
order.

But yes, the "dd" in the DDDD:bb:dd.f lspci -D output indeed signifies 
the slot, not the card -- exchange two PCI cards in your system and see 
them change numbering around as well.

> -Or is it hardwired on the PCI card? (So that this card if plugged on
> any slot in any machine will have the same PCI device number)?

No.

Rene.
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

      reply	other threads:[~2008-08-06 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06  5:54 Who decides PCI device number? Rajat Jain
2008-08-06 17:49 ` Rene Herman [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=4899E419.80507@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=Rajat.Jain@infogain.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@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.