Adding PMU and ACPI into HAL

[Richard Hughes]

On Mon, 10 Jan 2005 15:53:25 -0500, David Zeuthen wrote:
>> I thought you might say that.
>> What about info.bus = 'logical'
> 
> Maybe, I'm thinking of ditching info.bus for non-physical devices (in
> this case one can consider ACPI and PMU non-physical and rather logical
> device since those interfaces represent properties on the low-level
> system firmware).

info.device_type = logical | physical ?

> I think it makes sense to make a distinction between acpi_button and
> acpi_battery since the add-ons and eventually exported interfaces should
> live in different binaries.

Okay, you're the boss :-)

>> Sure I'll start reading lots of code... :-)
> Cool, this should be easy to port over to the new backend I'm working
> on.

Copy/paste :-)

> ACPI shouldn't need this, no. For example, the new backend I'm working
> on invokes a binary called probe-input that opens the device and 
> determines whether the input device got relative axes, absolute axes
> and the keys that keyboards normally got. Just as a proof of concept.

Cool.
 
Thanks for all your assistance and help David, I'm learning fast.

Richard

_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal