On Mon, Mar 06, 2006 at 03:23:04PM -0800, Jouni Malinen wrote:
> On Mon, Mar 06, 2006 at 02:25:52PM -0800, Jean Tourrilhes wrote:
> > Jouni Malinen wrote :
> > > This is used to implement radio on/off without having to change other
> > > parts of the configuration (e.g., set interfaces down).
>
> > The airo driver use 'txpower' for that. txpower has a 'off'
> > option, and with the airo driver this disable the whole MAC, leaving
> > the interface up (and 'on' revert back).
>
> This is somewhat confusing parameter for disabling both transmit and
> receive (or the whole MAC for that matter).
Yes, I fully agree. I did not say I was fully confortable with
that and that you should do it, it was just another data point.
On the other hand, the difference between disabling Tx and
disabling the whole MAC would never be noticed by users except in
monitor mode. Also, such functionality is not very useful to the vast
majority of people, no harm if it's a bit buried in the API.
> Other than that, I don't
> really have anything against using this for what the adm_status was
> used as long as the 'on' option returns the previously used TX level
> without user space program having to set it again.
This is what 'on' does in WE : it read the current value, flip
the 'disabled' flag and rewrite it. So, as long as you fill the
correct stuff in the GET, it should be transparent in the GET.
> I haven't looked at
> what the current drivers are doing in this case.
I'm not 100% sure, but it seems that the HostAP driver use
txpower only to switch on and off the radio. Maybe you want to have
two words with HostAP maintainer ;-)
> Jouni Malinen PGP id EFC895FA
Have fun...
Jean
-
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
