On Wed, May 10, 2006 at 03:53:48PM +0200, Ivo van Doorn wrote: > I think the problem is what the dscape exactly expects the driver to do when > add_interface() is called by the stack. When that call has finished, does the > stack > expects the radio to be enabled, or should it instruct the driver to enable > the radio later > on through a field in the config structure.
I think the current expectation is for the interface to be set into enabled state at this point. > What currently happens in rt2x00 (Which might not be doing what the stack > expects) > is that when add_interface() is called the radio remains off untill open() is > called or > radio_enabled has been set in the config structure. We used radio_enabled (or well, the previously used name adm_status) as a "soft disable", i.e., the radio hardware was mostly enabled, but no TX or RX happened. This could, e.g., mean masking out interrupts and/or disabling receive part of the radio. This has been used to provide a mechanism for disabling the radio without having to set the interface down, i.e., without causing IP addresses to be dropped or bridging status changed. -- Jouni Malinen PGP id EFC895FA - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
