Search Linux Wireless

Re: [RFC] b43: A patch for control of the radio LED using rfkill

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday 18 September 2008, Johannes Berg wrote:
> On Thu, 2008-09-18 at 19:52 +0200, Ivo van Doorn wrote:
> 
> > From rfkill.h:
> > 	RFKILL_STATE_SOFT_BLOCKED = 0,	/* Radio output blocked */
> > 	RFKILL_STATE_UNBLOCKED    = 1,	/* Radio output allowed */
> > 	RFKILL_STATE_HARD_BLOCKED = 2,	/* Output blocked, non-overrideable */
> > 
> > Since b43 has a rfkill mechanism that does switch of the radio when RFKILL is set to BLOCK
> > after a key press, it should send RFKILL_STATE_HARD_BLOCKED because rfkill cannot override
> > it.
> > 
> > rt2x00 hardware does not change the radio state when RFKILL is set to BLOCK after a key press,
> > the state is therefor overridable and it can send RFKILL_STATE_SOFT_BLOCKED to rfkill.
> 
> If rt2x00 has no meaning of "hardware blocked", why is the button not a
> simple input device?

Because I had that discussion with Henrique and that ended with a "it isn't a input device"...

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

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux