From: Dave Taht <dave.taht@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [Make-wifi-fast] Diagram of the ath9k TX path
Date: Fri, 13 May 2016 13:51:42 -0700 [thread overview]
Message-ID: <CAA93jw7jDP1qcvcHfL-SikotRJ---u5toCywgrAy6z6-UP3EvA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5yYGqtQdUr1-RHgyHy5vqh6ybCUqkdUfzDkDer7B7Awg@mail.gmail.com>
And for the reason I originally cc'd ath9k-devel on this thread, was
merely that I'd wanted
to know if the diagram of the ath9k driver's current structure was
actually accurate. Is it?
http://blog.cerowrt.org/post/wifi_software_paths/
The "make-wifi-fast" mailing list exists merely because keeping up on
patch traffic on linux-wireless and elsewhere, is too difficult for
many of the people on it (including me!), and we do tend to wax and
wane on issues of more theoretical interest.
That said, I have a habit of cross-posting that comes from being an
ancient decrepit former usenet junkie where topics did engage multiple
people, and it's also a way to draw attention to the project here
It is *very* annoying in how many posts get bounced off the mailing lists...
still.... Arguing in an echo chamber is futile.
I am curious, in terms of further out reach, if there are any other
good wifi/5g/6lowpan/wireless mailing lists to be on - I'd like in
particular to find one for iwl and the mediatek chips, and if anyone
is working on fixing up the rpi3's wifi, that would be good too.
next prev parent reply other threads:[~2016-05-13 20:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871t5bpkc7.fsf@toke.dk>
2016-05-09 15:35 ` [ath9k-devel] [Make-wifi-fast] Diagram of the ath9k TX path Dave Taht
2016-05-10 2:32 ` Jonathan Morton
2016-05-10 2:59 ` Dave Taht
2016-05-10 3:30 ` Adrian Chadd
2016-05-10 4:04 ` Dave Taht
2016-05-10 4:28 ` Aaron Wood
2016-05-10 7:15 ` Adrian Chadd
2016-05-10 7:17 ` Adrian Chadd
2016-05-10 3:49 ` David Lang
2016-05-10 4:59 ` Dave Taht
2016-05-10 5:22 ` David Lang
2016-05-10 9:14 ` Toke Høiland-Jørgensen
2016-05-13 17:52 ` Bob McMahon
2016-05-13 17:49 ` Dave Taht
2016-05-13 18:05 ` Bob McMahon
2016-05-13 18:11 ` Bob McMahon
2016-05-13 18:57 ` Dave Taht
2016-05-13 19:27 ` Aaron Wood
2016-05-13 20:21 ` Dave Taht
2016-05-13 20:51 ` Dave Taht [this message]
2016-05-13 20:49 ` David Lang
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7jDP1qcvcHfL-SikotRJ---u5toCywgrAy6z6-UP3EvA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
/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.
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).