linux-kernel - Re: [PATCH] ACPI: Adjust the return value of

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:	Tue, 24 Mar 2015 14:53:24 -0500
From:	Mario Limonciello <mario_limonciello@...l.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	Matt Fleming <matt@...eblueprint.co.uk>,
	Jason Ekstrand <jason@...kstrand.net>,
	LKML <linux-kernel@...r.kernel.org>,
	Bard Liao <bardliao@...ltek.com>,
	Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"lenb@...nel.org" <lenb@...nel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [PATCH] ACPI: Adjust the return value of _REV on x86


On 03/24/2015 01:01 PM, Matthew Garrett wrote:
> On Tue, Mar 24, 2015 at 12:22:18PM -0500, Mario Limonciello wrote:
>
> Since we don't expose any way for the platform to detect that it's
> running Linux, yes.
>
> Will it? You haven't shipped the firmware that changes this behaviour
> yet.
>
This was posted a few days ago.  BIOS A02, it resolves the broken behavior introduced in A01 and Linux.

It can be flashed in the BIOS F12 boot menu, no Windows or DOS necessary.

http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=F2PRR&fileId=3442501672&osCode=WB64A&productCode=xps-13-9343-laptop&languageCode=EN&categoryId=BI

Anything bought from now forward will have that BIOS version (or something newer).
--
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/