On Saturday 05 July 2008, Bryan Batten wrote: > Ivo van Doorn wrote: > ... > > That is interesting, have you tried controlling CSR14 and more > > specifically the TBCN or BeaconGen fields? > > No. It turns out that if I set the RT2500's CSR14 to zero (the default > power on state according to the data sheet) at driver initialization, > there are no beacon interrupts until enabled in AsicEnableIbssSync(). > I deem this a bug, the fix for which in now in CVS. Heh, that will bring down the number of raised interrupts in the legacy driver. :) You might want to add it to rt2400 as well, I expect the same behavior for that. ;) I'll put the initialization into rt2x00 as well, since it doesn't set it to 0 by default either. 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
