From: fengzeheng <zehengfeng@gmail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org, dcbw@redhat.com
Subject: Re: a question about marvell sd8686's wmm_config_change event
Date: Wed, 8 Jul 2009 18:10:20 +0800 [thread overview]
Message-ID: <5135d20a0907080310h6a67777av27e2a47eb072feb9@mail.gmail.com> (raw)
In-Reply-To: <200907080948.00065.hs4233@mail.mn-solutions.de>
Hi, Holger and dan
Sorry for my previous wrong message. I go through all the beacon
frames again and found that Ruckus AP update WMM
IE:wmm_parameter_set_update_counter. But it's strange that other
elements of wmm settings remain unchanged, RUCKUS just update the
update_counter for none of wmm settings updated actually ..........
thanks
2009/7/8 Holger Schurig <hs4233@mail.mn-solutions.de>:
> On Tuesday 07 July 2009 18:28:47 fengzeheng wrote:
>> hi, dan and all
>> My wireless card sd8686 reports that wmm_config_change
>> about every 2 seconds though wmm's setting in AP's beacons
>> don't change. seems that driver receive
>> MACREG_INT_CODE_WMM_STATUS_CHANGE event from firmware every 2
>> seconds. And according
>
> Hmm, if the firmware sends you a
> MACREG_INT_CODE_WMM_STATUS_CHANGE but you're sure that the
> beacons don't change, then the firmware seems to be buggy.
>
> Not sure if Marvell got sane and opened up their support for
> no-NDA-holders, but you could try and file a bug there.
>
>
> And we should look into the libertas driver if we always loose a
> packet whenever we get a MACREG :-)
>
> Greetings, Holger
>
> --
> http://www.holgerschurig.de
>
--
Best Regards
Feng zeheng
prev parent reply other threads:[~2009-07-08 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 16:28 a question about marvell sd8686's wmm_config_change event fengzeheng
2009-07-07 16:32 ` Dan Williams
2009-07-07 16:52 ` fengzeheng
2009-07-08 7:48 ` Holger Schurig
2009-07-08 10:10 ` fengzeheng [this message]
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=5135d20a0907080310h6a67777av27e2a47eb072feb9@mail.gmail.com \
--to=zehengfeng@gmail.com \
--cc=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
/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