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

Message-ID: <ab91fa38-2f5c-4237-811e-854d442a71bb@hogyros.de>
Date: Thu, 29 Jan 2026 13:45:44 +0900
From: Simon Richter <Simon.Richter@...yros.de>
To: "Usyskin, Alexander" <alexander.usyskin@...el.com>,
 Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven <geert+renesas@...der.be>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>
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

Hi,

On 1/28/26 3:57 PM, Usyskin, Alexander wrote:

> There are different usages of mei:
> - for discrete graphics xe/i915 will load mei via auxiliary device also on non x86.
> - 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

Is there discrete i915?

DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant, which 
is why I didn't add it in my version of the patch. If DRM_I915 is useful 
on non-x86 we might want to change that as well.

Also, is there any policy on dependency ordering? On non-X86, INTEL_MEI 
becomes available only after selecting DRM_XE, which is in a directory 
included much later, so the question is not shown initially, is that a 
problem?

    Simon