From owner-freebsd-current Sat Nov 9 13:25: 8 2002 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 A3B3437B406 for ; Sat, 9 Nov 2002 13:25:06 -0800 (PST) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 46ABA43E4A for ; Sat, 9 Nov 2002 13:25:05 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 9 Nov 2002 21:25:04 +0000 (GMT) To: Takanori Watanabe Cc: acpi-jp@jp.FreeBSD.org, current@freebsd.org, frode@nordahl.net Subject: Re: [acpi-jp 1933] Re: acpid implementation? In-Reply-To: Your message of "Sun, 10 Nov 2002 06:12:49 +0900." <200211092112.GAA10487@axe-inc.co.jp> Date: Sat, 09 Nov 2002 21:25:03 +0000 From: Ian Dowse Message-ID: <200211092125.aa12757@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200211092112.GAA10487@axe-inc.co.jp>, Takanori Watanabe writes: >== >Next way is that make /dev/acpictl node that can open >exclusively and catch the power event by it, like apmd. >== > >This way requires that the event reading proceess should >be only one, so we need another device node to read event. Yes, exactly - I think that your suggestion of extending /dev/devctl to support device-specific events to be handled by devd is a much nicer solution though. >options PSM_HOOKRESUME #hook the system resume event, useful > #for some laptops >options PSM_RESETAFTERSUSPEND #reset the device at the resume event > >will resolve your problem without the patch. Cool, thanks. I didn't know those options existed - I'll try them out next time I reboot. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message