From: Anusha Srivatsa <anusha.srivatsa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/2] HuC Updates
Date: Tue, 10 Sep 2019 15:42:16 -0700 [thread overview]
Message-ID: <20190910224218.389-1-anusha.srivatsa@intel.com> (raw)
The following changes since commit 6c6918ad8ae0dfb2cb591484eba525409980c16f:
linux-firmware: Update firmware file for Intel Bluetooth AX201 (2019-09-09 04:22:42 -0400)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-firmware ehl_huc
for you to fetch changes up to 44a6d7e577ca3df16d804c560de16cb8483c4306:
i915: Add HuC firmware v9.0.0 for EHL (2019-09-09 12:19:42 -0700)
----------------------------------------------------------------
Daniele Ceraolo Spurio (1):
i915: Add HuC firmware v9.0.0 for EHL
WHENCE | 3 +++
i915/ehl_huc_9.0.0.bin | Bin 0 -> 498880 bytes
2 files changed, 3 insertions(+)
create mode 100644 i915/ehl_huc_9.0.0.bin
Anusha Srivatsa (2):
drm/i915/uc: Update GuC and HuC firmware naming convention
HAX: force enable_guc=2
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 27 ++++++++++++------------
drivers/gpu/drm/i915/i915_params.h | 2 +-
2 files changed, 15 insertions(+), 14 deletions(-)
--
2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-09-10 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 22:42 Anusha Srivatsa [this message]
2019-09-10 22:42 ` [PATCH 1/2] drm/i915/uc: Update GuC and HuC firmware naming convention Anusha Srivatsa
2019-09-11 20:16 ` Daniele Ceraolo Spurio
2019-09-10 22:42 ` [PATCH 2/2] HAX: force enable_guc=2 Anusha Srivatsa
2019-09-11 0:00 ` ✗ Fi.CI.CHECKPATCH: warning for HuC Updates (rev2) Patchwork
2019-09-11 0:29 ` ✓ Fi.CI.BAT: success " Patchwork
2019-09-11 6:50 ` ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-09-09 19:27 [PATCH 0/2] HuC updates Anusha Srivatsa
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=20190910224218.389-1-anusha.srivatsa@intel.com \
--to=anusha.srivatsa@intel.com \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.