On Tue, 2009-12-01 at 18:29 -0200, Henrique de Moraes Holschuh wrote:
> Ok, so it is the rfkill-input stuff (that is now part of the rfkill core)
> that is showing the problem (the bug might be elsewhere). We need to track
> the state of the rfkill input device to know what's broken, then.
OK. I
On Sat, 05 Dec 2009, Kevin Locke wrote:
> Rfkill pretends that the master switch was set in its current position
> at startup by using an EV_SW event on devices that support them. So
Actually, no, rfkill doesn't pretend anything.
The *drivers* that implement that EV_SW SW_RFKILL_ALL (like thinkp
On Sat, 2009-12-05 at 18:12 -0200, Henrique de Moraes Holschuh wrote:
> On Sat, 05 Dec 2009, Kevin Locke wrote:
>> Rfkill pretends that the master switch was set in its current position
>> at startup by using an EV_SW event on devices that support them. So
>
> Actually, no, rfkill doesn't pretend
