From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 28 00:20:29 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CAD311FF; Mon, 28 Jan 2013 00:20:29 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) by mx1.freebsd.org (Postfix) with ESMTP id 7AF0DDFB; Mon, 28 Jan 2013 00:20:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=IT4ln9oJ/PihT+UONV2iWAR/M/GiJUWcbBFX7yZdPV8=; b=v5ic9mpd/5wtow9A4R4ASWcXD6Y2tIcqPNW9Gb4FWNAbY8cJ6c82YXlKRZJhOGy9T4v4N+aS9LRrUR/86HTfy+ew6dSOy6UlXR/e3pLGPQGtTRmNDMQ3MSxOrSxKfsqv; Received: from [122.129.203.50] (port=40744 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1TzcSZ-004OYr-Fc; Sun, 27 Jan 2013 17:20:28 -0700 Date: Mon, 28 Jan 2013 07:20:23 +0700 From: Erich Dollansky To: Eitan Adler Subject: Re: what is required to support a new laptop? Message-ID: <20130128072023.63939e6f@X220.ovitrap.com> In-Reply-To: References: <20130125140953.GA1328@glenbarber.us> <20130125141202.GB1328@glenbarber.us> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: Glen Barber , freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 00:20:29 -0000 Hi, On Sun, 27 Jan 2013 18:24:36 -0500 Eitan Adler wrote: > On 27 January 2013 12:59, Kevin Oberman wrote: > > On Fri, Jan 25, 2013 at 9:25 PM, Eitan Adler > > wrote: > >> On 25 January 2013 14:51, Kevin Oberman wrote: > >>> There are several threads in the archives of acpi@ and mobile@ > >>> discussing this. Most things are pretty easy. Use xev to find the > >>> events generated by the volume buttons. > >> > >> I'm handling the volume keys with xbindkeys. > >> > >>> Mute and the ThinkLight (if > >>> your system has one) should work as is. > >> > >> Mute does not function - I am using xbindkeys to handle it. The > >> "video" key generates no event. > >> > >>> Brightness is a bit bigger issue as Lenovo has completely > >>> revamped it These buttons don't generate events. :-( > >> > >> Where *should* they be handled? How do they work on windows? > >> > >> FWIW they seem to change hw.acpi.video.brightness, but change > >> nothing visible on the screen. > >> > >>> You can install the acpi_call > >>> port and use it to set the brightness, but it is a pain as it > >>> does not allow for setting incremental changes, only absolute > >>> values.(16 of them). > >> > >> Any pointers for what to look at? I have no idea what I'm doing > >> w.r.t. computers ^W ACPI. > > > > Install sysutils/acpi_call > > kldload acpi_call > > acpi_call -p '\VBRC' -i [0-15] > > > > There seem to be some differences on the range, but in my T530 0=off > > and 15=full. > > > > Unfortunately, the brightness functions do not generate X events > > and I have not seen any posts on how to tie them to anything to > > adjust brightness. > > > [2881 root@gravity ~ ]#acpi_call -p '\VBRC' -i 1 > Unknown object type '0' > [2882 root@gravity ~ !5!]#acpi_call -p '\VBRC' -i 2 > Unknown object type '0' > [2883 root@gravity ~ !5!]#acpi_call -p '\VBRC' -i 0 > Unknown object type '0' > [2884 root@gravity ~ !5!]#acpi_call -p '\VBRC' -i 15 > Unknown object type '0' > > I can confirm that this works on an X220: acpi_call -p '\VBRC' -i $value It also works lower case for me. Erich