Re: hotkey/video framework [was: [ACPI] ibm-acpi-0.2]

[Karol K. <sz...@he...>]

Thus wrote Yu, Luming:
> >One possibility is to just agree on the proc file format and ACPI
> >events for the common features, then have each driver implement them
> >separately. This would probably be simpler than trying to come up with
> >some sort of a wrapper framework as the code involved is fairly simple
> >and there probably isn't much we can share. Then again, there might
> >be, I haven't looked.
> I think the proposaled framework/abstraction layer is NOT just for 
> code sharing. We need to dynamically load the proper hotkey/video driver

While binding all HIDs in one place should be fairly easy, I don't think I
see an advantage to that as opposed to a modrobe *_acpi solution,
especially now that the fix to acpi_bus_register_driver() is in place.

As for the video, if a certain API was agreed on, the generic driver could
provide an abstraction that vendor-specific drivers could bind on. What I'm
afraid of is that the components and AML code used are so diverse that the
management of such a layer becomes a nightmare.

Best regards,

-- 
Karol 'sziwan' Kozimor
sz...@he...