From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: dri-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: DRM modesetting & sysfs
Date: Tue, 8 Apr 2008 13:17:43 -0700 [thread overview]
Message-ID: <200804081317.43712.jbarnes@virtuousgeek.org> (raw)
[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
next reply other threads:[~2008-04-08 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 20:17 Jesse Barnes [this message]
2008-04-09 8:57 ` Jakob Bornecrantz
2008-04-09 15:17 ` Jesse Barnes
2008-04-09 16:15 ` Alan Hourihane
2008-04-09 16:34 ` Jesse Barnes
2008-04-09 17:23 ` Alan Hourihane
2008-04-09 17:39 ` Jesse Barnes
2008-04-09 18:12 ` Jesse Barnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200804081317.43712.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®