mirror of
https://github.com/hardkernel/linux.git
synced 2026-06-10 21:07:02 +09:00
24e759113f
PD#SWPL-520 Problem: tl1 bringup changes Solution: 1. add tl1 cpu type 2. hevc decoder support 8k 3. replace get_cpu_type() with get_cpu_major_id() ucode commitid: d9582c3a6697c25d81b706d41d20d8908158ef9f Change-Id: Iac3a5f20698277d3f7f500fba6a27b88f6ac5839 Verify: p212, w400 Change-Id: Iac3a5f20698277d3f7f500fba6a27b88f6ac5839 Signed-off-by: shihong.zheng <shihong.zheng@amlogic.com>
DO NOT ADD FIRMWARE TO THIS DIRECTORY.
======================================
This directory is only here to contain firmware images extracted from old
device drivers which predate the common use of request_firmware().
As we update those drivers to use request_firmware() and keep a clean
separation between code and firmware, we put the extracted firmware
here.
This directory is _NOT_ for adding arbitrary new firmware images. The
place to add those is the separate linux-firmware repository:
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
That repository contains all these firmware images which have been
extracted from older drivers, as well various new firmware images which
we were never permitted to include in a GPL'd work, but which we _have_
been permitted to redistribute under separate cover.
To submit firmware to that repository, please send either a git binary
diff or preferably a git pull request to:
linux-firmware@kernel.org
and also cc: to related mailing lists.
Your commit should include an update to the WHENCE file clearly
identifying the licence under which the firmware is available, and
that it is redistributable. If the licence is long and involved, it's
permitted to include it in a separate file and refer to it from the
WHENCE file.
And if it were possible, a changelog of the firmware itself.
Ideally, your commit should contain a Signed-Off-By: from someone
authoritative on the licensing of the firmware in question (i.e. from
within the company that owns the code).
WARNING:
=======
Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or
request. Otherwise your firmware _will never be accepted_.
Maintainers are really busy, so don't expect a prompt reply.