linux-kernel - Re: [PATCH 0/4] platform/x86: wmi: Prepare for future changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <126f3332-ce35-46d0-bd81-a66528f92032@gmx.de>
Date: Mon, 10 Nov 2025 12:03:56 +0100
From: Armin Wolf <W_Armin@....de>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: Mario Limonciello <superm1@...nel.org>, viro@...iv.linux.org.uk,
 brauner@...nel.org, Hans de Goede <hansg@...nel.org>, jack@...e.cz,
 linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
 platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH 0/4] platform/x86: wmi: Prepare for future changes

Am 10.11.25 um 12:00 schrieb Ilpo Järvinen:

> On Wed, 5 Nov 2025, Armin Wolf wrote:
>
>> Am 04.11.25 um 21:52 schrieb Mario Limonciello:
>>
>>> On 11/4/25 2:45 PM, Armin Wolf wrote:
>>>> After over a year of reverse engineering, i am finally ready to
>>>> introduce support for WMI-ACPI marshalling inside the WMI driver core.
>>> marshaling> Since the resulting patch series is quite large, i am planning
>>> to
>>>> submit the necessary patches as three separate patch series.
>>>>
>>>> This is supposed to be the first of the three patch series. Its main
>>>> purpose is to prepare the WMI driver core for the upcoming changes.
>>>> The first patch fixes an issue inside the nls utf16 to utf8 conversion
>>>> code, while the next two patches fix some minor issues inside the WMI
>>>> driver core itself. The last patch finally moves the code of the WMI
>>>> driver core into a separate repository to allow for future additions
>>>> without cluttering the main directory.
>>> One question I have here on the patch to move things.
>>>
>>> Since Windows on ARM (WoA) laptops are a thing - is this still actually x86
>>> specific?  I am wondering if this should be moving to a different subsystem
>>> altogether like ACPI; especially now with this impending other large patch
>>> series you have on your way.
>> I know of a few WoA laptops that contain ACPI-WMI devices, meaning this driver
>> is indeed not x86-specific.
>> However i need to make some changes to the WMI driver core (and actually tests
>> it on a AArch64 VM) first
>> before moving it out of drivers/platform/x86.
>>
>> Once i am actually ready for this i would prefer to move the whole stuff to
>> drivers/platform, as drivers/acpi
>> IMHO is better suited for core ACPI drivers.
> So no need to put it under drivers/platform/x86/wmi/ then at all. It
> can move directly to drivers/platform/wmi/ and you work there towards
> making it non-x86-specific.

OK, i will send the v2 revision of this series soon.

Thanks,
Armin Wolf