On Saturday 05 July 2008, Johannes Berg wrote:
>
> > That problem is only in rt2400pci and rt2500pci who raise the beacon interrupt,
> > all other drivers have the template and auto sequence numbers.
>
> Ok.
>
> > But no sequence numbers for the beacons, I think that will definately cause
> > problems for those 2 drivers.
> >
> > But the function ieee80211_include_sequence() is being called from within the
> > ieee80211_beacon_get() function. Only for the Mesh it doesn't seem to be called.
>
> Well it's not called from where the IBSS beacon is set either, and the
> IBSS beacon isn't generated every time anyway. So I'm confused now. Do
> rt2{4,5}00pci not support IBSS?
Well it does claim support for it, but it has been enabled only since 2.6.26, so the number
of people who have tested it is very limited. And so far little to no success stories...
The main trick in rt2x00lib is that it doesn't care if it is an IBSS or AP beacon, it will always
use the update_beacon() callback function to write the beacon to the hardware. It doesn't
need to differentiate between the beacon types (as far as I know, master mode isn't implemented
in the legacy drivers, and the only claim about if it is possible cones from Asus who owns the
closed source driver with AP functionality).
So for the Ralink hardware it just needs a completely valid beacon which it can transmit,
only for rt2400pci/rt2500pci it requires that the sequence number is set due to lacking
hardware sequence counting.
After that those 2 will raise an interrupt every beacon interval to request a new beacon,
which rt2x00lib fulfills by calling ieee80211_beacon_get().
Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
