linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Srivatsa, Anusha" <anusha.srivatsa@intel.com>
To: "linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
	"ben@decadent.org.uk" <ben@decadent.org.uk>
Subject: I915 Update - ADLS(dmc), DG1(GuC, HuC)
Date: Tue, 2 Feb 2021 00:49:22 +0000	[thread overview]
Message-ID: <6ac7d05dfec24e8abff678f47f27f6a1@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Sending some i915 updates to be pulled in upstream.

The following changes since commit 05789708b79b38eb0f1a20d8449b4eb56d39b39f:

  brcm: Link RPi4's WiFi firmware with DMI machine name. (2021-01-19 07:42:43 -0500)

are available in the Git repository at:

  git://anongit.freedesktop.org/drm/drm-firmware DG1-guc-huc-ADLS-dmc

for you to fetch changes up to 348d8a9740930e7b8bd83a36baba40c5cfc3f8be:

  i915: Add DMC v2.01 for ADL-S (2021-01-29 11:43:12 -0800)

----------------------------------------------------------------
Anusha Srivatsa (3):
      i915: Add GuC v49.0.1 for DG1
      i915: Add HuC v7.7.1 for DG1
      i915: Add DMC v2.01 for ADL-S

WHENCE                    |   9 +++++++++
i915/adls_dmc_ver2_01.bin | Bin 0 -> 18704 bytes
i915/dg1_guc_49.0.1.bin   | Bin 0 -> 311872 bytes
i915/dg1_huc_7.7.1.bin    | Bin 0 -> 582400 bytes
4 files changed, 9 insertions(+)
create mode 100644 i915/adls_dmc_ver2_01.bin
create mode 100644 i915/dg1_guc_49.0.1.bin
create mode 100644 i915/dg1_huc_7.7.1.bin


Thanks,
Anusha


[-- Attachment #2: Type: text/html, Size: 3993 bytes --]

             reply	other threads:[~2021-02-02  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  0:49 Srivatsa, Anusha [this message]
2021-02-08 13:23 ` I915 Update - ADLS(dmc), DG1(GuC, HuC) Josh Boyer
2021-02-08 15:33   ` Srivatsa, Anusha

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=6ac7d05dfec24e8abff678f47f27f6a1@intel.com \
    --to=anusha.srivatsa@intel.com \
    --cc=ben@decadent.org.uk \
    --cc=kyle@mcmartin.ca \
    --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).