From: Chr <chunkeey@web.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
John W Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44
Date: Fri, 15 Aug 2008 23:06:38 +0200 [thread overview]
Message-ID: <200808152306.38450.chunkeey@web.de> (raw)
In-Reply-To: <1218831437.3197.5.camel@localhost>
On Friday 15 August 2008 22:17:16 Johannes Berg wrote:
> On Fri, 2008-08-15 at 22:15 +0200, Chr wrote:
> > hmm? has this something to do with the per STA TID in
> > 7.1.3.4.1 (802.11-2007) ?
>
> yes
>
> > Well the firmware (aka: LowerMAC) has some sort station
> > database so there could be some room for that... maybe.
>
> makes little sense since we don't tell it about stations, well, I dunno.
well, the firmware parses some parts of the ieee80211 header.
And we are actually supposed to tell the firmware about the station aid,
on every tx (and that's why there's a AID field in the tx_info struct now. ;-)
It's not used yet, but it will when Linville returns...
>
> > (But yes, when I was playing with the AP/IBSS,
> > all beacon frames had a running sequence counter...
>
> Maybe only non-QoS frames?
well, if you take a look at the cx3110x log you can see
that the duration & sequence field is always zero...
the firmware is actually ~30kb of ARM-code, but unfortunatly
they decided to pack it...
>
> > maybe you can see this with a cx3110x in IBSS mode too?!)
>
> we're supposed to be getting documentation on the lmac in there...
Really?! Well, from my POV it would be better to kickstart FreeMAC,
rather than writing a driver for these LMAC Firmwares... seriously!
Regards,
Chr
next prev parent reply other threads:[~2008-08-15 21:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 16:23 [PATCH] p54: Fix for TX sequence number problem that resulted from commit 741b4fbc44 Larry Finger
2008-08-08 8:26 ` Chr
2008-08-08 14:29 ` Larry Finger
2008-08-08 18:38 ` Chr
2008-08-09 16:02 ` Larry Finger
2008-08-09 16:43 ` Chr
2008-08-09 18:11 ` Larry Finger
2008-08-10 14:19 ` Larry Finger
2008-08-10 22:27 ` Chr
2008-08-10 23:04 ` Larry Finger
2008-08-13 22:15 ` Chr
2008-08-15 18:34 ` Chr
2008-08-15 19:26 ` Johannes Berg
2008-08-15 20:15 ` Chr
2008-08-15 20:17 ` Johannes Berg
2008-08-15 21:06 ` Chr [this message]
2008-08-15 21:13 ` Johannes Berg
2008-08-16 0:34 ` Larry Finger
2008-08-16 2:21 ` Chr
2008-08-16 14:00 ` Larry Finger
2008-08-16 14:38 ` Chr
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=200808152306.38450.chunkeey@web.de \
--to=chunkeey@web.de \
--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;
as well as URLs for NNTP newsgroup(s).