[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Adding firmware to FSD
From: |
Yuchen Pei |
Subject: |
Re: Adding firmware to FSD |
Date: |
Tue, 12 Oct 2021 07:44:33 +1100 |
User-agent: |
K-9 Mail for Android |
On 11 October 2021 21:37:55 GMT+11:00, David Hedlund <public@beloved.name>
wrote:
>
>On 2021-10-11 11:43, Yuchen Pei wrote:
>>
>> Yuchen Pei <hi@ypei.me> writes:
>>
>>> David Hedlund <public@beloved.name> writes:
>>>
>>>>>
>>>> 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
>>>> <https://packages.debian.org/firmware-atheros> package. Open
>>>> firmware
>>>> <https://wiki.debian.org/ath9k_htc/open_firmware> for this driver is
>>>> also available in the firmware-ath9k-htc
>>>> <https://packages.debian.org/firmware-ath9k-htc> package starting
>>>> from
>>>> Buster. " - https://wiki.debian.org/ath9k_htc
>>>>
>>>> https://packages.debian.org/source/stable/open-ath9k-htc-firmware is
>>>> the
>>>> source package used to build
>>>> https://packages.debian.org/bullseye/firmware-ath9k-htc
>>>
>>> Thanks. A problem with using the debian name is other distros may use
>>> different names. For example the guix package of the same firmware is
>>> called ath9k-htc-firmware[1]. This is why I think using the
>>> "official" name is better. Perhaps there's a way in an FSD entry to
>>> map a piece of software to corresponding packages in various distros?
>>>
>>> [1] https://guix.gnu.org/en/packages/ath9k-htc-firmware-1.4.0/
>>>
>>> Not sure if this has been discussed before, but regarding John's
>>> remark, this firmware, together with many others are in the
>>> linux-firmware repo[2], which seems to be not part of the kernel, so
>>> perhaps it makes sense to add it to FSD:
>>>
>>> [2]
>>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENCE.open-ath9k-htc-firmware
>>>
>>>
>>> BTW, I'm not sure if the email address info@h-node.com is still used
>>> by anyone. If you feel like a message is relevant to h-node, please
>>> cc h-source-users@nongnu.org instead. That is the mailing list we are
>>> using for h-node.org and h-source (the server application of
>>> h-node.org).
>>
>> I just added <https://directory.fsf.org/wiki/Open-ath9k-htc-firmware>.
>>
>I redirected it to https://directory.fsf.org/wiki/Firmware-ath9k-htc
>because it will be imported later anyway. Thanks.
I guess you are talking about importing using the directory script. I'm still
not sure it is a good idea to adhere to the Debian naming. The scripts should
work for the directory, not the other way around. What if Debian changes the
name of a package? What if we decide to import from guix as well? I imagine
it is also not hard to write some post processing script to edit names of some
packages.
How about we make
Firmware-ath9k-htc (and names of the same package in other distros) redirect to
open-ath9-htc-firmware?
As aside, how often does the script run and what was the last time it was run?
- Re: Adding firmware to FSD, (continued)
Re: Adding firmware to FSD, David Hedlund, 2021/10/08
- Re: Adding firmware to FSD, Yuchen Pei, 2021/10/09
- Re: Adding firmware to FSD, David Hedlund, 2021/10/09
- Re: Adding firmware to FSD, David Hedlund, 2021/10/09
- Re: Adding firmware to FSD, Yuchen Pei, 2021/10/11
- Re: Adding firmware to FSD, Yuchen Pei, 2021/10/11
- Re: Adding firmware to FSD, David Hedlund, 2021/10/11
- Re: Adding firmware to FSD,
Yuchen Pei <=
Re: Adding firmware to FSD, David Hedlund, 2021/10/11
Re: Adding firmware to FSD, David Hedlund, 2021/10/11
Re: Adding firmware to FSD, Yuchen Pei, 2021/10/11
Re: Adding firmware to FSD, Ron Nazarov, 2021/10/15
Re: Adding firmware to FSD, Yuchen Pei, 2021/10/15