From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 31 18:01:33 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1621BC95 for ; Wed, 31 Dec 2014 18:01:33 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E2F2627A7 for ; Wed, 31 Dec 2014 18:01:32 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 70F74B941; Wed, 31 Dec 2014 13:01:31 -0500 (EST) From: John Baldwin To: freebsd-acpi@freebsd.org Subject: Re: Lenovo T520: Present (-STABLE) vs. Future (-CURRENT) ACPI Support Date: Wed, 31 Dec 2014 11:15:24 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <20141226165731.GA28169@workbox.Home> In-Reply-To: <20141226165731.GA28169@workbox.Home> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201412311115.24212.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 31 Dec 2014 13:01:31 -0500 (EST) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Dec 2014 18:01:33 -0000 On Friday, December 26, 2014 11:57:31 am Bigby James wrote: > Howdy-ha, folks, > > Please forgive my ignorance if my question is rather mundane and/or inane. I'm > pretty new to FreeBSD and its development cycle. Here's my situation: I've > recently migrated my laptop (Levovo Thinkpad T520) to FreeBSD using the > 10.1-STABLE snapshot, and most everything works pretty well. The only > exceptions are some of the hardware keys, including the LCD brightness control > keys, which is something I'd really like to have. > > Before going ahead with that install, though, on a lark I decided to try out the > 11-CURRENT snapshot to see how it worked out. As it turns out, everything > presently missing from 10-STABLE worked out of the box on -CURRENT. So I know > that full support for my machine is in the source tree now and, barring any > fundamental changes in the development branch, will be in the next -RELEASE. I > don't really have the time, know-how or guts to maintain a -CURRENT install on > this machine, so for the time being I'm sticking with 10-STABLE. So I'm > wondering just how often ACPI functionality gets moved from the -CURRENT branch > into the most recent release's -STABLE branch. In other words, what are the > chances that the features I'm waiting for will get moved into the 10-STABLE > branch in the near future? Are the ACPI devs pretty conservative with this? For > the time being I can control screen brightness using xrandr, and as fond as I am > with the convenience it is just a convenince all the same, so I can always > remain patient. But I'm wondering if there's a way to know if and when ACPI > functionality will get backported to -STABLE. I currently follow this list and > the SVN mailing list for 10-STABLE, so I can also just keep an eye on them if > that's the answer. Thanks in advance. In the case of brightness hotkeys, please try MFC'ing 270516 to your stable/10 tree. If that fixes it (it fixed brightness for my X220) then you know the specific change to ask someone (in this case Adrian) to MFC. -- John Baldwin