|Subject:||Re: Adding firmware to FSD|
|Date:||Sat, 9 Oct 2021 16:54:28 +0200|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Icedove/78.13.0|
David Hedlund <firstname.lastname@example.org> writes:
On 2021-10-01 20:09, Craig Topham wrote:
On 9/24/21 3:51 AM, Yuchen Pei wrote:
Hi,I think this is a good idea. Having the two wikis interlinked will bring
Does it make sense to start a collection on free firmware? One can
start by adding items appearing on say
<https://wiki.debian.org/Firmware/Open> to the directory.
If we add some info of firmware for hardware entries on h-node.org,
then the two wikis can link to each other: hardware entries on h-node
can link to firmware entries on FSD and vice versa. :)
What do you think?
more attention to both. I am not sure a new collection is necessary (at
this time). After looking at the current Collections, it seems we need
to do a little house cleaning (and hone the purpose of collections)
before we create more. If a specific h-node hardware runs on a free
firmware, then that firmware should be vetted, added to the FSD, and
linked from h-node with a link (in the description?) to h-node from the
FSD entry. Example: <https://directory.fsf.org/wiki/Das_U-Boot>
"free driver used:*ath9k_htc*" -
Could state this in addition: "Depends on non-Linux driver/firmware:
I forgot to add the link text, sorry.
Thanks for the links. Shouldn't we use the "open-ath9k-htc-firmware" name for the fsd firmware entry since that is the name of the project appearing on its repo <https://github.com/qca/open-ath9k-htc-firmware>?
It seems that there are two packages available
for the ath9k_htc is a Linux kernel driver (I linked to both
above): "Firmware is required, which can be provided by installing
the firmware-atheros package. Open
firmware for this driver is also available in the firmware-ath9k-htc package starting from
Buster. " -
|[Prev in Thread]||Current Thread||[Next in Thread]|