From: Hans de Goede <hdegoede@redhat.com>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>,
"Pali Rohár" <pali@kernel.org>,
"Gerardo Esteban Malazdrewicz" <gerardo@malazdrewicz.com.ar>
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 18:00:40 +0200 [thread overview]
Message-ID: <5c60629a-c67b-e3dd-021b-0aa59f51b992@redhat.com> (raw)
In-Reply-To: <DM6PR19MB2636BAADCEAD0840771BF424FA0A0@DM6PR19MB2636.namprd19.prod.outlook.com>
Hi,
On 10/7/20 5:53 PM, Limonciello, Mario wrote:
>>
>> 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.
Ack, that is my take on this to (check on a case by case basis
if we need any of those other drivers on Alienware models too).
Regards,
Hans
>>>> Alienware has been a subsidiary of Dell since 2006.
>>>>
>>>> 2020 Alienware laptop:
>>>> $ sudo dmidecode | head -3
>>>> # dmidecode 3.2
>>>> Getting SMBIOS data from sysfs.
>>>> SMBIOS 3.2.0 present.
>>>> $ sudo dmidecode | grep -A 29 "OEM Strings"
>>>> OEM Strings
>>>> String 1: Alienware
>>>> String 2: 1[099B]
>>>> String 3: 3[1.0]
>>>> String 4: 4[0001]
>>>> String 5: 5[0000]
>>>> String 6: 6[D0, D4, D8, DA, DE]
>>>> String 7: 7[]
>>>> String 8: 8[]
>>>> String 9: 9[]
>>>> String 10: 10[1.3.0]
>>>> String 11: 11[]
>>>> String 12: 12[]
>>>> String 13: 13[P38E002]
>>>> String 14: 14[0]
>>>> String 15: 15[0]
>>>> String 16: 16[0]
>>>> String 17: 17[0000000000000000]
>>>> String 18: 18[0]
>>>> String 19: 19[1]
>>>> String 20: 20[]
>>>> String 21: 21[]
>>>> String 22: <BAD INDEX>
>>>> String 23: <BAD INDEX>
>>>> String 24: <BAD INDEX>
>>>> String 25: <BAD INDEX>
>>>> String 26: <BAD INDEX>
>>>> String 27: <BAD INDEX>
>>>> String 28: <BAD INDEX>
>>>>
>>>> 2013 Alienware laptop:
>>>> OEM Strings
>>>> String 1: Dell System
>>>> String 2: 1[05AA]
>>>> String 3: 14[2]
>>>> String 4: 15[0]
>>>> String 5: String5 for Original Equipment Manufacturer
>>>>
>>>> Don't know when the OEM String changed.
>>>> Change tested in the 2020 laptop, loads dell_smbios without further
>>>> issues.
>>>>
>>>> Signed-off-by: Gerardo E. Malazdrewicz <gerardo@malazdrewicz.com.ar>
>>>> Reviewed-by: Mario Limonciello <mario.limonciello@dell.com>
>>>> ---
>>>> drivers/platform/x86/dell-smbios-base.c | 3 ++-
>>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/platform/x86/dell-smbios-base.c
>>>> b/drivers/platform/x86/dell-smbios-base.c
>>>> index 2e2cd565926aa..5ad6f7c105cf3 100644
>>>> --- a/drivers/platform/x86/dell-smbios-base.c
>>>> +++ b/drivers/platform/x86/dell-smbios-base.c
>>>> @@ -564,7 +564,8 @@ static int __init dell_smbios_init(void)
>>>> int ret, wmi, smm;
>>>> if (!dmi_find_device(DMI_DEV_TYPE_OEM_STRING, "Dell System",
>>>> NULL) &&
>>>> - !dmi_find_device(DMI_DEV_TYPE_OEM_STRING, "www.dell.com",
>>>> NULL)) {
>>>> + !dmi_find_device(DMI_DEV_TYPE_OEM_STRING, "www.dell.com",
>>>> NULL) &&
>>>> + !dmi_find_device(DMI_DEV_TYPE_OEM_STRING, "Alienware",
>>>> NULL)) {
>>>> pr_err("Unable to run on non-Dell system\n");
>>>> return -ENODEV;
>>>> }
>>>>
>>>>
>>>>
>>>
>
next prev parent reply other threads:[~2020-10-07 16:00 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 [this message]
[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
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=5c60629a-c67b-e3dd-021b-0aa59f51b992@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