From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932604AbWG1J6U (ORCPT ); Fri, 28 Jul 2006 05:58:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932603AbWG1J6U (ORCPT ); Fri, 28 Jul 2006 05:58:20 -0400 Received: from cavan.codon.org.uk ([217.147.92.49]:39068 "EHLO vavatch.codon.org.uk") by vger.kernel.org with ESMTP id S932602AbWG1J6T (ORCPT ); Fri, 28 Jul 2006 05:58:19 -0400 Date: Fri, 28 Jul 2006 10:58:06 +0100 From: Matthew Garrett To: "Brown, Len" Cc: Shem Multinymous , Pavel Machek , vojtech@suse.cz, kernel list , linux-thinkpad@linux-thinkpad.org, linux-acpi@vger.kernel.org Subject: Re: Generic battery interface Message-ID: <20060728095806.GA2046@srcf.ucam.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@codon.org.uk X-SA-Exim-Scanned: No (on vavatch.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 28, 2006 at 12:05:35AM -0400, Brown, Len wrote: > Wonderful, but isn't the key here how simple it is for HAL > or X to understand and use the kernel API rather than the > developers of the kernel driver that implements the API? HAL currently gets most of its information from sysfs, and managed to deal with parsing the existing /proc/acpi/battery stuff. I don't think there's any real difficulty there. -- Matthew Garrett | mjg59@srcf.ucam.org