From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 00/15] ARM: mach-shmobile: HDMI hot-plug and improvements
Date: Tue, 14 Sep 2010 08:31:45 +0000 [thread overview]
Message-ID: <20100914083145.GL7336@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1009030856020.2883@axis700.grange>
On Fri, Sep 03, 2010 at 09:19:45AM +0200, Guennadi Liakhovetski wrote:
> The main purpose of this patch set is supporting dynamic framebuffer
> reconfiguration upon monitor hot-plug. The good thing is - it works. The
> not so good thing is - only to the extent, that the current fbdev API
> allows. Specifically, there is currently no possibility under the fbdev
> API to inform framebuffer users about a changed framebuffer configuration,
> as can easily be the case, when a new monitor has been plugged in. It is,
> however, possible to inform in-kernel framebuffer users, e.g., the fbcon
> console, about such a change, using framebuffer notifications. This patch
> series implements support for monitor hot-plug on the hardware level,
> i.e., the LCD and HDMI controllers get reconfigured for a new device. The
> user configuration remains untouched. With this approach with a new
> monitor plugged in, the user either gets to see the upper left corner of
> the framebuffer image, or the whole framebuffer will be displayed in the
> upper left corner of the display.
>
> The patch series also contains a number of improvements to both the lcdc
> and hdmi SH-Mobile drivers.
>
> Based on the current (commit 410d878b) genesis-2.6/master tree.
>
Applied, thanks.
prev parent reply other threads:[~2010-09-14 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 7:19 [PATCH 00/15] ARM: mach-shmobile: HDMI hot-plug and improvements Guennadi Liakhovetski
2010-09-14 8:31 ` Paul Mundt [this message]
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=20100914083145.GL7336@linux-sh.org \
--to=lethal@linux-sh.org \
--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;
as well as URLs for NNTP newsgroup(s).