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

Date:	Thu, 7 Oct 2010 22:49:27 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Mario Limonciello <superm1@...ntu.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Keng-Yu Lin <keng-yu.lin@...onical.com>, len.brown@...el.com,
	alan-jenkins@...fmail.co.uk, 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 04:45:22PM -0500, Mario Limonciello wrote:
> Matthew:
> 
> On Thu, Oct 7, 2010 at 16:42, Matthew Garrett <mjg59@...f.ucam.org> wrote:
> > I don't understand this. You know which code is broken - surely you're
> > able to determine which products shipped with BIOSes derived from the
> > broken code?
> 
> Not all product's BIOS are developed in-house.  The ones that are, yes
> it quite possible to identify.  Matter of fact, this issue tends to
> not exist on the in-house developed BIOS codebase.

Ok, so let's approach this differently. What is it that results in this 
issue not affecting Windows?

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