Hi, I'm attaching a first draft of my work. The first 3 patches are infrastructure work, the fourth wires the notification handler and retrieves the requests from the system BIOS, but it does not actually change brightness yet.
The problem here is how to get the correct encoder: should I just scan encoder_list checking for ATOM_DEVICE_LCD_SUPPORT and see if it has a backlight device attached? Hopefully there is only one encoder with it, right? I'm also toying with the idea of creating structures matching the output of the various ACPI methods, this would remove some ugly pointer arithmetics, but it _might_ make it easier to read past the buffer if one does not check the size before using the struct. What do you think? Luca -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-drm-radeon-refactor-radeon_atif_call.patch Type: text/x-diff Size: 2233 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120729/3d5d47fc/attachment.patch> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-drm-radeon-implement-radeon_atif_verify_interface.patch Type: text/x-diff Size: 5331 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120729/3d5d47fc/attachment-0001.patch> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0003-drm-radeon-implement-wrapper-for-GET_SYSTEM_PARAMS.patch Type: text/x-diff Size: 3101 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120729/3d5d47fc/attachment-0002.patch> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0004-drm-radeon-implement-skeleton-handler-for-ACPI-event.patch Type: text/x-diff Size: 3696 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20120729/3d5d47fc/attachment-0003.patch>
