From: Bjorn Helgaas <bhelgaas@google.com>
To: Jordan Hargrave <jharg93@gmail.com>
Cc: Jean Delvare <jdelvare@suse.de>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Jordan Hargrave <Jordan_Hargrave@dell.com>
Subject: Re: [PATCH] Add support for reading SMBIOS Slot number for PCI devices
Date: Tue, 21 Jul 2015 11:57:59 -0500 [thread overview]
Message-ID: <20150721165759.GD21967@google.com> (raw)
In-Reply-To: <CAC1AzdfFjPrfvg2iBYXY5JDKhbVH3LPQdh5LzyjMaBFSNDBi6Q@mail.gmail.com>
On Mon, Jul 13, 2015 at 09:57:32AM -0500, Jordan Hargrave wrote:
> On Mon, Jul 13, 2015 at 2:35 AM, Jean Delvare <jdelvare@suse.de> wrote:
>
> > Hi Jordan,
> >
> > On Fri, 10 Jul 2015 17:02:46 -0500, Jordan Hargrave wrote:
> > > From: Jordan Hargrave <Jordan_Hargrave@dell.com>
> > >
> > > There currently isn't an easy way to determine which PCI devices belong
> > to
> > > system slots. This patch adds support to read SMBIOS Type 9 (System
> > Slots).
> >
> > I'm wondering, can't you use dmidecode or libsmbios to retrieve the
> > same information?
> >
> > --
> > Jean Delvare
> > SUSE L3 Support
> >
>
> You can but it's as not easy to determine the slot number for leaf devices
> on bridges. Eventually planning on using this for pulling slot number for
> identifying network cards and disk numbering for systemd
Can you outline the problems with using dmidecode or libsmbios?
next prev parent reply other threads:[~2015-07-21 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 22:02 [PATCH] Add support for reading SMBIOS Slot number for PCI devices Jordan Hargrave
2015-07-13 7:35 ` Jean Delvare
[not found] ` <CAC1AzdfFjPrfvg2iBYXY5JDKhbVH3LPQdh5LzyjMaBFSNDBi6Q@mail.gmail.com>
2015-07-13 15:11 ` Jordan Hargrave
2015-07-21 16:57 ` Bjorn Helgaas [this message]
2015-07-21 17:31 ` Jordan Hargrave
2015-07-22 1:09 ` Bjorn Helgaas
2015-07-22 20:07 ` Jordan Hargrave
2015-07-23 17:24 ` Bjorn Helgaas
2015-07-24 2:31 ` Jordan Hargrave
2015-07-24 3:11 ` Jordan Hargrave
2015-11-10 14:40 ` Jordan Hargrave
2015-07-21 18:09 ` Bjorn Helgaas
2015-07-21 18:56 ` Jordan Hargrave
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=20150721165759.GD21967@google.com \
--to=bhelgaas@google.com \
--cc=Jordan_Hargrave@dell.com \
--cc=jdelvare@suse.de \
--cc=jharg93@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).