From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jkm@devicescape.com>
Cc: netdev@vger.kernel.org, Simon Barber <simon@devicescape.com>,
Jiri Benc <jbenc@suse.cz>
Subject: Re: [clarification request] ieee80211_tx_control.pkt_type
Date: Fri, 18 Aug 2006 16:50:48 +0200 [thread overview]
Message-ID: <1155912648.5671.3.camel@ux156> (raw)
In-Reply-To: <20060818143321.GA23446@instant802.com>
On Fri, 2006-08-18 at 07:33 -0700, Jouni Malinen wrote:
> Some hardware designs require this configuration for TX frames. It is
> used to select whether some of the fields are being filled in hardware
> (e.g., timestamp for Probe Response).
Ah ok, timestamp makes sense.
> This would only be needed for AP
> mode and IBSS (adhoc), so it is possible that not all low-level dirvers
> have yet been implemented to support such operation.
Right.
> This pkt_type was added at generic 802.11 layer in order to avoid
> forcing the low-level driver to even look at the 802.11 header when
> queuing the frame for transmission. Taken into account how simple
> operation it is to get the type and subtype from the frame control
> field, this tx ctrl pkt_type could be removed, if desired. However, it
> was added there for a reason.
No, that's ok, I was just wondering why it is there at all.
Thanks for clarifying,
johannes
next prev parent reply other threads:[~2006-08-18 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 11:41 [clarification request] ieee80211_tx_control.pkt_type Johannes Berg
2006-08-18 14:33 ` Jouni Malinen
2006-08-18 14:50 ` Johannes Berg [this message]
2006-08-18 16:25 ` Simon Barber
2006-08-21 7:21 ` Johannes Berg
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=1155912648.5671.3.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=jbenc@suse.cz \
--cc=jkm@devicescape.com \
--cc=netdev@vger.kernel.org \
--cc=simon@devicescape.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).