public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "kyle@infradead.org" <kyle@infradead.org>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: linux-firmware-i915 pull request
Date: Thu, 20 Aug 2015 15:42:27 +0000	[thread overview]
Message-ID: <1440085401.3879.6.camel@intel.com> (raw)

Hi,

Please consider pulling i915 updates to linux-firmware.git.

The following changes since commit
38358cfcf50436bf4462b3e45f5b30ab66bb63a6:

  firmware: tegra: Update XHCI firmware to v50.10 for T210 (2015-08-12
14:39:31 -0400)

are available in the git repository at:

  git://people.freedesktop.org/~vivijim/linux-firmware-i915 

for you to fetch changes up to
d1fa230aff5d7bd198c9697b1eee396fd66d88a4:

  linux-firmware: New major GuC release for Skylake. (2015-08-20
08:28:18 -0700)

----------------------------------------------------------------
Rodrigo Vivi (6):
      linux-firmware: New minor DMC release for Skylake - ver1_19
      linux-firmware: New minor DMC release for Broxton - ver1_05
      linux-firmware: New minor DMC release for Skylake - ver1_20
      linux-firmware: New minor DMC release for Skylake - ver1_21
      linux-firmware: Clean up i915 by removing old skl dmc firmware.
      linux-firmware: New major GuC release for Skylake.

 WHENCE                                            |  15 ++++++++++----
-
 i915/bxt_dmc_ver1.bin                             |   2 +-
 i915/bxt_dmc_ver1_05.bin                          | Bin 0 -> 5872
bytes
 i915/skl_dmc_ver1.bin                             |   2 +-
 i915/skl_dmc_ver1_04.bin                          | Bin 8048 -> 0
bytes
 i915/{skl_dmc_ver1_16.bin => skl_dmc_ver1_19.bin} | Bin 7892 -> 8380
bytes
 i915/{skl_dmc_ver1_18.bin => skl_dmc_ver1_20.bin} | Bin 7892 -> 8380
bytes
 i915/skl_dmc_ver1_21.bin                          | Bin 0 -> 8824
bytes
 i915/skl_guc_ver4.bin                             |   1 +
 i915/skl_guc_ver4_3.bin                           | Bin 0 -> 128320
bytes
 10 files changed, 13 insertions(+), 7 deletions(-)
 create mode 100644 i915/bxt_dmc_ver1_05.bin
 delete mode 100644 i915/skl_dmc_ver1_04.bin
 rename i915/{skl_dmc_ver1_16.bin => skl_dmc_ver1_19.bin} (90%)
 rename i915/{skl_dmc_ver1_18.bin => skl_dmc_ver1_20.bin} (58%)
 create mode 100644 i915/skl_dmc_ver1_21.bin
 create mode 120000 i915/skl_guc_ver4.bin
 create mode 100644 i915/skl_guc_ver4_3.bin

Thanks,
Rodrigo.
 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2015-08-20 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 15:42 Vivi, Rodrigo [this message]
2015-09-03 20:50 ` linux-firmware-i915 pull request Kyle McMartin
  -- strict thread matches above, loose matches on Subject: below --
2015-09-23 21:18 Vivi, Rodrigo
2015-09-24 15:30 ` Kyle McMartin
2015-06-20  0:35 Vivi, Rodrigo
2015-07-08  6:08 ` Timo Aaltonen
2015-07-14 21:04   ` Kyle McMartin

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=1440085401.3879.6.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kyle@infradead.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