linux-kernel - Re: [PATCH 2/2] eeepc-laptop: Use standard interfaces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080804173627.GA10302@srcf.ucam.org>
Date:	Mon, 4 Aug 2008 18:36:27 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Ivo van Doorn <ivdoorn@...il.com>
Cc:	corentincj@...aif.net, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, hmh@....eng.br
Subject: Re: [PATCH 2/2] eeepc-laptop: Use standard interfaces

On Mon, Aug 04, 2008 at 07:53:38PM +0200, Ivo van Doorn wrote:
> On Monday 04 August 2008, Matthew Garrett wrote:
> > eeepc-laptop currently only sends key events via ACPI and has 
> > non-standard rfkill control. Add an input device and use the rfkill 
> > infrastructure.
> > 
> > Signed-off-by: Matthew Garrett <mjg@...hat.com>
> 
> Please use the rfkill_force_state() to report state changes,
> that will ensure that the events are immediately send to the
> rfkill layer.

Why does writing to the sysfs file not generate an update implicitly? 
This is purely a software rfkill device, the input hotkey just generates 
KEY_WLAN and needs rfkill-input to handle it.
-- 
Matthew Garrett <mjg59@...f.ucam.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/