All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Corey Minyard <minyard@acm.org>,
	Andy Lutomirski <luto@kernel.org>,
	OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	brijeshkumar.singh@amd.com
Subject: Re: [Openipmi-developer] ipmi_si feature request: SMBIOS-based autoloading
Date: Mon, 01 Feb 2016 09:46:49 +0100	[thread overview]
Message-ID: <1454316409.4754.9.camel@chaos.site> (raw)
In-Reply-To: <CALCETrWAFcx8_Z2aat9-bPwc0Ov5eCHiP-AOiJu8J41pG==COg@mail.gmail.com>

Le Tuesday 26 January 2016 à 09:29 -0800, Andy Lutomirski a écrit :
> On Tue, Jan 26, 2016 at 5:43 AM, Corey Minyard <minyard@acm.org> wrote:
> >
> > On 01/26/2016 07:32 AM, Corey Minyard wrote:
> >>
> >> On 01/24/2016 07:45 PM, Andy Lutomirski wrote:
> >>> Alternatively, maybe /sys/firmware/dmi could learn how to advertise
> >>> modaliases.  But that might be a giant mess to solve a tiny problem.
> >>
> >> This sounds like the right way, but you are probably right.  Are
> >> there any other resources that could benefit from this?  I"m
> >> guessing not.
> 
> No clue.  Jean might know.  Jean?

In principle I agree it would be the right thing to do.

Now in practice I'm afraid the interest would be limited, because 1* on
so many occasions the DMI data is wrong and 2* the level of details that
can be encoded in the DMI table data is fairly limited. The IPMI records
may be an exception there because IPMI is only found on high-end
hardware and this is where in general the DMI data is correct. But for
most other records, you want to trust the hardware itself more than the
DMI data.

So you only want to rely on DMI data for information you can't get in
any other way. That being said, advertising a modalias is something
fairly safe. The driver getting loaded is free to use or not use the DMI
data.

And even if the only modalias in /sys/firmware/dmi is going to be for
IPMI, I see no reason for not doing that, if it serves the purpose.

-- 
Jean Delvare
SUSE L3 Support

      parent reply	other threads:[~2016-02-01  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  1:45 ipmi_si feature request: SMBIOS-based autoloading Andy Lutomirski
2016-01-26 13:32 ` Corey Minyard
2016-01-26 13:43   ` [Openipmi-developer] " Corey Minyard
2016-01-26 17:29     ` Andy Lutomirski
2016-01-29 20:12       ` Corey Minyard
2016-02-01  8:46       ` Jean Delvare [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=1454316409.4754.9.camel@chaos.site \
    --to=jdelvare@suse.de \
    --cc=brijeshkumar.singh@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=minyard@acm.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.