X86 platform drivers
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>,
	"Gerardo Esteban Malazdrewicz" <gerardo@malazdrewicz.com.ar>,
	"Pali Rohár" <pali@kernel.org>
Cc: "platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>
Subject: Re: [ PATCH v2 1/1] dell smbios driver : Consider Alienware a valid OEM String
Date: Wed, 7 Oct 2020 23:30:53 +0200	[thread overview]
Message-ID: <a655cb84-97ec-5558-8576-452b6ff0e34a@redhat.com> (raw)
In-Reply-To: <DM6PR19MB2636C37CC24CC23D31E36F01FA0A0@DM6PR19MB2636.namprd19.prod.outlook.com>

Hi,

On 10/7/20 11:26 PM, Limonciello, Mario wrote:
>> On 10/7/20 9:58 PM, Limonciello, Mario wrote:
>>>> -----Original Message-----
>>>> From: Gerardo Esteban Malazdrewicz <gerardo@malazdrewicz.com.ar>
>>>> Sent: Wednesday, October 7, 2020 14:55
>>>> To: Limonciello, Mario; Pali Rohár; Hans de Goede
>>>> Subject: Re: [ PATCH v2 1/1] dell smbios driver : Consider Alienware a
>> valid
>>>> OEM String
>>>>
>>>>
>>>> [EXTERNAL EMAIL]
>>>>
>>>> El mié, 07-10-2020 a las 15:53 +0000, Limonciello, Mario escribió:
>>>>>> Hans, there are more drivers which checks for Dell DMI strings.
>>>>>> Probably
>>>>>> it would be needed to update Alienware on more places, not only in
>>>>>> dell-smbios-base.c driver.
>>>>>
>>>>> I would prefer that each of those be checked on a case by case basis
>>>>> and only
>>>>> added if actually necessary.  Gerardo if you can please check any
>>>>> other drivers
>>>>> that should need this string added to their allow list.
>>>>
>>>> I didn't find other instances of that string in this subsystem, but see
>>>> below.
>>>>
>>>> There is one in pci, another in hotplug.
>>>>
>>>> However, this is an extract from kernel logs:
>>>>
>>>> [  138.093686] dell-smbios A80593CE-A997-11DA-B012-B622A1EF5492: WMI
>>>> SMBIOS userspace interface not supported(0), try upgrading to a newer
>>>> BIOS
>>>
>>> Considering that messaging - does the non-WMI interface actually work?
>>> dell-smbios has two backends available.
>>
>> Yes that is a very good question.
>>
>> Gerardo, I guess you started looking into this because of the:
>>
>> 	pr_err("Unable to run on non-Dell system\n");
>>
>> In dell-smbios-base.c triggering on your system?
> 
> If that's the case, I would ask why this driver even auto-loaded?
> The module load table is very prescriptive.
> https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-smbios-wmi.c#L277
> https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-smbios-smm.c#L56
> Was it because it was compiled into the kernel?

I believe that the laptops ACPI tables do define the WMI GUID
that dell-smbios-wmi.c has in its module-id-table otherwise
the "WMI SMBIOS userspace interface not supported(0)" error
would not trigger.

Regards,

Hans


  reply	other threads:[~2020-10-07 21:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03 11:52 [ PATCH: 1/1] dell smbios driver : Consider Alienware a valid OEM String Gerardo Esteban Malazdrewicz
2020-10-03 13:00 ` Hans de Goede
2020-10-05 12:45   ` Limonciello, Mario
2020-10-06  3:23     ` [ PATCH v2 " Gerardo Esteban Malazdrewicz
2020-10-07 14:21       ` Hans de Goede
2020-10-07 14:33         ` Pali Rohár
2020-10-07 15:53           ` Limonciello, Mario
2020-10-07 16:00             ` Hans de Goede
     [not found]             ` <45e82b6dabb591de630ac0e91a3ebb7937245fb1.camel@malazdrewicz.com.ar>
     [not found]               ` <DM6PR19MB26363563F46E95E50AD28854FA0A0@DM6PR19MB2636.namprd19.prod.outlook.com>
2020-10-07 20:38                 ` Hans de Goede
2020-10-07 21:26                   ` Limonciello, Mario
2020-10-07 21:30                     ` Hans de Goede [this message]
2020-10-07 21:33                       ` Limonciello, Mario
2020-10-09  5:33                   ` Gerardo Esteban Malazdrewicz
2020-10-09  8:26                     ` Pali Rohár
2020-10-09  9:14                       ` Hans de Goede
2020-10-09  9:24                         ` Pali Rohár
2020-10-09  9:40                           ` Hans de Goede

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=a655cb84-97ec-5558-8576-452b6ff0e34a@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=gerardo@malazdrewicz.com.ar \
    --cc=pali@kernel.org \
    --cc=platform-driver-x86@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