linux-kernel - Re: Lenovo ThinkPads need acpi

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]

Message-ID: <20080114020352.GA2502@srcf.ucam.org>
Date:	Mon, 14 Jan 2008 02:03:52 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Pavel Machek <pavel@....cz>, Len Brown <lenb@...nel.org>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Lenovo ThinkPads need acpi_osi="Linux"

On Sun, Jan 13, 2008 at 11:57:18PM -0200, Henrique de Moraes Holschuh wrote:
> On Mon, 14 Jan 2008, Matthew Garrett wrote:
> > not going to want the low-level ACPI code to do anything video-related 
> > on a lot of hardware. The in-kernel modesetting code for Intel machines 
> > will be able to handle this significantly more effectively.
> 
> Yeah, but we have a ton of machines (thinkpads among them) with ATI, and
> other GPUs.

The ATI case is certainly more of an issue, but I'm becoming more 
optimistic about that being workable in the near future - certainly on 
machines with ATOM-based BIOSes.

> Whitelists would need to be reasonably specific, anyway (not "all
> thinkpads"), so it just means "don't do it on certain R50e", or whatever.

I'd prefer not to push this policy into the kernel, since the right 
thing to do depends on which graphics drivers you're using and so on. 
Userspace is in a better position to make this determination. Of course, 
this also means not passing the Linux OSI to the firmware. Our hardware 
interaction is sufficiently in flux that any attempt to work around it 
in the firmware is just going to lead to bizarre breakage down the road.

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