On Thu, May 24, 2012 at 01:42:36AM +1000, Jonathan Gray wrote:
> [...]
> Could you explain why you have need of this sensor I don't
> quite see it?
> [...]
I usually manage the network connections on my laptop with an ifstated
configuration. If the wireless device's link went down, it could be for
On Wed, May 23, 2012 at 05:22:24PM +0200, Gregor Best wrote:
> On Wed, May 23, 2012 at 09:12:20AM +0200, Tobias Ulmer wrote:
> > [...]
> > This a read-only sensor, it has no effect on misbehaving
> > hardware as far as I can tell.
> > [...]
>
> That is right. If I recall correctly, the very reason
On Wed, May 23, 2012 at 09:12:20AM +0200, Tobias Ulmer wrote:
> [...]
> This a read-only sensor, it has no effect on misbehaving
> hardware as far as I can tell.
> [...]
That is right. If I recall correctly, the very reason for introducing real
hardware killswitches was so that the OS could not
i
On Wed, May 23, 2012 at 01:27:26PM +1000, Brett wrote:
> On Tue, 22 May 2012 20:20:38 +0200
> Gregor Best wrote:
>
> > Hi people,
> >
> > the attached patch adds an indicator sensor to wpi devices that describes
> > the
> > current RFKill status. If the RF killswitch is engaged, the sensor rea
On Tue, 22 May 2012 20:20:38 +0200
Gregor Best wrote:
> Hi people,
>
> the attached patch adds an indicator sensor to wpi devices that describes the
> current RFKill status. If the RF killswitch is engaged, the sensor reads
> "Off",
> if it is not engaged and the device can operate, it reads "
Hi people,
the attached patch adds an indicator sensor to wpi devices that describes the
current RFKill status. If the RF killswitch is engaged, the sensor reads "Off",
if it is not engaged and the device can operate, it reads "On".
If this is okay, I plan on adding similar sensors to other wire
