linux-kernel - Re: [PATCH] dell-laptop: Add hwswitch

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] [day] [month] [year] [list]

Date:	Thu, 7 Oct 2010 12:15:10 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Keng-Yu Lin <keng-yu.lin@...onical.com>
Cc:	len.brown@...el.com, alan-jenkins@...fmail.co.uk,
	superm1@...ntu.com, platform-driver-x86@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dell-laptop: Add hwswitch_only module parameter

On Thu, Oct 07, 2010 at 11:30:07AM +0800, Keng-Yu Lin wrote:
> Some BIOS does not report the correct state of the wireless killswitch
> in the return value of SMI Class 17, Select 11.
> 
> This causes the killswitch to always stay as soft-blocked once the rfkill
> hotkey is pressed.
> 
> This patch adds a module parameter to work around this by disregarding
> the software rfkill and using only Bit 16 in the return value of
> SMI Class 17, Select 11 as the hardware killswitch.

I don't like "Fix my hardware" options. Is there any way we can identify 
this failure case?

-- 
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/