From owner-freebsd-mobile@FreeBSD.ORG Mon Oct 22 14:37:46 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 D6F38F0A; Mon, 22 Oct 2012 14:37:46 +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 A65698FC1A; Mon, 22 Oct 2012 14:37:46 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F3C5EB978; Mon, 22 Oct 2012 10:37:45 -0400 (EDT) From: John Baldwin To: Alberto Villa Subject: Re: Dell acpi_video patch Date: Mon, 22 Oct 2012 10:25:14 -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> <201210200840.48613.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201210221025.14331.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 22 Oct 2012 10:37:46 -0400 (EDT) Cc: 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, 22 Oct 2012 14:37:46 -0000 On Saturday, October 20, 2012 9:37:40 am Alberto Villa wrote: > On Sat, Oct 20, 2012 at 2:40 PM, John Baldwin wrote: > > Oh, no, I hadn't been able to tell from your ASL that bit 16 was set (it's > > not that easy to guess as it computes the ID's dynamically at runtime. > > I see. > > > I was merely guessing that since I had changed the matching logic to look at > > bit 31 that that was the cause, > > Oh, no, it wasn't working before too, it just changed from "crt" to > "out" because of your change (which makes sense). > > > but it wasn't the matching logic that was > > different (comparing _ADR to _DOD), but the logic that parsed _DOD is what > > treated your laptop differently. > > So, just to be sure, you don't need any other information from me, > right? I don't think, by the way, that a list of known non-standard > configurations is worth being added to the code for this issue. Largely correct. However, we could add support for vendor-specific IDs if someone wanted to maintain it. -- John Baldwin