Would it be possible to tag a release at some point after d0ad09603867beab49ead2536b2239be43d6eb42 and 29426f31458682304dee9f2da0f1e9e60237018f?
I have packagedopen-ath9k-htc-firmware for nixpkgs. Nixpkgs generally doesn't provide software until upstream (i.e. you) have assigned it a release name/number/identifier. Unfortunately at the moment the latest tagged release, 1.4.0, uses a very old version of gcc that doesn't work well on powerpc64le or aarch64. It also doesn't include cryptographic hashes for the toolchain sources. The latest git HEAD doesn't have either of these problems, and works quite well!
Thank you so much for providing this. I can only try to imagine the superhuman patience and political skill it must have taken to get a major semiconductor design firm to release firmware source like this (although I have heard that Atheros Communications was an unusually enlightened company).
Would it be possible to tag a release at some point after d0ad09603867beab49ead2536b2239be43d6eb42 and 29426f31458682304dee9f2da0f1e9e60237018f?
I have packaged
open-ath9k-htc-firmwarefor nixpkgs. Nixpkgs generally doesn't provide software until upstream (i.e. you) have assigned it a release name/number/identifier. Unfortunately at the moment the latest tagged release, 1.4.0, uses a very old version of gcc that doesn't work well on powerpc64le or aarch64. It also doesn't include cryptographic hashes for the toolchain sources. The latest git HEAD doesn't have either of these problems, and works quite well!Thank you so much for providing this. I can only try to imagine the superhuman patience and political skill it must have taken to get a major semiconductor design firm to release firmware source like this (although I have heard that Atheros Communications was an unusually enlightened company).