maximilian attems d6a18e90f8 WHENCE: link to similar config file for rtl8821a support
linux-firmware ships no config file for rtl8821a, as it seems
quite similar to rtl8821c add symlink to that config file
see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784835
(Maintainers may replace with proper file).

fixes: https://bugs.debian.org/893912

-- error
[    2.574742] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
[    2.575137] bluetooth hci0: firmware: failed to load
rtl_bt/rtl8821a_config.bin (-2)
[    2.575143] bluetooth hci0: Direct firmware load for
rtl_bt/rtl8821a_config.bin failed with error -2
[    2.575145] Bluetooth: hci0: Failed to load rtl_bt/rtl8821a_config.bin
--

-- with config file
[   26.389532] Bluetooth: hci0: RTL: rtl: examining hci_ver=06
hci_rev=000a lmp_ver=06 lmp_subver=8821

[   26.390623] Bluetooth: hci0: RTL: rom_version status=0 version=1

[   26.390624] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8821a_fw.bin

[   26.392597] bluetooth hci0: firmware: direct-loading firmware
rtl_bt/rtl8821a_fw.bin
[   26.392605] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8821a_config.bin

[   26.392748] bluetooth hci0: firmware: direct-loading firmware
rtl_bt/rtl8821a_config.bin
[   26.392757] Bluetooth: hci0: RTL: cfg_sz 10, total sz 17438
--

Cc: Max Chou <max.chou@realtek.com>
Reported-by: Kate Komi <katahipo@gmail.com>
Signed-off-by: maximilian attems <maks@stro.at>
2021-04-08 17:57:11 +02:00
2009-03-30 20:02:50 +05:30
2009-01-04 16:12:11 -08:00
2021-04-05 10:40:08 -04:00
2016-02-11 10:55:05 -08:00
2019-10-23 08:30:48 -04:00
2008-07-14 14:43:28 -07:00
2008-07-14 14:44:21 -07:00
2008-07-10 14:49:12 +01:00
2013-05-23 10:04:25 +02:00
2021-01-29 11:43:12 -08:00
2008-07-10 14:47:51 +01:00
2008-07-10 14:48:49 +01:00
2019-10-04 18:34:07 -04:00
2009-04-04 16:38:42 -07:00
2009-03-30 20:25:13 +05:30
2020-01-06 16:32:25 -05:00
2009-12-15 11:42:01 -08:00
2021-03-02 14:32:33 +01:00
2008-09-22 19:27:10 -07:00
2009-02-26 23:20:56 -08:00
2020-11-13 10:22:36 -05:00
2008-07-14 14:44:32 -07:00
2010-12-16 00:15:29 +00:00
2009-03-30 19:27:07 +05:30
2010-09-08 22:08:48 +01:00
2011-03-03 08:33:43 +00:00
2009-08-12 22:53:28 -07:00
2010-02-17 13:35:44 -08:00
2009-08-12 22:53:28 -07:00
2018-10-12 12:18:44 -04:00
2015-12-12 09:36:46 -05:00
2016-12-21 15:54:54 -05:00
2015-12-12 09:36:46 -05:00
2008-07-10 14:49:41 +01:00
2010-01-17 16:57:08 +00:00
2013-05-23 10:04:25 +02:00
2011-08-04 15:40:04 -07:00
2010-10-10 15:24:58 +01:00
2008-08-15 23:01:41 +01:00
2008-08-15 23:01:41 +01:00
2014-05-27 21:31:37 +01:00
2012-06-15 03:06:56 +01:00
2008-07-10 14:47:50 +01:00
2009-04-22 16:22:33 -07:00
2009-04-22 16:22:33 -07:00
2010-10-10 15:24:58 +01:00
2008-07-10 14:49:38 +01:00

	Linux firmware
	==============

  <http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git>

  git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

This 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 this 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.

If your commit adds new firmware, it must update the WHENCE file to
clearly state the license under which the firmware is available, and
that it is redistributable. Being redistributable includes ensuring
the firmware license provided includes an implicit or explicit
patent grant to end users to ensure full functionality of device
operation with the firmware. If the license is long and involved, it's
permitted to include it in a separate file and refer to it from the
WHENCE file ('See LICENSE.foo for details.').
And if it were possible, a changelog of the firmware itself.

Run 'make check' to check that WHENCE is consistent with the
repository contents.

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.
Description
No description provided
Readme 1.4 GiB
Languages
TL-Verilog 67.4%
C 23.8%
Assembly 5.4%
CMake 1.2%
Python 0.9%
Other 1.3%