From: Magnus Damm <magnus.damm@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/6] fbdev: sh-mobile: HDMI support for SH-Mobile SoCs
Date: Thu, 01 Jul 2010 09:30:37 +0000 [thread overview]
Message-ID: <AANLkTimFd21-FyUr-a7bJOAWqNiQSffD7KGNmxvu6qGD@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1006301128310.17489@axis700.grange>
Hi Guennadi,
On Wed, Jun 30, 2010 at 6:55 PM, Guennadi Liakhovetski
<g.liakhovetski@gmx.de> wrote:
> This patch set adds a static HDMI support to SH-Mobile SoCs, specifically,
> to sh7372 (ap4evb) in this version. "Static" means only 720p is supported
> ATM. Also hotplug support is implemented without changing the framebuffer
> geometry. Dynamic geometry reconfiguration is planned for a future patch.
I just gave your patches a quick try, and they seem to work fine on my
AP4EVB board.
The timings are not perfect for my 16:9 LG monitor, but this is much
better than nothing. I suppose next step will be to parse the EDID and
dynamically configure the LCDC. This version ties in the LCDC, but
does nothing with sound, right?
With this set of patches the HDMI port comes up as /dev/fb1. My AP4EVB
board does not have any LCD panel mounted - both MIPI-DSI ports are
empty and I have not bothered attaching the Ecovec WVGA panel. I've
heard that's the case for most AP4EVB boards these days. So /dev/fb0
ends up being unused.
Not sure how to get console output to /dev/fb1 easily - in my quick
test I ended up removing the LCDC0 platform devices to get the HDMI on
/dev/fb0. Also, I'm very sad to discover that the penguin is gone. I
wonder why, hint-hint. =)
I'll look at the patches in more detail tomorrow.
Thanks!
/ magnus
next prev parent reply other threads:[~2010-07-01 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 9:55 [PATCH 0/6] fbdev: sh-mobile: HDMI support for SH-Mobile SoCs Guennadi Liakhovetski
2010-07-01 9:30 ` Magnus Damm [this message]
2010-07-02 9:18 ` Guennadi Liakhovetski
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=AANLkTimFd21-FyUr-a7bJOAWqNiQSffD7KGNmxvu6qGD@mail.gmail.com \
--to=magnus.damm@gmail.com \
--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).