From owner-acpi-jp@jp.freebsd.org  Mon Oct  9 06:08:11 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id GAA03944;
	Mon, 9 Oct 2000 06:08:11 +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 GAA03939
	for <acpi-jp@jp.freebsd.org>; Mon, 9 Oct 2000 06:08:10 +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 e98LA5h02476
	for <acpi-jp@jp.freebsd.org>; Sun, 8 Oct 2000 14:10:06 -0700 (PDT)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200010082110.e98LA5h02476@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 22:29:09 +0900."
             <20001008222909T.iwasaki@jp.FreeBSD.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 08 Oct 2000 14:10:05 -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 830
Subject: [acpi-jp 830] Re: acpi_lid patch 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> Hi,
> 
> > >  - 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?
> 
> Please trust them :-)  or I have to buy new laptop.

Er, sorry.  I meant that the AML was rubbish, not that we should throw 
your laptop out. 8)

> Actually this laptop generates Notify events only when Lid is closed.
> Opening lid doesn't generate events.
> I guess that BIOS programmer of this machine thought it is just enough
> to start Sx transition.  
> I also wonder what is detecting opened lid event for?

I'd guess that you'd use it to abort the Sx transition and restart.

-- 
... 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


