Re: Re: Smart Battery System driver

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

Johan Vromans wrote:
> Rich Townsend <rhdt-OBnUx95tOyn10jlvfTC4gA@public.gmane.org> writes:
> 
> 
>>http://shayol.bartol.udel.edu/~rhdt/download/acpi_sbs-20050119.tar.gz
> 
> 
> It seems you install the modules in /lib/modules/XXX/i2c etc. instead
> of /lib/modules/XXX/kernel/driver/i2c etc. Is that intentional?
> 
> I got bitten by this since I previously installed the i2c-acpi-ec
> driver in /lib/modules/XXX/kernel/driver/i2c, which apparently took
> precedence over the one installed in /lib/modules/XXX/i2c.

I do this because everything in /lib/modules/XXX/kernel/* gets clobbered 
when you do a make modules_install from the kernel source tree; any 
module not part of the source tree is deleted. That's why external 
modules really don't belong in the /lib/modules/XXX/kernel/* tree -- IMHO.

Of course, this will eventaully be moot, when/if the SBS stuff actually 
gets put into the kernel. I have recently realized that the whole SBS 
functionality can be implemented in terms of control methods in the 
DSDT, without the need for any kernel drivers. It may be interesting to 
have a shot at implementing the SBS this way, and then making some sort 
of autopatch script which adds the SBS code to a supplied DSDT.

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