linux-kernel - Re: [PATCH] Dell AWCC platform

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20241007172456.8590-1-kuurtb@gmail.com>
Date: Mon,  7 Oct 2024 14:24:56 -0300
From: Kurt Borja <kuurtb@...il.com>
To: w_armin@....de
Cc: hdegoede@...hat.com,
	ilpo.jarvinen@...ux.intel.com,
	kuurtb@...il.com,
	linux-kernel@...r.kernel.org,
	platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH] Dell AWCC platform_profile support

On Mon, Oct 07, 2024 at 02:24:52PM +0200, Armin Wolf wrote:
> Hi,
>
> this WMI device is already handled by the alienware-wmi driver. Could you please integrate
> this functionality into this driver instead of creating a new one?
>
> Thanks,
> Armin Wolf

Hi,

Thank you for your feedback.

Although they the same name and same GUID, both interfaces are very
different. Alienware x15's WMAX method doesn't support any of the methods
listed on alienware-wmi driver and the de-compiled MOF file on [1] which is
an open source alternative to AWCC, makes me think this might be the case
for various other newer models (G, M, X Series).

Still I could implement it as a quirk of newer models. Would this be ok?

My only worry was that it could make alienware-wmi's logic overly complex
and cumbersome, as it would support two very different interfaces with the
same GUID.

Kurt

[1] https://github.com/AlexIII/tcc-g15/blob/master/WMI-AWCC-doc.md