[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <f941534d-4ebb-46b5-88af-0fdfbffa1057@app.fastmail.com>
Date: Fri, 27 Dec 2024 12:06:49 -0500
From: "Mark Pearson" <mpearson-lenovo@...ebb.ca>
To: "Armin Wolf" <W_Armin@....de>, "John Martens" <johnfanv2@...il.com>
Cc: "Jonathan Corbet" <corbet@....net>,
"Derek J . Clark" <derekjohn.clark@...il.com>,
"Hans de Goede" <hdegoede@...hat.com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
"Luke D . Jones" <luke@...nes.dev>, nijs1@...ovo.com,
pgriffais@...vesoftware.com,
"platform-driver-x86@...r.kernel.org" <platform-driver-x86@...r.kernel.org>,
shaohz1@...ovo.com, "Mario Limonciello" <superm1@...nel.org>
Subject: Re: [PATCH 0/1] platform/x86: Add Lenovo Legion WMI Drivers
On Thu, Dec 26, 2024, at 6:19 PM, Armin Wolf wrote:
> Am 26.12.24 um 01:18 schrieb John Martens:
>
<snip>
>
>> - When trying to find out what access method to choose one cannot rely
>> on the ACPI/WMI interface. From disassembling the ACPI, one can see
>> that sometimes/often even if the function is not implemented it
>> will return without error. Moreover, there are some WMI methods
>> with name "*IsSupported" (or similar) but they often do not tell
>> the truth.
>
> Oh no.
>
> I hope that we just misinterpret the result of those methods. Otherwise
> this would indeed be
> very frustrating. Maybe some help from Lenovo can solve this issue.
>
Can someone (John?) send me the details off email list and I'll see if the Legion team can help.
(this comes with a caveat that the Legion platforms are not part of the official Linux program yet, so no promises or guarantees)
>
>> - Using just one WMI interface is simple — my grandmother could do it.
You have an awesome grandmother :D
Mark
Powered by blists - more mailing lists