mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2025-12-17 02:34:50 +08:00
3de1c437e75320c0d2f23dc990fac741f0bcc3ca
This fixes a variety of issues, including but not limited to:
ath9k_htc_firmware: check only the mesh control present subfield
Fix: bug in extend_tsf near 0x8000000 values
FIX: support rstamps from the future too.
Firmware sometimes returns erroneous timestamps(2)
Fixed incorrect wrapping handling in ath_extend_tsf().
Firmware sometimes returns erroneous timestamps
Added proper synchronization while handling lower 32 bit and
upper 32 bit parts in ar5416GetTsf64().
Fix resetting of txstatus flags.
Fix Array Out of Bounds in rcSibUpdate_ht()
ath9k_htc_firmware: fix the offset of CCMP header for mesh data frame
init.c: do cold reboot on exception
wmi:eadd new command WMI_REG_RMW_CMDID
remove transfer type patches for EP3 and EP4
k2_fw_usb_api: workaround for EP4 bug.
k2_fw_usb_api: prevent buffer overflow.
k2_fw_usb_api: fix typo in usb reg address
k2_fw_usb_api: add delay after mac reset
simplify STBC handling
This has been tested on both AR7010 and AR9271 devices.
Signed-off-by: Adrian Chadd <adrian@FreeBSD.org>
Signed-off-by: Kyle McMartin <kyle@kernel.org>
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.
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.
Description
Languages
TL-Verilog
67.4%
C
23.8%
Assembly
5.4%
CMake
1.2%
Python
0.9%
Other
1.3%