From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Jakob Bornecrantz" <wallbraker@gmail.com>
Cc: dri-devel@lists.sourceforge.net,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: DRM modesetting & sysfs
Date: Wed, 9 Apr 2008 08:17:02 -0700 [thread overview]
Message-ID: <200804090817.02836.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <427ca1a20804090157t4fa1bbcei27d3bbea085aa9c3@mail.gmail.com>
On Wednesday, April 09, 2008 1:57 am Jakob Bornecrantz wrote:
> I was going to suggest that you plug it into the hotplug_stage_two
> function but it looks like you have already done that. Things might be
> routed differently now then since the last time I looked at the code,
> are you sure that stage_two is being run?
I'll have to check, I'm not sure I'm even getting interrupts...
> > Any thoughts on the interface? Anything in particular people would like
> > to see?
>
> Looks good, can you write to dpms, that is turn a monitor on and of,
> that would be slightly cool but not overly useful. On the whole I
> think exporting properties are fine, but I don't think setting modes
> and crtc's are to be done in sysfs. However it is entirely possible.
Agreed. I view this more as a way of exporting information about the DRM
configuration to userspace rather than a way to control the whole thing. I
think we should stick with ioctls for the latter... Anyway thanks for
checking it out.
Jesse
next prev parent reply other threads:[~2008-04-09 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 20:17 DRM modesetting & sysfs Jesse Barnes
2008-04-09 8:57 ` Jakob Bornecrantz
2008-04-09 15:17 ` Jesse Barnes [this message]
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=200804090817.02836.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wallbraker@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.