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.
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.
Hope this is helpful,
--
Bryan
-
"Beyond the point of no return, there's no going back."
Narration to "Mars Rising" on the Science Channel
--
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
