8053 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
..
3com beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
acenic beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
adaptec beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
advansys beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
av7110 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
bnx2 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
bnx2x beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
cis beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
cpia2 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
cxgb3 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
dsp56k beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
e100 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
edgeport beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
emi26 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
emi62 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
ess beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
kaweth beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
keyspan beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
keyspan_pda beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
korg beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
matrox beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
myricom beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
ositech beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
qlogic beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
r128 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
radeon beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
sb16 beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
sun beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
tehuti beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
tigon beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
ttusb-budget beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
vicam beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
yam beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
yamaha beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
.gitignore beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
.ihex2fw.cmd beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
Makefile beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
README.AddingFirmware beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
WHENCE beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
atmsar11.HEX beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
ihex2fw.c beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
mts_cdma.fw.ihex beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
mts_edge.fw.ihex beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
mts_gsm.fw.ihex beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
ti_3410.fw.ihex beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
ti_5052.fw.ihex beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
whiteheat.HEX beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
whiteheat_loader.HEX beefd0184a 2022-08-08 ct_chen 2 vuotta sitten
whiteheat_loader_debug.HEX beefd0184a 2022-08-08 ct_chen 2 vuotta sitten

README.AddingFirmware


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.