From owner-freebsd-acpi@FreeBSD.ORG  Mon May  9 08:14:25 2005
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 553C716A4E7
	for <freebsd-acpi@freebsd.org>; Mon,  9 May 2005 08:14:25 +0000 (GMT)
Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B687543D79
	for <freebsd-acpi@freebsd.org>; Mon,  9 May 2005 08:14:24 +0000 (GMT)
	(envelope-from philip@paeps.cx)
Received: from loge.nixsys.be (loge.nixsys.be
	[IPv6:2001:838:37f:0:20c:6eff:fe4b:23f])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "loge.home.paeps.cx", Issuer "NixSys CA" (verified OK))
	by gateway.nixsys.be (Postfix) with ESMTP id 269E0C158;
	Mon,  9 May 2005 10:14:22 +0200 (CEST)
Received: from loge.nixsys.be (philip@localhost [127.0.0.1])
	by loge.nixsys.be (8.13.3/8.13.3) with ESMTP id j498EK8h004808;
	Mon, 9 May 2005 10:14:21 +0200 (CEST)
	(envelope-from philip@loge.nixsys.be)
Received: (from philip@localhost)
	by loge.nixsys.be (8.13.3/8.13.3/Submit) id j498EJ8f004807;
	Mon, 9 May 2005 10:14:19 +0200 (CEST)
	(envelope-from philip)
Date: Mon, 9 May 2005 10:14:17 +0200
From: Philip Paeps <philip@freebsd.org>
To: =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?= <jspedron@club-internet.fr>
Message-ID: <20050509081417.GF719@loge.nixsys.be>
Mail-Followup-To: =?iso-8859-1?Q?Jean-S=E9bastien_P=E9dron?=
	<jspedron@club-internet.fr>,	freebsd-acpi@freebsd.org
References: <427A8293.4020104@club-internet.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <427A8293.4020104@club-internet.fr>
X-Date-in-Rome: ante diem VII Idius Maias MMDCCLVIII ab Urbe Condida
X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3  FC53 BF4B D0E6 049D B879
X-Message-Flag: Get a proper mailclient!  <http://www.mutt.org/>
Organization: Happily Disorganized
User-Agent: Mutt/1.5.9i
cc: freebsd-acpi@freebsd.org
Subject: Re: Support for Asus V6V in acpi_asus(4)
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2005 08:14:25 -0000

On 2005-05-05 22:31:15 (+0200), Jean-Sébastien Pédron <jspedron@club-internet.fr> wrote:
> Here[1] is a patch against today's acpi_asus.c (HEAD) to add support for
> Asus V6V.

Thanks :-)  I'll commit this soonish.

> Especially, the method to get the display state (.disp_get): at boot time,
> hw.acpi.asus.video_output contains out-of-range values, but after setting it
> to an acceptable value, it reports the last set number.

Would be interesting to know how out of range these values are and where they
come from.  Are the values also out of range when you load acpi_asus as a
module after booting?

 - Philip

-- 
Philip Paeps                                    Please don't Cc me, I am
philip@freebsd.org                               subscribed to the list.

  When working toward the solution of a problem,
  it always helps if you know the answer.
  Provided of course you know there is a problem.