Commit Graph

14 Commits

Author SHA1 Message Date
coolcuber
a96b9b6cb6 ath9k-htc-blobless-firmware-unstable: fix version 2026-07-28 18:28:26 -04:00
Sandro
61cea1405d ath9k-htc-blobless-firmware-{unstable}: fix cmake 4 error (#457087) 2025-11-07 18:25:48 +00:00
Rafael Ieda
cdc8050f8e treewide: mark as broken on darwin (last successful Hydra build in 2024) 2025-11-05 12:57:40 -03:00
Guy Chronister
5a3445b59a ath9k-htc-blobless-firmware,ath9k-htc-blobless-firmware-unstable: fix cmake 4 error 2025-10-30 15:35:41 -05:00
jopejoe1
61d0373a40 lib.licenses: replace classpath license with exception
The GPL-2.0-with-classpath-exception is deprecated in spdx and the exception Classpath-exception-2.0 should be used instead.
Other Classpath license hace also benn replaced with it.
2025-08-31 16:19:22 +02:00
Wolfgang Walther
5a0711127c treewide: run nixfmt 1.0.0 2025-07-24 13:55:40 +02:00
Atemu
472eb192b0 ath9k: fix build of old gmp by disabling compiler warnings 2025-05-18 15:37:06 +02:00
Winter
a19cd4ffb1 Revert "treewide: replace rev with tag"
This reverts commit 65a333600d.

This wasn't tested for correctness with something like fodwatch [0],
and should not have been (self-)merged so quickly, especially without
further review.

It also resulted in the breakage of at least one package [1] (and that's
the one we know of and was caught).

A few packages that were updated in between this commit and this revert
were not reverted back to using `rev`, but other than that, this is a
1:1 revert.

[0]: https://codeberg.org/raphaelr/fodwatch
[1]: https://github.com/NixOS/nixpkgs/pull/396904 / 758551e458
2025-04-08 02:57:25 -04:00
Pol Dellaiera
65a333600d treewide: replace rev with tag 2025-04-07 16:57:22 +02:00
Silvan Mosberger
4f0dadbf38 treewide: format all inactive Nix files
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.

Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.

A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.

This commit was automatically created and can be verified using

    nix-build a08b3a4d19.tar.gz \
      --argstr baseRev b32a094368
    result/bin/apply-formatting $NIXPKGS_PATH
2024-12-10 20:26:33 +01:00
rnhmjoj
cc065fe18a ath9k-htc-blobless-firmware: use name expected by the kernel
The kernel asks for the firmware with the version string in the filename[1], so
it's not easy to load the "blobs" from this package.
With this change you can just add the package with a `lib.hiPrio` to
`hardware.firmware` and it will be loaded correctly.

Note: I used symlinks instead of simply renaming the files in order to not
introduce a breaking change.
2023-06-23 14:39:07 +02:00
Artturin
f9fdf2d402 treewide: move NIX_CFLAGS_COMPILE to the env attrset
with structuredAttrs lists will be bash arrays which cannot be exported
which will be a issue with some patches and some wrappers like cc-wrapper

this makes it clearer that NIX_CFLAGS_COMPILE must be a string as lists
in env cause a eval failure
2023-02-22 21:23:04 +02:00
sternenseemann
6c8644fc37 ath9k-htc-blobless-firmware: fix evaluation with Nix 2.3
Path interpolation is not available in all Nix versions nixpkgs supports
2023-01-11 16:28:28 +01:00
Adam Joseph
7af47c9877 ath9k-htc-blobless-firmware: init at 1.4.0
This firmware is completely open source with no blobs, which is
quite rare in the wifi world.  Wifi chips have their own dedicated
general-purpose CPUs.  This source code allows you to see what those
CPUs are doing and modify their behavior.

When the upstream repository was created in 2013, "open source
firmware" meant "firmware which is open source".  In 2023 that is no
longer the generally accepted [definition], so I have chosen an
unambiguous adjective (whose meaning has remained stable for
decades) to use in the pname.

[definition]: https://web.archive.org/web/20221209121315/https://www.opencompute.org/projects/open-system-firmware#:~:text=Another,allows%20it

Co-authored-by: Artturi <Artturin@artturin.com>
2023-01-09 16:10:04 -08:00