From: Kendrick Hamilton <hamilton@sedsystems.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCI probe, please CC hamilton@sedsystems.ca
Date: Mon, 15 Sep 2003 17:22:09 -0600 [thread overview]
Message-ID: <3F6649A1.6070103@sedsystems.ca> (raw)
In-Reply-To: <20030915230949.GA18153@kroah.com>
Greg,
We don't have a hardware address to use. What I am looking for is a
way to tie it to the slot number. Is there any way of getting the slot
number?
Kendrick
PS. I just subscribed to the linux kernel mailing list so I don't need
the CC hamilton@sedsystems.ca anymore.
Greg KH wrote:
>On Mon, Sep 15, 2003 at 04:58:39PM -0600, Kendrick Hamilton wrote:
>
>
>>Hello,
>> we are using the Linux 2.2.16 kernel (some of the code we purchased
>>does not work with 2.4.x kernels and we would have to do a lot of
>>regression testing to upgrade) on an IBM e-server. We wrote a module for
>>a modulator card we are using. The code uses pci_find_device to find the
>>modulator cards. The problem we are having is that it finds the cards in
>>different orders. One time hss0 is the card in slot 4 and hss1 is the
>>card in slot5. The next time we power up the computer, hss0 is the card
>>in slot5 and hss1 is the card in slot 4.
>> The IBM e-server has about 5 PCI bridges.
>> Do you have any suggestion as to how I might be able to ensure the
>>cards are always detected in the same order? Our system requires that
>>they always be in the same order.
>>
>>
>
>Are the pci device ids different across different boots? If not, is
>there any way you can tie a specific device to a specific interface
>(unique hardware addresses, mac addresses, etc.)?
>
>thanks,
>
>greg k-h
>
>
next prev parent reply other threads:[~2003-09-15 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 22:58 PCI probe, please CC hamilton@sedsystems.ca Kendrick Hamilton
2003-09-15 23:09 ` Greg KH
2003-09-15 23:22 ` Kendrick Hamilton [this message]
2003-09-16 0:17 ` Greg KH
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=3F6649A1.6070103@sedsystems.ca \
--to=hamilton@sedsystems.ca \
--cc=linux-kernel@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