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: <CY5PR11MB63664450881F6ADF08B0A7F4ED9EA@CY5PR11MB6366.namprd11.prod.outlook.com>
Date: Thu, 29 Jan 2026 09:01:25 +0000
From: "Usyskin, Alexander" <alexander.usyskin@...el.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>, Simon Richter
	<Simon.Richter@...yros.de>
CC: Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven
	<geert+renesas@...der.be>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE

> 
> > 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?
> 
> Let's give it a try on arm64.
> Remove "# CONFIG_DRM_XE is not set" from .config.
> 
>     $ make oldconfig
>     [...]
>       Intel Xe2 Graphics (DRM_XE) [N/y/?] (NEW) y
>     [...]
>     Intel Management Engine Interface (INTEL_MEI) [N/y/?] (NEW) y
>       ME Enabled Intel Chipsets (INTEL_MEI_ME) [Y/n/?] (NEW)
>     [...]
> 
> So the ordering is not an issue.
> 
> I only wonder about some of the other INTEL_MEI_* options.
> I think e.g. INTEL_MEI_ME now needs a dependency on X86, as I doubt
> any of these Intel Chipsets are used on non-x86?
> 

INTEL_MEI_ME is re-used by INTEL_MEI_GSC (the HW access code, not PCI one),
so it should not be bound to x86.

- - 
Thanks,
Sasha