| 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: <AANLkTimh649Lhj-sBYzViq_G-2Bva0U-TPCMGfSdK=QE@mail.gmail.com> Date: Thu, 7 Oct 2010 16:45:22 -0500 From: Mario Limonciello <superm1@...ntu.com> To: Matthew Garrett <mjg59@...f.ucam.org> 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 Matthew: On Thu, Oct 7, 2010 at 16:42, Matthew Garrett <mjg59@...f.ucam.org> wrote: > On Thu, Oct 07, 2010 at 04:41:12PM -0500, Mario Limonciello wrote: > >> All Dell laptops are /supposed/ to adhere to the specification in >> question. Unfortunately, not all machines are tested with Linux >> during their development and on the OS they ship with that >> functionality isn't always used in that specific way for rfkill. > > 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? > > -- > Matthew Garrett | mjg59@...f.ucam.org > 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. -- Mario Limonciello superm1@...il.com -- 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