From: Jean Delvare <jdelvare@suse.de>
To: Jordan Hargrave <jharg93@gmail.com>
Cc: Jordan Hargrave <Jordan_Hargrave@dell.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Save SMBIOS Type 9 System Slots during DMI Scan
Date: Thu, 26 Nov 2015 09:26:54 +0100 [thread overview]
Message-ID: <20151126092654.3519cef4@endymion.delvare> (raw)
In-Reply-To: <CAC1Azdf_kbZ2o0WyO6Mm=sYiAZc5SxT1Ew-D0bJf0hRNjn5LOA@mail.gmail.com>
On Thu, 26 Nov 2015 02:02:52 -0600, Jordan Hargrave wrote:
> On Wed, Nov 25, 2015 at 5:47 AM, Jean Delvare <jdelvare@suse.de> wrote:
> > On Wed, 18 Nov 2015 16:02:14 -0600, Jordan Hargrave wrote:
> > > +static void __init dmi_save_system_slot(const struct dmi_header *dm)
> > > +{
> > > + const char *name;
> > > + const u8 *d = (u8*)dm;
> > > +
> > > + if (dm->type == DMI_ENTRY_SYSTEM_SLOT && dm->length >= 0x11) {
> >
> > The first half of the test will always succeed so it can be omitted.
> > OTOH you do not check the value of d + 0x07 (current usage.) As I
> > understand it, you should only consider slots which are in use, so
> > where *(d + 0x07) == 0x04?
>
> Unfortunately BIOS often get 'usage' wrong. And I'd like to keep all slots
> recorded if user hotplugs PCIe card.
OK, then please add a comment saying so.
I'm curious how the BIOS can assign a device number and function when
there is no card in the slot. I'm also curious how multi-function
cards are handled. I suppose that only the first function has a DMI
record?
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2015-11-26 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 22:02 Jordan Hargrave
2015-11-18 22:14 ` Jordan_Hargrave
2015-11-25 11:47 ` Jean Delvare
[not found] ` <CAC1Azdf_kbZ2o0WyO6Mm=sYiAZc5SxT1Ew-D0bJf0hRNjn5LOA@mail.gmail.com>
2015-11-26 8:26 ` Jean Delvare [this message]
[not found] ` <CAC1AzdcFKA_zP5S-oxjjP1sSdnzCeBsNgsocLR2vyhqy3Mhhcg@mail.gmail.com>
2015-11-27 9:25 ` Jean Delvare
2015-11-27 11:45 ` Jean Delvare
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=20151126092654.3519cef4@endymion.delvare \
--to=jdelvare@suse.de \
--cc=Jordan_Hargrave@dell.com \
--cc=jharg93@gmail.com \
--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
all inboxes | Powered by JetHome®