linux-kernel - Re: eeepc-laptop rfkill, stupid question #4

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: <20081102132650.GA13084@srcf.ucam.org>
Date:	Sun, 2 Nov 2008 13:26:50 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
Cc:	Henrique de Moraes Holschuh <hmh@....eng.br>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux acpi <linux-acpi@...r.kernel.org>
Subject: Re: eeepc-laptop rfkill, stupid question #4

On Sun, Nov 02, 2008 at 01:25:07PM +0000, Alan Jenkins wrote:

> No, the current rfkill core forces the device to restore the state on 
> resume.  So it can't be of sync after resume.  And there's no way for 
> the platform driver to affect this behaviour, aside from illegally 
> generating input events.

Oh, so it does. Yeah, in that case I don't see any real point in 
changing 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/