From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-fbdev@vger.kernel.org
Subject: q: monitor hotplug with fbdev?
Date: Fri, 28 May 2010 10:25:05 +0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1005281208120.32352@axis700.grange> (raw)
Hi all
What's the correct driver behaviour on detected monitor unplu / replug
events? Possibly, of a different monitor, maybe with a different
resolution? I see an attempt to support this in the via FB driver, but
that hot-plug rather reminds some kind of a cold-plug: it is triggered by
a VIA-specific ioctl. Even DRM/KMS subsystem doesn't seem to be doing much
upon such hotplug events to inform /dev/fb* users?
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
reply other threads:[~2010-05-28 10:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.1005281208120.32352@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-fbdev@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