From: Josh Boyer <jwboyer@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-firmware@kernel.org, Wentong Wu <wentong.wu@intel.com>
Subject: Re: [GIT PULL] Intel Visual Sensing Controller firmware
Date: Tue, 26 Dec 2023 14:40:38 -0500 [thread overview]
Message-ID: <CA+5PVA6S5XG+DwLdDHX00W3VjAx_kvAPLx6HKJBxjCgh250Lkg@mail.gmail.com> (raw)
In-Reply-To: <ZYC2sqDmHb3jiI9I@kekkonen.localdomain>
On Mon, Dec 18, 2023 at 4:16 PM Sakari Ailus
<sakari.ailus@linux.intel.com> wrote:
>
> Hi folks,
>
> This PR adds firmware binaries for Intel Visual Sensing Controller (VSC).
> The driver for the device has been recently merged to the char-misc tree
> and is expected to make it to Linux 6.8.
>
> Please pull.
>
>
> The following changes since commit c156e6be6d4a0a2290e7059bc74fb0612aa19693:
>
> Merge branch 'robot/pr-0-1702625169' into 'main' (2023-12-15 12:16:57 +0000)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/sailus/linux-firmware.git tags/ivsc-2023-12-18
Pulled and pushed out.
https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/101
josh
>
> for you to fetch changes up to cfc997c664f076c6800b749ed7ef315b1e8e76fd:
>
> intel: vsc: Add firmware for Visual Sensing Controller (2023-12-18 22:59:39 +0200)
>
> ----------------------------------------------------------------
> Add Intel Visual Sensing Controller firmware
>
> ----------------------------------------------------------------
> Sakari Ailus (1):
> intel: vsc: Add firmware for Visual Sensing Controller
>
> LICENSE.ivsc | 38 +++++++++++++++++++++++++++++++++
> WHENCE | 36 +++++++++++++++++++++++++++++++
> intel/vsc/ivsc_fw.bin | Bin 0 -> 966560 bytes
> intel/vsc/ivsc_pkg_hi556_0.bin | Bin 0 -> 767068 bytes
> intel/vsc/ivsc_pkg_himx11b1_0.bin | Bin 0 -> 730204 bytes
> intel/vsc/ivsc_pkg_himx2170_0.bin | Bin 0 -> 771164 bytes
> intel/vsc/ivsc_pkg_himx2172_0.bin | Bin 0 -> 799836 bytes
> intel/vsc/ivsc_pkg_int3537_0.bin | Bin 0 -> 767068 bytes
> intel/vsc/ivsc_pkg_ovti01a0_0.bin | Bin 0 -> 726108 bytes
> intel/vsc/ivsc_pkg_ovti01af_0.bin | Bin 0 -> 726108 bytes
> intel/vsc/ivsc_pkg_ovti01as_0.bin | Bin 0 -> 726108 bytes
> intel/vsc/ivsc_pkg_ovti02c1_0.bin | Bin 0 -> 762972 bytes
> intel/vsc/ivsc_pkg_ovti02e1_0.bin | Bin 0 -> 791644 bytes
> intel/vsc/ivsc_pkg_ovti2740_0.bin | Bin 0 -> 726108 bytes
> intel/vsc/ivsc_pkg_ovti5678_0.bin | Bin 0 -> 726108 bytes
> intel/vsc/ivsc_pkg_ovti9734_0.bin | Bin 0 -> 730204 bytes
> intel/vsc/ivsc_pkg_ovti9738_0.bin | Bin 0 -> 730204 bytes
> intel/vsc/ivsc_skucfg_hi556_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_himx11b1_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_himx2170_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_himx2172_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_int3537_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti01a0_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti01af_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti01as_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti02c1_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti02e1_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti2740_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti5678_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti9734_0_1.bin | Bin 0 -> 4100 bytes
> intel/vsc/ivsc_skucfg_ovti9738_0_1.bin | Bin 0 -> 4100 bytes
> 31 files changed, 74 insertions(+)
> create mode 100644 LICENSE.ivsc
> create mode 100644 intel/vsc/ivsc_fw.bin
> create mode 100644 intel/vsc/ivsc_pkg_hi556_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_himx11b1_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_himx2170_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_himx2172_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_int3537_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti01a0_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti01af_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti01as_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti02c1_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti02e1_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti2740_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti5678_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti9734_0.bin
> create mode 100644 intel/vsc/ivsc_pkg_ovti9738_0.bin
> create mode 100644 intel/vsc/ivsc_skucfg_hi556_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_himx11b1_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_himx2170_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_himx2172_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_int3537_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti01a0_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti01af_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti01as_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti02c1_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti02e1_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti2740_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti5678_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti9734_0_1.bin
> create mode 100644 intel/vsc/ivsc_skucfg_ovti9738_0_1.bin
>
> --
> Kind regards,
>
> Sakari Ailus
prev parent reply other threads:[~2023-12-26 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:16 [GIT PULL] Intel Visual Sensing Controller firmware Sakari Ailus
2023-12-26 19:40 ` Josh Boyer [this message]
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=CA+5PVA6S5XG+DwLdDHX00W3VjAx_kvAPLx6HKJBxjCgh250Lkg@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=wentong.wu@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).