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:	Mon, 14 May 2012 16:21:17 -0500
From:	Mario Limonciello <mario_limonciello@...l.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	Kamal Mostafa <kamal@...onical.com>,
	"platform-driver-x86@...r.kernel.org" 
	<platform-driver-x86@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dell-laptop: rfkill blacklist Dell XPS 13z, 15z



On 05/14/2012 04:19 PM, Matthew Garrett wrote:
> On Mon, May 14, 2012 at 03:08:57PM -0500, Mario Limonciello wrote:
>> On 05/14/2012 02:37 PM, Matthew Garrett wrote:
>>> What does "Improper BIOS interaction" mean? What's the proper BIOS interaction?
>> These platforms are not obeying the smbios interface specs for turning on and off radios.  It's not currently expected that the interaction will improve during the lifetime of these platforms.  If it does, then this can be adjusted to only apply to the BIOS versions before the fix.
> Ok, pretty bored of this at this point. If the bios interface is
> unreliable then I'll just remove the rfkill support. I'm not going to
> continue adding machines to a blacklist some time after users find
> things are broken.
>
> Is this just as broken under Windows?
>
The BIOS interface is reliable on business client (Latitude and Vostro) hardware.

The outliers of Inspiron and XPS don't seem to follow the interface as explicitly.  It is not broken on Windows.  I don't have an understanding why it's not, but conjecture that it's a different interface being used on these that I don't have information on yet.

You would be better to only match on Latitude and Vostro and anything else that people want to opt in via a paramater than to remove the interface entirely IMO.

-- 
*Mario Limonciello*
Linux Engineer
*Dell*| OS Engineering
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ