From: "Michael Büsch" <mb@bu3sch.de>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Daniel Berger <daniel@dat-berger.de>,
linux-wireless@vger.kernel.org
Subject: Re: Manual Control about Sending ACKs
Date: Wed, 22 Sep 2010 15:54:47 +0200 [thread overview]
Message-ID: <1285163687.15806.9.camel@maggie> (raw)
In-Reply-To: <201009221545.41377.chunkeey@googlemail.com> (sfid-20100922_154601_624932_FFFFFFFFD00B9F23)
On Wed, 2010-09-22 at 15:45 +0200, Christian Lamparter wrote:
> > I suspect you need to be looking at hacking firmware.
> > You might look at the open-source ar9170 firmware
> > or the b43-openfwwf project.
>
> probably not ar9170 either.
> The ACK - mechanism (response control) is mostly hardwired in
> the chip, there is not much to control here.
The ack mechanism is implemented in firmware for the b43 chip and I
think it's understood pretty much completely how ACKing works in
the firmware. So you may want to take a look at b43-openfwwf.
The guys who created b43-openfwwf also experimented with this
kind of stuff, so you might want to contact them.
--
Greetings Michael.
next prev parent reply other threads:[~2010-09-22 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 10:39 Manual Control about Sending ACKs Daniel Berger
2010-09-22 13:02 ` John W. Linville
2010-09-22 13:45 ` Christian Lamparter
2010-09-22 13:54 ` Michael Büsch [this message]
2010-09-22 17:12 ` Luis R. Rodriguez
2010-09-22 17:17 ` Ben Greear
2010-09-22 18:38 ` Daniel Berger
2010-09-23 18:56 ` AW: " Bjoern Czybik
2010-09-23 20:14 ` Daniel Berger
2010-09-22 18:50 ` Nick Kossifidis
-- strict thread matches above, loose matches on Subject: below --
2010-09-22 10:36 Daniel Berger
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=1285163687.15806.9.camel@maggie \
--to=mb@bu3sch.de \
--cc=chunkeey@googlemail.com \
--cc=daniel@dat-berger.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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 NNTP newsgroup(s).