From owner-acpi-jp@jp.freebsd.org  Sun Oct  8 19:16:22 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id TAA75909;
	Sun, 8 Oct 2000 19:16:22 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id TAA75902
	for <acpi-jp@jp.freebsd.org>; Sun, 8 Oct 2000 19:16:20 +0900 (JST)
	(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e98AIFh00830
	for <acpi-jp@jp.freebsd.org>; Sun, 8 Oct 2000 03:18:16 -0700 (PDT)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200010081018.e98AIFh00830@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Sun, 08 Oct 2000 19:08:46 +0900."
             <20001008190846M.iwasaki@jp.FreeBSD.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 08 Oct 2000 03:18:15 -0700
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 826
Subject: [acpi-jp 826] Re: acpi_lid patch 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> 
> > BTW, did you plan to implement support for fixed sleep/power buttons as 
> > well in the button driver?  I have a machine here with a control method 
> > sleep button but a fixed power button (I think).  It also has a 
> > front-panel NMI button, which is really scary. 8)
> 
> Yes, I attached my latest patch, but not in acpi_button.c.  Fixed
> sleep/power button feature is specified in FACP table and cannot be
> probed by matching _HID, so it was difficult to integrate fixed
> sleep/power initialization in acpi_button.c.  These are in acpi.c as
> fixed events initialization in my latest patch attached.

Hmm.  I bet that we can do this with the identify method.  I'll have a 
look at it. 8)  I'm trying to make the PCI interface "nice", it's being
an "interesting" challenge.   Before I crash tonight I *hope* to get a 
new patchset out that attaches PCI and ISA stuff properly.  We'll see.

>  - Remove lid_status checking because some _LID method is bogus.
>    My main laptop's _LID always returns ZERO :-(
>    -- ACPI/data/chandra2.asl --
>     Device(LID) {
>         Name(_HID, 0xd0cd041)   
>         Method(_LID) {
>             Return(0x0)
>         }
>     }

Hmm.  Can we detect this sort of rubbish, or should we just trust the 
events?

Thanks!

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


