From owner-freebsd-hackers Fri Jan 12 10:40:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 5373837B400; Fri, 12 Jan 2001 10:40:26 -0800 (PST) Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92]) by tasogare.imasy.or.jp (8.11.1+3.4W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id f0CIeOk31978; Sat, 13 Jan 2001 03:40:24 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) To: jhb@FreeBSD.org Cc: iwasaki@jp.FreeBSD.org, hackers@FreeBSD.org Subject: Re: CFR: Generalized power-management interface In-Reply-To: References: <20010113024339Z.iwasaki@jp.FreeBSD.org> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010113034023K.iwasaki@jp.FreeBSD.org> Date: Sat, 13 Jan 2001 03:40:23 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > I'll get device major number for /dev/power and commit them within a > > few days if no objection. > > One thing that I was talking about with Mike Smith is that perhaps instead of > having a /dev/power just for power management stuff we should be a bit more > generic and have a /dev/health used for anything related to the machine's > "health"? This could include power management, thermal zones, etc. BTW, the I'm not sure if /dev/health is better but I think having common API for the machine's health is good thing. How about having /dev/power, /dev/thermal or whatever related with machine's health as abstracted layers, and creating API libraries for each subsystems like libpower, then providing libhealth as full-set API for the applications? > battery status doesn't work on my laptop unfortunately, but that is because I > have to have the Super IO (and thus all GPIO) disabled to get ACPI to boot. :( Is that related with embedded controller too? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message