From: Josh Boyer <jwboyer@kernel.org>
To: John.C.Harrison@intel.com
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Kyle McMartin <kyle@kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
Linux Firmware <linux-firmware@kernel.org>
Subject: Re: [Intel-gfx] linux firmware PR for i915 GuC v49.0.1
Date: Mon, 30 Nov 2020 09:26:25 -0500 [thread overview]
Message-ID: <CA+5PVA5n3C3fzTrLWLAmjqdjnVzxN2ae+fZDRS5Qbqj3UG+iKw@mail.gmail.com> (raw)
Message-ID: <20201130142625.yXJ1cM_Dsy-AHao0zLF4v0Vgn0e7hE6Co04iiYogGUk@z> (raw)
In-Reply-To: <20201125014214.3772152-1-John.C.Harrison@Intel.com>
On Tue, Nov 24, 2020 at 8:42 PM <John.C.Harrison@intel.com> wrote:
>
> Hi Josh, Kyle, Ben,
>
> Kindly add the below i915 changes to linux-firmware.git:
>
>
> The following changes since commit b362fd4cb8963ad75517dbcf424974f65a29a60e:
>
> Mellanox: Add new mlxsw_spectrum firmware xx.2008.2018 (2020-11-24 09:55:03 -0500)
>
> are available in the Git repository at:
>
> git://anongit.freedesktop.org/drm/drm-firmware FDO/guc_v49
This doesn't exist. Git complains with:
fatal: couldn't find remote ref FDO/guc_v49
Did you just mean guc_v49?
josh
>
> for you to fetch changes up to c487f7dadcd21116613441ed355b764003b3f57b:
>
> i915: Add GuC firmware v49.0.1 for all platforms (2020-11-24 17:04:17 -0800)
>
> ----------------------------------------------------------------
> John Harrison (2):
> i915: Remove duplicate KBL DMC entry
> i915: Add GuC firmware v49.0.1 for all platforms
>
> WHENCE | 25 ++++++++++++++++++++++++-
> i915/bxt_guc_49.0.1.bin | Bin 0 -> 196224 bytes
> i915/cml_guc_49.0.1.bin | Bin 0 -> 197184 bytes
> i915/ehl_guc_49.0.1.bin | Bin 0 -> 324160 bytes
> i915/glk_guc_49.0.1.bin | Bin 0 -> 196672 bytes
> i915/icl_guc_49.0.1.bin | Bin 0 -> 324160 bytes
> i915/kbl_guc_49.0.1.bin | Bin 0 -> 197184 bytes
> i915/skl_guc_49.0.1.bin | Bin 0 -> 196288 bytes
> i915/tgl_guc_49.0.1.bin | Bin 0 -> 321792 bytes
> 9 files changed, 24 insertions(+), 1 deletion(-)
> create mode 100644 i915/bxt_guc_49.0.1.bin
> create mode 100644 i915/cml_guc_49.0.1.bin
> create mode 100644 i915/ehl_guc_49.0.1.bin
> create mode 100644 i915/glk_guc_49.0.1.bin
> create mode 100644 i915/icl_guc_49.0.1.bin
> create mode 100644 i915/kbl_guc_49.0.1.bin
> create mode 100644 i915/skl_guc_49.0.1.bin
> create mode 100644 i915/tgl_guc_49.0.1.bin
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-11-30 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 1:42 linux firmware PR for i915 GuC v49.0.1 John.C.Harrison
2020-11-25 1:42 ` [Intel-gfx] " John.C.Harrison
2020-11-30 14:26 ` Josh Boyer [this message]
2020-11-30 14:26 ` Josh Boyer
2020-11-30 18:49 ` John Harrison
2020-11-30 18:49 ` [Intel-gfx] " John Harrison
2020-11-30 19:09 ` Josh Boyer
2020-11-30 19:09 ` [Intel-gfx] " Josh Boyer
2020-11-30 19:15 ` John Harrison
2020-11-30 19:15 ` [Intel-gfx] " John Harrison
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=CA+5PVA5n3C3fzTrLWLAmjqdjnVzxN2ae+fZDRS5Qbqj3UG+iKw@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=John.C.Harrison@intel.com \
--cc=ben@decadent.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kyle@kernel.org \
--cc=linux-firmware@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).