Hi Michael, we are collecting every kind of material about Broadcom board, too. Could you please point out the document with such specifications?
I confirm what Lorenzo wrote: there are 32 bytes for queue. If you leave 22 then all the Qos mechanisms go wrong. Indeed, the bcm board takes (quite) exclusive control of the channel as gap is always set to zero. Cheers, -FG On Sep 10, 2008, at 2:58 PM, Michael Buesch wrote: > On Wednesday 10 September 2008 00:15:14 Lorenzo Nava wrote: >> Hi everybody, >> >> I worked with the QoS parameters trying to understand why, checking >> them within the firmware, they don't seems to have the correct values >> even if they were set correctly by the driver. >> I think that there could be an error in the b43.h file: >> >> /* SHM offsets to the QOS data structures for the 4 different >> queues. */ >> #define B43_QOS_PARAMS(queue) (B43_SHM_SH_EDCFQ + \ >> (B43_NR_QOSPARAMS * sizeof(u16) * >> (queue))) >> #define B43_QOS_BACKGROUND B43_QOS_PARAMS(0) >> #define B43_QOS_BESTEFFORT B43_QOS_PARAMS(1) >> #define B43_QOS_VIDEO B43_QOS_PARAMS(2) >> #define B43_QOS_VOICE B43_QOS_PARAMS(3) >> >> /* QOS parameter hardware data structure offsets. */ >> #define B43_NR_QOSPARAMS 22 >> >> Each EDCF parameters set take up 32 byte (in the firmware the offset >> between 2 EDCFQ is 0x010 that is equivalent to 0x020 if the offset >> was >> expressed in byte). This means that the B43_NR_QOSPARAMS must be set >> to 16. >> With the value equal to 16 I can access correctly the aifs, cwcur, >> cwmax, etc within the firmware. >> >> What do you think about that? > > The specifications says there are 22 (decimal) entries. > > > > -- > Greetings Michael. > _______________________________________________ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
