linux-firmware/carl9170fw
Konrad Weihmann eaee2dacc2
Makefile: replace mkdir by install
mkdir -p creates paths that are bound to user's settings and therefore
can lead to different file mode bits of the base paths accross different
machines.
Use install instead, as this tool is not prone to such behavior.

Signed-off-by: Konrad Weihmann <kweihmann@outlook.com>
Signed-off-by: Josh Boyer <jwboyer@kernel.org>
2022-05-31 12:57:56 -04:00
..
carlfw Remove executable permissions from firmware files 2014-01-27 00:49:23 +00:00
config linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
extra carl9170: Fix minimum CMake version 2013-01-14 10:55:27 +00:00
include linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
minifw linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
toolchain Makefile: replace mkdir by install 2022-05-31 12:57:56 -04:00
tools linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
CMakeLists.txt linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
COPYRIGHT linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
GPL linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
Kconfig linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
README linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
autogen.sh Revert "carl9170: Add checksum during installation, as preferred by the driver" 2013-01-17 21:15:48 +00:00
genapi.sh linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00

README

Community AR9170 Linux firmware
-----------------------

This is the firmware for the Atheros ar9170 802.11n devices.

To build the firmware you will need an SH-2 toolchain.
You can build your own toolchain:

make -C toolchain

but be aware that this will take some time and requires
about 1.2 GiB disk space.

The resulting firmware, carl9170.fw, can be used only
with the carl9170 Linux driver.

After getting a toolchain, you will need to get more
tools & libs:

 * gcc 4.4+

 * gperf, bison/flex

 * cmake 2.8.0+

 * libusb 1.0+

 * SDL SDK 1.2.13+

afterwards, simply execute:

autogen.sh

to start the configuration and build process.

if you want to "install" your own firmware, you can either
do this manually, or by executing:
 
autogen.sh install

This will place a copy with the right filename [adds API rev]
into /lib/firmware/[the default path on most Distributions].