From: Michael Buesch <mb@bu3sch.de>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Christian Lamparter" <chunkeey@web.de>,
"John Linville" <linville@tuxdriver.com>,
"Michael Wu" <flamingice@sourmilk.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211: give burst time in txop rather than 0.1msec units
Date: Tue, 12 Feb 2008 21:42:09 +0100 [thread overview]
Message-ID: <200802122142.10325.mb@bu3sch.de> (raw)
In-Reply-To: <1ba2fa240802121157t370c8418v8a24484596ce5bcd@mail.gmail.com>
On Tuesday 12 February 2008 20:57:45 Tomas Winkler wrote:
> On Feb 12, 2008 9:21 PM, Michael Buesch <mb@bu3sch.de> wrote:
> > On Tuesday 12 February 2008 12:31:40 Johannes Berg wrote:
> > > > > + /*
> > > > > + * FIXME: The default values in the spec (IEEE 802.11
> > > > > + * 7.3.2.19 Table 37) are 47, 94, 0, 0, why use
> >
> > Does somebody know the correct place where these values are in
> > the specs? Section 7.3.2.19 is about "Supported channels IE".
> >
> >
> > > > > + * 47, 94, 63, 0 here? Also, the default AIFS
> > > > > + * values (second parameter) are 2, 2, 3, 7...
> > > > > + */
> >
> >
> 7.3.2.29 EDCA Parameter Set element
Thanks, found it :)
--
Greetings Michael.
next prev parent reply other threads:[~2008-02-12 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 15:49 [PATCH v2] mac80211: give burst time in txop rather than 0.1msec units Johannes Berg
2008-02-11 18:52 ` Christian Lamparter
2008-02-12 11:31 ` Johannes Berg
2008-02-12 13:02 ` [PATCH] p54: use IEEE 802.11e defaults for initialization Christian Lamparter
2008-02-13 12:11 ` Johannes Berg
2008-02-12 19:21 ` [PATCH v2] mac80211: give burst time in txop rather than 0.1msec units Michael Buesch
2008-02-12 19:57 ` Tomas Winkler
2008-02-12 20:42 ` Michael Buesch [this message]
2008-02-13 12:10 ` Johannes Berg
2008-02-12 16:26 ` John W. Linville
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=200802122142.10325.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=chunkeey@web.de \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.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).