From: Christian Lamparter <chunkeey@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Daniel Berger <daniel@dat-berger.de>, linux-wireless@vger.kernel.org
Subject: Re: Manual Control about Sending ACKs
Date: Wed, 22 Sep 2010 15:45:40 +0200 [thread overview]
Message-ID: <201009221545.41377.chunkeey@googlemail.com> (raw)
In-Reply-To: <20100922130245.GC5515@tuxdriver.com>
On Wednesday 22 September 2010 15:02:45 John W. Linville wrote:
> On Wed, Sep 22, 2010 at 12:39:53PM +0200, Daniel Berger wrote:
>
> > Thus I deduce ACK sending is completely done in hardware.
>
> Yes, I believe this is the case with all of our supported hardware.
>
> > Is my conclusion and understanding right? Is there any possible solution
> > to my problem of sending ACKs manually? Would that be fast enough for
> > the SIFS and other stations' ACK timeout?
>
> 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.
next prev parent reply other threads:[~2010-09-22 13:45 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 [this message]
2010-09-22 13:54 ` Michael Büsch
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=201009221545.41377.chunkeey@googlemail.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.