Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: provide sequence numbers
Date: Sat, 11 Oct 2008 16:49:51 +0200	[thread overview]
Message-ID: <200810111649.51946.IvDoorn@gmail.com> (raw)
In-Reply-To: <1223637719.17594.6.camel@johannes.berg>

On Friday 10 October 2008, Johannes Berg wrote:
> I've come to think that not providing sequence numbers for
> the normal STA mode case was a mistake, at least two drivers
> now had to implement code they wouldn't otherwise need, and
> I believe at76_usb and adm8211 might be broken.
> 
> This patch makes mac80211 assign a sequence number to all
> those frames that need one except beacons. That means that
> if a driver only implements modes that do not do beaconing
> it need not worry about the sequence number.

Very good news. :)

>  	if (!ieee80211_is_data_qos(hdr->frame_control)) {
> +		/* driver should assign sequence number */
>  		info->flags |= IEEE80211_TX_CTL_ASSIGN_SEQ;
> +		/* for pure STA mode without beacons, we can do it */
> +		hdr->seq_ctrl = cpu_to_le16(tx->sdata->sequence_number);
> +		tx->sdata->sequence_number += 0x10;
> +		tx->sdata->sequence_number &= IEEE80211_SCTL_SEQ;
>  		return TX_CONTINUE;
>  	}

Shouldn't this be changed to only setting the IEEE80211_TX_CTL_ASSIGN_SEQ
flag when the sequence counter was _not_ set (with beacons)?

Ivo

  reply	other threads:[~2008-10-11 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 11:21 [PATCH] mac80211: provide sequence numbers Johannes Berg
2008-10-11 14:49 ` Ivo van Doorn [this message]
2008-10-11 15:22   ` 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=200810111649.51946.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox