From owner-freebsd-current@FreeBSD.ORG Tue Jun 17 05:41:38 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F42937B401 for ; Tue, 17 Jun 2003 05:41:38 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7134743FA3 for ; Tue, 17 Jun 2003 05:41:37 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h5HCfakA067926; Tue, 17 Jun 2003 06:41:36 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Tue, 17 Jun 2003 06:40:59 -0600 (MDT) Message-Id: <20030617.064059.43008640.imp@bsdimp.com> To: simon@nitro.dk From: "M. Warner Losh" In-Reply-To: <20030616125857.GB400@nitro.dk> References: <16109.42232.319995.177184@canoe.velocet.net> <20030616125857.GB400@nitro.dk> X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: dgilbert@velocet.ca cc: FreeBSD-current@freebsd.org Subject: Re: Need acpi-event-d? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 12:41:38 -0000 In message: <20030616125857.GB400@nitro.dk> "Simon L. Nielsen" writes: : On 2003.06.16 07:07:36 -0400, David Gilbert wrote: : > First, I must say that it's cool that ACPI code can be examined and : > rewritten. In my laptop's case, this was key to make things fairly : > happy. : > : > Anyways, after a resume, it would appear I need to kill and restart : > moused. Under 4.x, apmd was used for this purpose ... but this new : > laptop doesn't support apm at all. /dev/apm seemed to be emulated by : > acpi for the benifit of battery monitors, but apmd won't run. : > : > Is there a facility to run things on resume, or is this reset : > something better done inside the kernel? : : I think devd(8) should be used for this, but I havn't tried. devd does not (currently) get events for suspend/resume. Maybe it should. Warner