[Sorry for the DUP, forgot to cc lkml] I just pushed a few changes updating the DRM modesetting sysfs support, both for debugging and eventual HAL friendliness.
So far, the support is limited to describing outputs and generating hotplug events. A typical "card0" directory now looks like this: . |-- card0-DAC-1 | |-- device -> ../../../../../../devices/pci0000:00/0000:00:02.0/drm/card0 | |-- dpms | |-- edid | |-- modes | |-- power | | `-- wakeup | |-- status | |-- subsystem -> ../../../../../../class/drm | `-- uevent |-- card0-LVDS-1 | |-- device -> ../../../../../../devices/pci0000:00/0000:00:02.0/drm/card0 | |-- dpms | |-- edid | |-- modes | |-- power | | `-- wakeup | |-- status | |-- subsystem -> ../../../../../../class/drm | `-- uevent |-- dev |-- device -> ../../../../../devices/pci0000:00/0000:00:02.0 |-- dri_library_name |-- power | `-- wakeup |-- subsystem -> ../../../../../class/drm `-- uevent Each output is listed, prefixed with its associated card number to disambiguate it at the top level /sys/class/drm directory (where it also has some symlinks). Currently, only DPMS, EDID, mode list and connection status properties are exported, but we could list more as needed. You can use 'udevmonitor --env' to look for hotplug events; you should see several at load time, and presumably some at connection hotplug time (though I haven't gotten that working yet, any ideas Jakob?). Any thoughts on the interface? Anything in particular people would like to see? Thanks, Jesse ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
