On Saturday 05 July 2008, Bryan Batten wrote: > Ivo van Doorn wrote: > ... > > Note that the "raise beacondone interrupts without a beacon" is > > also a bug, and will be addressed later. > ... > > FWIW, I've never been able to figure out a way to shut it off in the > legacy drivers. Unless there's some mechanism I've missed, I would > consider this a bug, but its a hardware bug because - in the rt2500 > driver at least - even disabling it in the interrupt mask register has > no effect. That is interesting, have you tried controlling CSR14 and more specifically the TBCN or BeaconGen fields? > I think it would be more accurately termed a target beacon > transmission time interrupt. The rt61 driver's ISR simply does not > test for the condition. The rt2400 and rt2500 drivers do nothing if > not in adhoc mode. If in adhoc mode, they both assume a beacon frame > is ready to go and send it. This relies on a canned frame that is set > up during initialization. Hmm, in that case I have to fix something in the beacondone handler to prevent it requesting a beacon when mac80211 hasn't supplied anything yet.. Thanks for the notice. :) 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
