linux-firmware/carl9170fw
Ben Hutchings 9f43b7a6b0 carl9170: Add and check SHA-256 sums for the toolchain tarballs
The sums for binutils and gcc are based on an HTTPS download (instead
of the default HTTP).

newlib doesn't seem to be available with any kind of signature, so I
compared a tarball and CVS checkout; let's hope they weren't both
compromised.

Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2013-01-14 11:02:57 +00:00
..
carlfw linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +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 carl9170: Add and check SHA-256 sums for the toolchain tarballs 2013-01-14 11:02:57 +00:00
tools linux-firmware: add carl9170 firmware 2013-01-14 02:20:40 +00:00
autogen.sh 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
genapi.sh 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

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].