Re: New SmartBattery DSDT-based controller

[Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org>]

Matthew Garrett wrote:
> On Sat, 2005-01-29 at 14:02 -0500, Rich Townsend wrote:
> 
> 
>>Eventually, the modified DSDTs can be put back into the ACPI4Linux 
>>database; but I'm more interested at the moment in ironing out any 
>>glitches in the code.
> 
> 
> While this is a neat hack, there's no real way that distributions are
> ever going to adopt this approach - DSDTs are copyrighted by the
> vendors, and without permission they're not going to be distributed by
> the Linux vendors. The alternative approach of modifying the user's DSDT
> on the fly is likely to be excessively fragile. The only reasonable
> solution is to provide a mechanism to read the battery directly.
> 

Yeah, this has occurred to me. I'm looking into cooking up some Perl, to 
allow the users to modify their own DSDTs. Of course, this is never 
going to be user friendly, and a long-term solution, as you say, is to 
read the battery directly.

That's what my acpi-sbs module already does, but I'm reluctuant to spend 
much time developing the module further, until some form of uniform 
battery interface for the kernel is designed and implemented. Having two 
seperate /proc/acpi interfaces, one for CM batteries and one for smart 
batteries, is not the way to go.

cheers,

Rich



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl