From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: PCIe bus enumeration
Date: Thu, 22 Jan 2015 19:37:10 +0800 [thread overview]
Message-ID: <20150122113710.GA3977@kroah.com> (raw)
In-Reply-To: <54C0B8F1.2010208@gmail.com>
On Thu, Jan 22, 2015 at 05:46:41PM +0900, J.Hwan Kim wrote:
> Hi,
>
> Is there any method for assigning PCIe bus fixed?
Nope, sorry, the BIOS controls this.
> For example, my device pcie bus number is changed
> when another pcie device is inserted.
>
> I have a 4 same pcie device and i want to identify each device
> according to the pci bus number (according to pcie slot they are
> inserted into).
Then use the slot attribute, if your BIOS supports that. If it doesn't,
then there's nothing you can do, pci ids can be randomly assigned, and
you should never make any assumptions based on them. I had a bios that
would change the order every other boot, was great for testing things
like this out.
sorry,
greg k-h
prev parent reply other threads:[~2015-01-22 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 8:46 PCIe bus enumeration J.Hwan Kim
2015-01-22 11:37 ` Greg KH [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=20150122113710.GA3977@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).