From: Kristen Accardi <kristen.c.accardi@intel.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: pcihpd-discuss@lists.sourceforge.net,
linux-kernel@vger.kernel.org, greg@kroah.com,
rajesh.shah@intel.com
Subject: Re: [Pcihpd-discuss] [PATCH] use bus_slot number for name
Date: Tue, 16 Aug 2005 15:47:20 -0700 [thread overview]
Message-ID: <1124232440.6584.75.camel@whizzy> (raw)
In-Reply-To: <20050810150154.GB16724@parcelfarce.linux.theplanet.co.uk>
On Wed, 2005-08-10 at 16:01 +0100, Matthew Wilcox wrote:
> On Fri, Aug 05, 2005 at 12:16:06PM -0700, Kristen Accardi wrote:
> > For systems with multiple hotplug controllers, you need to use more than
> > just the slot number to uniquely name the slot. Without a unique slot
> > name, the pci_hp_register() will fail. This patch adds the bus number
> > to the name.
>
> That doesn't make much sense. The slot number should at least be unique
> to the chassis, if not to the whole machine. HP's large machines with
> multiple cabinets encode the cabinet number in the return from _SUN.
> It ends up as something like 80103 for a large machine while still being
> merely slot 3 for the smaller machines.
>
> IOW, I think this is a firmware bug which needs to be fixed there.
>
Just wanted to let you know that I'm not ignoring your comment :). I'm
checking now to see if the firmware is required to make the slot number
unique across all controllers. I also am expecting a hardware/firmware
update for the machine that exhibited this behavior, and so will retest
when I get it and let you know. although, I'm not sure if it's a good
idea to trust the BIOS to do this properly even if it's required.
prev parent reply other threads:[~2005-08-16 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 19:16 [PATCH] use bus_slot number for name Kristen Accardi
2005-08-05 19:51 ` Dave Jones
2005-08-05 20:47 ` Kristen Accardi
2005-08-05 21:31 ` Kristen Accardi
2005-08-05 22:11 ` [Pcihpd-discuss] " Greg KH
2005-08-05 21:33 ` Greg KH
2005-08-10 15:01 ` [Pcihpd-discuss] " Matthew Wilcox
2005-08-16 22:47 ` Kristen Accardi [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=1124232440.6584.75.camel@whizzy \
--to=kristen.c.accardi@intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajesh.shah@intel.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