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
to firmware spec v5.1 this event generated when firmware monitors a
change in wmm state. This is a result of an ap change in the wmm
parameter ie or a change in the operational state of one of the AC
queues. However , I can't find any change of AP's wme settings in
beacon from the sniffer packets. So why does firmware send this event?
thanks for your any comments.
--
Best Regards
Fzh
On Wed, 2009-07-08 at 00:28 +0800, 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
> to firmware spec v5.1 this event generated when firmware monitors a
> change in wmm state. This is a result of an ap change in the wmm
> parameter ie or a change in the operational state of one of the AC
> queues. However , I can't find any change of AP's wme settings in
> beacon from the sniffer packets. So why does firmware send this event?
> thanks for your any comments.
It's probably something in the internal firmware's WMM queues then, not
something from the AP's IEs. Is the event causing a problem?
Dan
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
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 <[email protected]>:
> 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
If this event happen, then packet lost appear. However , I just send
80kbps udp stream using Iperf....
will 80kbps cause firmware's wmm queue full or change wmm setting?
2009/7/8 Dan Williams <[email protected]>:
> On Wed, 2009-07-08 at 00:28 +0800, 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
>> to firmware spec v5.1 ?this event generated when firmware monitors a
>> change in wmm state. This is a result of an ap change in the wmm
>> parameter ie or a change in the operational state of one of the AC
>> queues. However , ?I can't find any change of AP's wme settings in
>> beacon from the sniffer packets. So why does firmware send this event?
>> thanks for your any comments.
>
> It's probably something in the internal firmware's WMM queues then, not
> something from the AP's IEs. ?Is the event causing a problem?
>
> Dan
>
>
>
--
Best Regards
Fzh