linux-kernel - Re: Endless ACPI errors on Linus tree (5b664cb235)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Jul 2008 10:43:54 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jan Beulich <jbeulich@...ell.com>
Cc:	Andi Kleen <andi@...stfloor.org>, Takashi Iwai <tiwai@...e.de>,
	robert.moore@...el.com, Len Brown <lenb@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Endless ACPI errors on Linus tree (5b664cb235)

> That would basically mean there's no way to use the v2 fields here - all
> the code could do is report the inconsitency, but it would have to use
> the v1 field in any case. That's really a shame, and as before I'm
> somewhat hesitant to do so. The only way I could easily find myself
> doing this would be to introduce a command line option controlling the
> behavior here, but that would need to be done outside of the ACPICA
> code I'd assume.
> 
> Andi, Bob, Len?

I think we should only use v1 FADT fields for now and ignore v2.

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