linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Jourdan <mjourdan@baylibre.com>
To: linux-firmware@kernel.org
Cc: Jerome Brunet <jbrunet@baylibre.com>,
	linux-amlogic@lists.infradead.org,
	Neil Armstrong <narmstrong@baylibre.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Arden Jin <Arden.Jin@amlogic.com>
Subject: [GIT PULL] amlogic: add video decoder firmwares
Date: Mon, 13 May 2019 12:44:52 +0200	[thread overview]
Message-ID: <CAMO6naxcGeNWO9384OS-ijtykU-mXN71JVu=MKffZph8M3XqqA@mail.gmail.com> (raw)

Hello linux-firmware maintainers,

It's been about 7 months since the last time I sent a pull request for
the Amlogic video decoder firmwares. At the time, there were
irregularities with the license used.
We have now received a redistributable license from Amlogic for which
the contact, Arden Jin, is in Cc.
More details about the firmwares themselves can be found in the single
commit description.

Cheers,
Maxime

The following changes since commit 92e17d0dd2437140fab044ae62baf69b35d7d1fa:

  amdgpu: update vega20 to the latest 19.10 firmware (2019-05-02 06:24:19 -0400)

are available in the Git repository at:

  https://github.com/Elyotna/linux-firmware.git amlogic-vdec

for you to fetch changes up to e04cc56d0e6b6ff05924ff88fdba1a438ee7d3c8:

  amlogic: add video decoder firmwares (2019-05-13 12:00:21 +0200)

----------------------------------------------------------------
Maxime Jourdan (1):
      amlogic: add video decoder firmwares

 LICENSE.amlogic_vdec        |  15 +++++++++++++++
 WHENCE                      |  18 ++++++++++++++++++
 meson/vdec/g12a_h264.bin    | Bin 0 -> 36864 bytes
 meson/vdec/g12a_vp9.bin     | Bin 0 -> 16384 bytes
 meson/vdec/gxbb_h264.bin    | Bin 0 -> 36864 bytes
 meson/vdec/gxl_h263.bin     | Bin 0 -> 16384 bytes
 meson/vdec/gxl_h264.bin     | Bin 0 -> 36864 bytes
 meson/vdec/gxl_hevc.bin     | Bin 0 -> 16384 bytes
 meson/vdec/gxl_hevc_mmu.bin | Bin 0 -> 16384 bytes
 meson/vdec/gxl_mjpeg.bin    | Bin 0 -> 16384 bytes
 meson/vdec/gxl_mpeg12.bin   | Bin 0 -> 16384 bytes
 meson/vdec/gxl_mpeg4_5.bin  | Bin 0 -> 16384 bytes
 meson/vdec/gxm_h264.bin     | Bin 0 -> 36864 bytes
 13 files changed, 33 insertions(+)
 create mode 100644 LICENSE.amlogic_vdec
 create mode 100644 meson/vdec/g12a_h264.bin
 create mode 100644 meson/vdec/g12a_vp9.bin
 create mode 100644 meson/vdec/gxbb_h264.bin
 create mode 100644 meson/vdec/gxl_h263.bin
 create mode 100644 meson/vdec/gxl_h264.bin
 create mode 100644 meson/vdec/gxl_hevc.bin
 create mode 100644 meson/vdec/gxl_hevc_mmu.bin
 create mode 100644 meson/vdec/gxl_mjpeg.bin
 create mode 100644 meson/vdec/gxl_mpeg12.bin
 create mode 100644 meson/vdec/gxl_mpeg4_5.bin
 create mode 100644 meson/vdec/gxm_h264.bin

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

             reply	other threads:[~2019-05-13 10:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 10:44 Maxime Jourdan [this message]
2019-05-14 11:33 ` [GIT PULL] amlogic: add video decoder firmwares Josh Boyer
2019-05-14 12:21   ` Maxime Jourdan

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='CAMO6naxcGeNWO9384OS-ijtykU-mXN71JVu=MKffZph8M3XqqA@mail.gmail.com' \
    --to=mjourdan@baylibre.com \
    --cc=Arden.Jin@amlogic.com \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-firmware@kernel.org \
    --cc=narmstrong@baylibre.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 NNTP newsgroup(s).