| 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
| ||
|
Message-ID: <20101007215028.GB2292@srcf.ucam.org> Date: Thu, 7 Oct 2010 22:50:28 +0100 From: Matthew Garrett <mjg59@...f.ucam.org> To: Dmitry Torokhov <dmitry.torokhov@...il.com> Cc: Mario Limonciello <superm1@...ntu.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 02:46:28PM -0700, Dmitry Torokhov wrote: > On Thu, Oct 07, 2010 at 10:37:54PM +0100, Matthew Garrett wrote: > > Dell laptop driver is reasonable. All we need is a list of hardware, and > > I'd really hope that Dell know which BIOS versions contain this code! > > > > Unfortunately this kind of crap tends to flow from one BIOS version to > another.. How many DMI entries do we know about so far? Did Dell issue > firmware updates correcting the issue so new boxes will not exhibit the > problem? Pushing this out to userspace doesn't help. If it's sufficiently prevelant that it's impossible to have a comprehensive list, then a module option makes it too easy for people to just post the fix on a forum somewhere and never actually get it upstream. -- 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/
Powered by blists - more mailing lists