From: Kyle McMartin <kyle@infradead.org>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"kyle@infradead.org" <kyle@infradead.org>,
linux-firmware@kernel.org
Subject: Re: linux-firmware-i915 pull request (bxt dmc, kbl dmc)
Date: Tue, 5 Jul 2016 09:43:43 -0400 [thread overview]
Message-ID: <20160705134343.GD8680@merlin.infradead.org> (raw)
In-Reply-To: <1467415169.26811.149.camel@intel.com>
On Fri, Jul 01, 2016 at 11:20:09PM +0000, Vivi, Rodrigo wrote:
> Hi,
>
> Please consider pulling i915 updates to linux-firmware.git
>
>
> The following changes since commit
> 040c24514b94fcdbd6308d986d1bde59a704a21a:
>
> linux-firmware: intel: Update Broxton audio firmware (2016-06-29
> 14:20:20 +0530)
>
> are available in the git repository at:
>
> git://people.freedesktop.org/~vivijim/linux-firmware-i915 master
>
Pulled, thanks Rodrigo.
cheers, --Kyle
> for you to fetch changes up to
> 19b71af5326bf28fe62ac2b1607b5e18d4b0eeb6:
>
> linux-firmware/i915: Step away from symbolic links and clean up repo.
> (2016-07-01 16:07:52 -0700)
>
> ----------------------------------------------------------------
> Rodrigo Vivi (3):
> linux-firmware: New minor DMC release for Broxton - ver1_07
> linux-firmware: First DMC image for Kabylake.
> linux-firmware/i915: Step away from symbolic links and clean up
> repo.
>
> WHENCE | 14 +++++---------
> i915/bxt_dmc_ver1.bin | 2 +-
> i915/bxt_dmc_ver1_04.bin | Bin 5872 -> 0
> bytes
> i915/bxt_dmc_ver1_05.bin | Bin 5872 -> 0
> bytes
> i915/{bxt_dmc_ver1_06.bin => bxt_dmc_ver1_07.bin} | Bin 8380 -> 8380
> bytes
> i915/kbl_dmc_ver1.bin | 1 +
> i915/kbl_dmc_ver1_01.bin | Bin 0 -> 8616
> bytes
> i915/skl_dmc_ver1_23.bin | Bin 8824 -> 0
> bytes
> i915/skl_guc_ver1.bin | Bin 21 -> 109636
> bytes
> i915/skl_guc_ver1_1059.bin | Bin 109636 -> 0
> bytes
> i915/skl_guc_ver4.bin | Bin 18 -> 128320
> bytes
> i915/skl_guc_ver4_3.bin | Bin 128320 -> 0
> bytes
> 12 files changed, 7 insertions(+), 10 deletions(-)
> delete mode 100644 i915/bxt_dmc_ver1_04.bin
> delete mode 100644 i915/bxt_dmc_ver1_05.bin
> rename i915/{bxt_dmc_ver1_06.bin => bxt_dmc_ver1_07.bin} (64%)
> create mode 120000 i915/kbl_dmc_ver1.bin
> create mode 100644 i915/kbl_dmc_ver1_01.bin
> delete mode 100644 i915/skl_dmc_ver1_23.bin
> mode change 120000 => 100644 i915/skl_guc_ver1.bin
> delete mode 100644 i915/skl_guc_ver1_1059.bin
> mode change 120000 => 100644 i915/skl_guc_ver4.bin
> delete mode 100644 i915/skl_guc_ver4_3.bin
>
> Thanks,
> Rodrigo.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-05 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 23:20 linux-firmware-i915 pull request (bxt dmc, kbl dmc) Vivi, Rodrigo
2016-07-05 13:43 ` Kyle McMartin [this message]
2016-07-06 23:36 ` Vivi, Rodrigo
2016-08-02 11:04 ` Jani Nikula
2016-08-02 20:48 ` Vivi, Rodrigo
2016-08-03 0:09 ` Ben Hutchings
2016-08-03 9:08 ` Jani Nikula
2016-08-03 15:02 ` Daniel Vetter
2016-08-03 15:06 ` Vivi, Rodrigo
2016-08-03 15:08 ` Daniel Vetter
2016-08-03 15:12 ` Vivi, Rodrigo
2016-08-03 15:26 ` Daniel Vetter
2016-08-03 15:48 ` Vivi, Rodrigo
2016-08-04 18:38 ` David Weinehall
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=20160705134343.GD8680@merlin.infradead.org \
--to=kyle@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-firmware@kernel.org \
--cc=rodrigo.vivi@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