From: "Mani, Rajmohan" <rajmohan.mani@intel.com>
To: "linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"Zheng, Jian Xu" <jian.xu.zheng@intel.com>,
"tfiga@chromium.org" <tfiga@chromium.org>,
"Toivonen, Tuukka" <tuukka.toivonen@intel.com>,
"Zhi, Yong" <yong.zhi@intel.com>
Subject: [GIT PULL] linux-firmware: intel: Add Kabylake IPU3 firmware
Date: Sat, 5 Aug 2017 00:04:26 +0000 [thread overview]
Message-ID: <6F87890CF0F5204F892DEA1EF0D77A59725E1A1D@FMSMSX114.amr.corp.intel.com> (raw)
Hi,
Please review this PULL request to add Kabylake IPU3 firmware to the linux-firmware repository.
The following changes since commit 7d2c913dcd1be083350d97a8cb1eba24cfacbc8a:
ath10k: update year in license (2017-06-22 12:06:02 -0700)
are available in the git repository at:
https://github.com/RajmohanMani/linux-firmware.git tags/v1
for you to fetch changes up to 2c27b0cb02f18c022d8378e0e1abaf8b7ae8188f:
linux-firmware: intel: Add Kabylake IPU3 firmware (2017-08-04 15:53:13 -0700)
----------------------------------------------------------------
IPU3 firmware version irci_irci_ecr-master_20161208_0213_20170112_1500
----------------------------------------------------------------
Rajmohan Mani (1):
linux-firmware: intel: Add Kabylake IPU3 firmware
LICENSE.ipu3_firmware | 36 ++++++++++++++++++++++++++++++++++++
WHENCE | 11 +++++++++++
intel/ipu3-fw.bin | 1 +
intel/irci_irci_ecr-master_20161208_0213_20170112_1500.bin | Bin 0 -> 1212984 bytes
4 files changed, 48 insertions(+)
create mode 100644 LICENSE.ipu3_firmware
create mode 120000 intel/ipu3-fw.bin
create mode 100644 intel/irci_irci_ecr-master_20161208_0213_20170112_1500.bin
Thanks
Raj
next reply other threads:[~2017-08-05 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 0:04 Mani, Rajmohan [this message]
2017-08-15 11:32 ` [GIT PULL] linux-firmware: intel: Add Kabylake IPU3 firmware Tomasz Figa
2017-08-23 14:50 ` Tomasz Figa
2017-08-23 16:47 ` Kyle McMartin
2017-08-23 18:45 ` Mani, Rajmohan
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=6F87890CF0F5204F892DEA1EF0D77A59725E1A1D@FMSMSX114.amr.corp.intel.com \
--to=rajmohan.mani@intel.com \
--cc=jian.xu.zheng@intel.com \
--cc=linux-firmware@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=tuukka.toivonen@intel.com \
--cc=yong.zhi@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 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.