From owner-freebsd-mobile Sun May 23 11: 0:48 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 7688214FC9 for ; Sun, 23 May 1999 11:00:41 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn56.imasy.or.jp [202.227.24.248]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id DAA03143; Mon, 24 May 1999 03:00:34 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199905231800.DAA03143@tasogare.imasy.or.jp> To: imp@harmony.village.org Cc: nate@mt.sri.com, freebsd-mobile@FreeBSD.ORG Subject: Re: apm on quantex h-1331 w/ pao 2.2.8 In-Reply-To: Your message of "Sat, 22 May 1999 13:27:22 -0600" <199905221927.NAA07011@harmony.village.org> References: <199905221927.NAA07011@harmony.village.org> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 24 May 1999 02:59:13 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 28 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Warner Losh-san imp> Hmmm. Looking at the code, it appears that the bug is still present imp> in -current. One of the PAO developers sent me a patch which I could imp> have sworn I applied and committed, but sadly I didn't. Hmmm. Let's Shall I send-pr it? :-) imp> tree). I'll look at integrating it into the tree... Thanks a lot. I hope that we could exchange information each other and work together. BTW, my current small project is to develop apmd(8) and support code in apm device driver. I've just ported NetBSD's driver code (apm_record_event() and apmpoll()), implemented event filtering feature for user fetching (user can select which event to be processed in user land). Now we are thinking about design of apmd(8) in PAO's mailing list. Any ideas? I understand that development of apmd(8) is short-term solution, we need to consider higher level power management system as Warner-san and Hosokawa-san mentioned, so our implementation will be simple as possible :-) I'll post some patchs against -current after finish my work on PAO for 3.2 if you are interested in it. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message