From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Jacob K <jacobk@disroot.org>, 57269@debbugs.gnu.org
Subject: bug#57269: [rtl8812au-aircrack-ng-linux-module] Missing Source for hal/rtl8812a/hal8812a_fw.c (and probably other files ending in fw.c)
Date: Fri, 19 Aug 2022 16:23:49 -0400 [thread overview]
Message-ID: <87o7wghtii.fsf@gmail.com> (raw)
In-Reply-To: <87y1vl1v3y.fsf@nckx> (Tobias Geerinckx-Rice's message of "Thu, 18 Aug 2022 16:23:30 +0200")
Hi,
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Hi Jacob,
>
> Jacob K via Bug reports for GNU Guix 写道:
>> Files such as hal8812a_fw.c [1] have large arrays that seem to be
>> binary
>> firmware encoded in text. My understanding is that source code is
>> not
>> available, so I believe the files are nonfree software,
>
> Even if free source code exists, we should still remove the blobs and
> build our own. (Yes, we actually do this for other firmware :-)
>
>> the short-term at least, be removed from Guix. Long term it would be
>> good to get the source code (via reverse engineering or asking
>> Realtek),
>> but I imagine that would take a significant amount of time and
>> effort (I
>> do have a Realtek USB Wi-Fi card, maybe not with this exact firmware
>> though.).
>
> Unfortunately all correct. Another blow to wireless networking with
> Guix. Attached is a patch removing the rtl8821ce-linux-module and
> rtl8812au-aircrack-ng-linux-module packages.
Ouch. There goes the tiny WiFi dongle I liked on my x200 :-). Can we
report this upstream, so that it's at least documented and opens the
door for an eventual resolution?
> I didn't apply it yet. Since this case, unlike some others, appears
> to be straightforward, I don't intend to wait long.
Fine by me (without the lol part).
Maxim
next prev parent reply other threads:[~2022-08-19 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 1:12 bug#57269: [rtl8812au-aircrack-ng-linux-module] Missing Source for hal/rtl8812a/hal8812a_fw.c (and probably other files ending in fw.c) Jacob K via Bug reports for GNU Guix
2022-08-18 14:23 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-18 15:04 ` Jack Hill
2022-08-19 20:23 ` Maxim Cournoyer [this message]
2022-08-27 15:47 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7wghtii.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=57269@debbugs.gnu.org \
--cc=jacobk@disroot.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).