From: Simon Richter <Simon.Richter@hogyros•de>
To: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Cc: Simon Richter <Simon.Richter@hogyros•de>,
"Usyskin, Alexander" <alexander.usyskin@intel•com>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Subject: [PATCH v2 1/4] misc/mei: Allow building Intel ME interface on non-x86
Date: Thu, 8 Jan 2026 03:26:02 +0900 [thread overview]
Message-ID: <20260107182615.488194-2-Simon.Richter@hogyros.de> (raw)
In-Reply-To: <20260107182615.488194-1-Simon.Richter@hogyros.de>
The xe driver supports dGPUs which can be plugged into non-x86 machines,
and exposes a MEI GSC interface, so this driver is no longer x86 only.
Cc: Usyskin, Alexander <alexander.usyskin@intel•com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Signed-off-by: Simon Richter <Simon.Richter@hogyros•de>
---
drivers/misc/mei/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
index f4eb307cd35e..6da518f3b73c 100644
--- a/drivers/misc/mei/Kconfig
+++ b/drivers/misc/mei/Kconfig
@@ -2,7 +2,7 @@
# Copyright (c) 2003-2019, Intel Corporation. All rights reserved.
config INTEL_MEI
tristate "Intel Management Engine Interface"
- depends on X86 && PCI
+ depends on PCI
default X86_64 || MATOM
help
The Intel Management Engine (Intel ME) provides Manageability,
--
2.47.3
next prev parent reply other threads:[~2026-01-07 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260107174646.GA1230850@psionic12.psi5.com>
2026-01-07 18:26 ` [PATCH v2 0/4] Intel MEI Kconfig cleanups Simon Richter
2026-01-07 18:26 ` Simon Richter [this message]
2026-01-07 18:26 ` [PATCH v2 2/4] misc/mei: Decouple ME interfaces from GPU drivers Simon Richter
2026-01-07 18:26 ` [PATCH v2 3/4] misc/mei: Allow building standalone for compile testing Simon Richter
2026-01-07 18:26 ` [PATCH v2 4/4] misc/mei: gsc_proxy: add dependency on Xe driver Simon Richter
2026-01-13 7:09 ` [PATCH v2 0/4] Intel MEI Kconfig cleanups Usyskin, Alexander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260107182615.488194-2-Simon.Richter@hogyros.de \
--to=simon.richter@hogyros$(echo .)de \
--cc=alexander.usyskin@intel$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox