From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH 1/2] rt2x00: configure different txdesc parameters for non HT channel
Date: Mon, 2 Apr 2012 14:35:43 +0200 [thread overview]
Message-ID: <20120402123542.GA4567@redhat.com> (raw)
In-Reply-To: <CAGXE3d8C61rnWPgRU565n_FjjKTqk4pi9ncmdjxyAmEvVM-uvA@mail.gmail.com>
Hello
On Mon, Apr 02, 2012 at 02:09:14PM +0200, Helmut Schaa wrote:
> Why should we use PIFS for the beacon? Is that what the ralink drivers
> are doing?
Hmm, seems that is my own invention. I thought that should be used for
beacons, but currently I can only find in docs, that this is only needed
for entering PCF.
> > + else if (!(tx_info->flags & IEEE80211_TX_CTL_FIRST_FRAGMENT))
> > + txdesc->u.ht.txop = TXOP_SIFS;
> > + else
> > + txdesc->u.ht.txop = TXOP_BACKOFF;
> > +
> > + txdesc->u.ht.mcs = txrate->idx;
> > +
>
> This lacks short preamble handling. Something like:
>
> if (txrate->flags & IEEE80211_TX_RC_USE_SHORT_PREAMBLE)
> txdesc->u.ht.mcs |= 0x08;
>
> Actually, you could just shuffle the code a bit such that the rate setup
> happens before all the HT stuff, no?
Make sense.
Stanislaw
next prev parent reply other threads:[~2012-04-02 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 11:21 [PATCH 1/2] rt2x00: configure different txdesc parameters for non HT channel Stanislaw Gruszka
2012-04-02 11:21 ` [PATCH 2/2] rt2x00: do not generate seqno in h/w if QOS is disabled Stanislaw Gruszka
2012-04-02 13:26 ` Helmut Schaa
2012-04-02 12:09 ` [PATCH 1/2] rt2x00: configure different txdesc parameters for non HT channel Helmut Schaa
2012-04-02 12:35 ` Stanislaw Gruszka [this message]
2012-04-02 13:20 ` Helmut Schaa
2012-04-04 14:15 ` [PATCH 1/2 v2] " Stanislaw Gruszka
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=20120402123542.GA4567@redhat.com \
--to=sgruszka@redhat.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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).