Files
linux/firmware
shihong.zheng 4bdc7e4ff3 H265: fix output frame latancy [1/1]
PD#IPTV-347

Problem:
output frame latancy when run videophonetest.

Solution:
sps_max_dec_pic_buffering_minus1_0 to
get buf num when sps_num_reorder_pics_0 is 0.
ucode gerrit id: 56487

Verify:
need verify by u212 iptv code

Change-Id: I199c45ee48ba4c535d0303347af27f9a572ed2c8
Signed-off-by: shihong.zheng <shihong.zheng@amlogic.com>
2019-07-23 17:52:49 +09:00
..
2009-01-04 16:12:11 -08:00
2011-03-14 15:00:12 -07:00
2011-03-31 17:03:36 -07:00
2008-07-14 14:43:28 -07:00
2008-07-10 14:49:12 +01:00
2008-07-10 14:47:51 +01:00
2008-07-10 14:48:49 +01:00
2009-04-04 16:38:42 -07:00
2009-03-30 20:25:13 +05:30
2009-08-31 09:09:30 +10:00
2008-09-22 19:27:10 -07:00
2009-02-26 23:20:56 -08:00
2008-07-14 14:44:32 -07:00
2009-03-30 19:27:07 +05:30

	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.