From: "Das, Nirmoy" <nirmoy.das@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Fei Yang <fei.yang@intel.com>
Cc: Lucas Martins De Marchi <lucas.demarchi@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [Intel-gfx] [PATCH 0/2] Restore MTL boot
Date: Mon, 24 Apr 2023 18:16:33 +0200 [thread overview]
Message-ID: <3545d4c8-08ef-7382-d25f-0c16e256eb63@intel.com> (raw)
In-Reply-To: <20230424160913.19886-1-andi.shyti@linux.intel.com>
On 4/24/2023 6:09 PM, Andi Shyti wrote:
> Hi,
>
> The two patches reverted in this series are, together, preventing
> MTL from booting.
>
> Revert them until the fix is deployed.
>
> Andi
>
> Andi Shyti (2):
> Revert "drm/i915/mtl: fix mocs selftest"
> Revert "drm/i915/mtl: Define MOCS and PAT tables for MTL"
Series is Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
>
> drivers/gpu/drm/i915/gt/intel_gt_regs.h | 6 +--
> drivers/gpu/drm/i915/gt/intel_gtt.c | 47 +----------------
> drivers/gpu/drm/i915/gt/intel_gtt.h | 8 ---
> drivers/gpu/drm/i915/gt/intel_mocs.c | 70 +------------------------
> drivers/gpu/drm/i915/gt/selftest_mocs.c | 3 +-
> 5 files changed, 4 insertions(+), 130 deletions(-)
>
next prev parent reply other threads:[~2023-04-24 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 16:09 [Intel-gfx] [PATCH 0/2] Restore MTL boot Andi Shyti
2023-04-24 16:09 ` [Intel-gfx] [PATCH 1/2] Revert "drm/i915/mtl: fix mocs selftest" Andi Shyti
2023-04-25 6:25 ` Andrzej Hajda
2023-04-24 16:09 ` [Intel-gfx] [PATCH 2/2] Revert "drm/i915/mtl: Define MOCS and PAT tables for MTL" Andi Shyti
2023-04-25 6:25 ` Andrzej Hajda
2023-04-24 16:16 ` Das, Nirmoy [this message]
2023-04-24 23:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Restore MTL boot (rev2) Patchwork
2023-04-25 0:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-25 6:19 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=3545d4c8-08ef-7382-d25f-0c16e256eb63@intel.com \
--to=nirmoy.das@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fei.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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