linux-kernel - DRM modesetting & sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200804081317.43712.jbarnes@virtuousgeek.org>
Date:	Tue, 8 Apr 2008 13:17:43 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	dri-devel@...ts.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: DRM modesetting & sysfs

[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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/