linux-kernel - Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM

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] [day] [month] [year] [list]

Message-Id: <96fb5e3f-7855-4fe6-b263-60bc132716d3@app.fastmail.com>
Date: Wed, 28 Jan 2026 08:24:08 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Alexander Usyskin" <alexander.usyskin@...el.com>,
 "Geert Uytterhoeven" <geert+renesas@...der.be>,
 "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
 "Simon Richter" <Simon.Richter@...yros.de>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE

On Wed, Jan 28, 2026, at 07:57, Usyskin, Alexander wrote:
>> Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
>> As far as I can tell, i915 and xe will attempt (and fail) to
>> use MEI if that is enabled, so there is no point in enabling
>> INTEL_MEI outside of compile-testing even if XE is built.
>> 
>
> There are different usages of mei:
> - for discrete graphics xe/i915 will load mei via auxiliary device also 
> on non x86.

Right, I see.

> - for integrated xe/i915 communicate with mei for on-chip CSME - this 
> scenario is x86 only.
>
> IMO this should cover all:
> depends on X86 || DRM_XE!=n || DRM_I915!=n || COMPILE_TEST

Ok

        Arnd