* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE [not found] ` <CY5PR11MB63665464BE137AE70B0D47ADED9EA@CY5PR11MB6366.namprd11.prod.outlook.com> @ 2026-01-30 21:15 ` Rodrigo Vivi 2026-02-01 10:15 ` Usyskin, Alexander 0 siblings, 1 reply; 4+ messages in thread From: Rodrigo Vivi @ 2026-01-30 21:15 UTC (permalink / raw) To: Usyskin, Alexander, intel-gfx Cc: Simon Richter, Arnd Bergmann, Geert Uytterhoeven, Greg Kroah-Hartman, linux-kernel@vger.kernel.org On Thu, Jan 29, 2026 at 12:53:12AM -0500, Usyskin, Alexander wrote: > > 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? > > > > DG1, Alchemist and some server cards are supported by 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. > > > > Let ask gfx people. Cc: intel-gfx@lists.freedesktop.org > Rodrigo, is DRM_I915 useful on non-x86? No, I really don't believe it would work out. > > > 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? > > > > By not enabling INTEL_MEI the biggest thing that you loose are the firmware update. > I'm not sure how to sort this out and if it is worth the effort. > > - - > Thanks, > Sasha > > ^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE 2026-01-30 21:15 ` [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE Rodrigo Vivi @ 2026-02-01 10:15 ` Usyskin, Alexander 2026-02-02 9:33 ` Geert Uytterhoeven 0 siblings, 1 reply; 4+ messages in thread From: Usyskin, Alexander @ 2026-02-01 10:15 UTC (permalink / raw) To: Simon Richter Cc: Arnd Bergmann, Geert Uytterhoeven, Greg Kroah-Hartman, linux-kernel@vger.kernel.org, Vivi, Rodrigo, intel-gfx@lists.freedesktop.org > > > > > > > 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? > > > > > > > DG1, Alchemist and some server cards are supported by 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. > > > > > > > Let ask gfx people. > > Cc: intel-gfx@lists.freedesktop.org > > > Rodrigo, is DRM_I915 useful on non-x86? > > No, I really don't believe it would work out. > In this case the below should be good, I suppose: depends on X86 || DRM_XE!=n || COMPILE_TEST - - Thanks, Sasha ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE 2026-02-01 10:15 ` Usyskin, Alexander @ 2026-02-02 9:33 ` Geert Uytterhoeven 2026-02-02 11:43 ` Usyskin, Alexander 0 siblings, 1 reply; 4+ messages in thread From: Geert Uytterhoeven @ 2026-02-02 9:33 UTC (permalink / raw) To: Usyskin, Alexander Cc: Simon Richter, Arnd Bergmann, Geert Uytterhoeven, Greg Kroah-Hartman, linux-kernel@vger.kernel.org, Vivi, Rodrigo, intel-gfx@lists.freedesktop.org Hi Sasha On Sun, 1 Feb 2026 at 11:15, Usyskin, Alexander <alexander.usyskin@intel.com> 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? > > > > > > DG1, Alchemist and some server cards are supported by 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. > > > > > > Let ask gfx people. > > > > Cc: intel-gfx@lists.freedesktop.org > > > > > Rodrigo, is DRM_I915 useful on non-x86? > > > > No, I really don't believe it would work out. > > In this case the below should be good, I suppose: > > depends on X86 || DRM_XE!=n || COMPILE_TEST ... which is exactly what I added in my patch. So life's good? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds ^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE 2026-02-02 9:33 ` Geert Uytterhoeven @ 2026-02-02 11:43 ` Usyskin, Alexander 0 siblings, 0 replies; 4+ messages in thread From: Usyskin, Alexander @ 2026-02-02 11:43 UTC (permalink / raw) To: Geert Uytterhoeven Cc: Simon Richter, Arnd Bergmann, Geert Uytterhoeven, Greg Kroah-Hartman, linux-kernel@vger.kernel.org, Vivi, Rodrigo, intel-gfx@lists.freedesktop.org > Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE > > Hi Sasha > > On Sun, 1 Feb 2026 at 11:15, Usyskin, Alexander > <alexander.usyskin@intel.com> 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? > > > > > > > > DG1, Alchemist and some server cards are supported by 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. > > > > > > > > Let ask gfx people. > > > > > > Cc: intel-gfx@lists.freedesktop.org > > > > > > > Rodrigo, is DRM_I915 useful on non-x86? > > > > > > No, I really don't believe it would work out. > > > > In this case the below should be good, I suppose: > > > > depends on X86 || DRM_XE!=n || COMPILE_TEST > > ... which is exactly what I added in my patch. So life's good? > From my point of view now - yes, it is reasonable. - - Thanks, Sasha ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-02-02 11:44 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <8e2646fb71b148b3d38beb13f19b14e3634a1e1a.1769541024.git.geert+renesas@glider.be>
[not found] ` <CY5PR11MB6366560330FE64F22ADF2C2EED91A@CY5PR11MB6366.namprd11.prod.outlook.com>
[not found] ` <2dd8286a-a3c7-4a3d-bd5d-011966dc07f9@app.fastmail.com>
[not found] ` <CY5PR11MB636685688893B7873C3BE85AED91A@CY5PR11MB6366.namprd11.prod.outlook.com>
[not found] ` <ab91fa38-2f5c-4237-811e-854d442a71bb@hogyros.de>
[not found] ` <CY5PR11MB63665464BE137AE70B0D47ADED9EA@CY5PR11MB6366.namprd11.prod.outlook.com>
2026-01-30 21:15 ` [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE Rodrigo Vivi
2026-02-01 10:15 ` Usyskin, Alexander
2026-02-02 9:33 ` Geert Uytterhoeven
2026-02-02 11:43 ` Usyskin, Alexander
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox