From owner-freebsd-mobile@FreeBSD.ORG Mon Oct 15 15:17:28 2012 Return-Path: Delivered-To: mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AECEC81E; Mon, 15 Oct 2012 15:17:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8328FC16; Mon, 15 Oct 2012 15:17:28 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D51ACB958; Mon, 15 Oct 2012 11:17:27 -0400 (EDT) From: John Baldwin To: Alberto Villa Subject: Re: Dell acpi_video patch Date: Mon, 15 Oct 2012 11:12:03 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p20; KDE/4.5.5; amd64; ; ) References: <20121005215316.GA38707@triton8.kn-bremen.de> <201210121006.17276.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201210151112.03393.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 15 Oct 2012 11:17:27 -0400 (EDT) Cc: acpi@freebsd.org, freebsd-acpi@freebsd.org, Juergen Lock , mobile@freebsd.org X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2012 15:17:28 -0000 On Friday, October 12, 2012 7:57:43 pm Alberto Villa wrote: > On Fri, Oct 12, 2012 at 4:06 PM, John Baldwin wrote: > > I think this is correct, but in we need to do more to properly handle that > > flag (DOD_DEVID_SCHEME_STD). Specifically, we shouldn't trust any bits in the > > device ID unless that bit is set (except for the special case of > > DOD_DEVID_LCD) as per my reading of the _DOD description in the ACPI 3.0b > > spec. I think this larger patch will do that while also fixing your case: > > I tested your patch and the only effect is that my three reported > screens (I'm on a laptop) changed from "crt" to "out" (I understand > why, from the code): > > hw.acpi.video.out0.active: 1 > hw.acpi.video.out1.active: 1 > hw.acpi.video.out1.brightness: 100 > hw.acpi.video.out1.fullpower: 100 > hw.acpi.video.out1.economy: 50 > hw.acpi.video.out1.levels: 100 50 0 10 20 30 40 50 60 70 80 90 100 > hw.acpi.video.out2.active: 1 > > Is there something I can do to help you make them recognised > correctly, or is it fault of a buggy ACPI table? Interesting. Can you get an acpidump? -- John Baldwin