From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: Smart Battery System driver Date: Sat, 15 Jan 2005 00:13:03 +0000 Message-ID: <1105747983.7368.3.camel@tyrosine> References: <41E81C2C.8010809@bartol.udel.edu> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <41E81C2C.8010809-OBnUx95tOyn10jlvfTC4gA@public.gmane.org> Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Fri, 2005-01-14 at 14:23 -0500, Rich Townsend wrote: > ...provides access to the SBS via a new /proc/acpi/sbs interface, and > also provides a "legacy" /proc/acpi/battery interface that current > battery-monitoring tools can access. This driver depends on Bruno's > i2c-acpi-ec driver, which I have included with my source code since a > couple of bug fixes were necessary. One thing I've been meaning to ask - several Thinkpads have an interesting design issue, whereby reading certain smbus addresses can render the machine unbootable without a motherboard replacement. As a result, i2c-piix refuses to load on Thinkpads. Does something similar need to be done for i2c-acpi-ec, or does it only provide i2c access to devices connected to the embedded controller? -- Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt