From: "Jouni Malinen" <jkm@devicescape.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] d80211: Add API to generate RTS and CTS-to-self frames
Date: Mon, 5 Feb 2007 08:47:38 -0800 [thread overview]
Message-ID: <20070205164738.GA31058@instant802.com> (raw)
In-Reply-To: <200702051628.46518.mb@bu3sch.de>
On Mon, Feb 05, 2007 at 04:28:46PM +0100, Michael Buesch wrote:
> As I said in response to Johannes' comment, if a driver needs just
> the duration, we should export the functions to calculate it
> and remove the calculation from the tx_control and the tx_control
> setup path.
In that case, I would like to see this change being included in the same
patch/patchset.. Without this, I can only NAK this kind of change since
it removes functionality needed for some designs and that is not
something I would like to see happening with net/d80211 since the goal
is to allow all reasonable hardware designs to work with it.
> Currently there is no driver using it, so I simply removed it.
There are, but maybe not in wireless-dev.git.
> BTW: Which cards need the duration, but not the whole frame?
Any card that supports different transmit rates for hw retries involving
RTS/CTS/fragmentation (e.g., Atheros).
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-02-05 17:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 13:12 [PATCH] d80211: Add API to generate RTS and CTS-to-self frames Michael Buesch
2007-02-05 13:14 ` [PATCH] bcm43xx-d80211: Use d80211 API to generate RTS/CTS frames Michael Buesch
2007-02-05 13:15 ` [PATCH] rt2x00-d80211: " Michael Buesch
2007-02-05 13:31 ` [PATCH] d80211: Add API to generate RTS and CTS-to-self frames Michael Buesch
2007-02-05 13:43 ` Johannes Berg
2007-02-05 13:53 ` Michael Buesch
2007-02-05 14:58 ` Jouni Malinen
2007-02-05 15:28 ` Michael Buesch
2007-02-05 16:47 ` Jouni Malinen [this message]
2007-02-05 16:53 ` Michael Buesch
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=20070205164738.GA31058@instant802.com \
--to=jkm@devicescape.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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.