From: John Weber <rjohnweber@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
Jacob Kroon <jacob.kroon@gmail.com>,
Trevor Woerner <trevor.woerner@linaro.org>
Cc: meta-freescale <meta-freescale@yoctoproject.org>
Subject: Re: linux-imx/linux-wandboard 3.10.17 kernel and HDMI display
Date: Mon, 24 Mar 2014 11:16:05 -0500 [thread overview]
Message-ID: <53305A45.3060405@gmail.com> (raw)
In-Reply-To: <CAP9ODKqJe3MtOy6LH5RYzDGVnnaK5_GsjxBrfMSiXFLntE36Ww@mail.gmail.com>
Hi Jacob,
On 3/24/14, 10:10 AM, Otavio Salvador wrote:
> Hello Kroon,
>
> On Mon, Mar 17, 2014 at 6:06 AM, Jacob Kroon <jacob.kroon@gmail.com> wrote:
>> Hi,
>>
>> Just some test reporting, I finally got the 3.10.17 linux-imx kernel from
>> meta-fsl-arm working with my Sony TV, but I had to revert commit
>>
>> ce224e3c4fc3c1b00a94641c28724be2adcd78be
>> "ENGR00288972 HDMI: unmask overflow interrupter when HDMI phy power on"
>>
>> otherwise the kernel would lockup once I plugged in the HDMI-cable.
>> This was on a Wandboard Solo. linux-wandboard 3.10.17 kernel from
>> meta-fsl-arm-extra showed the same problem, I didn't test if reverting the
>> same commit would solve the problem but I'm guessing so.
While there are some issues with the 3.10.17 kernel for Wandboard with HDMI, I'm
not aware of this one. Then again, I don't have a Sony HDMI monitor. I've been
working with an Acer 22" monitor with HDMI input. I suspect that most of the
problems I've seen are related to the lack of working EDID on Wandboard.
> Did you find out why this was need?
>
> I am adding John and Trevor in Cc so they can comment on this.
>
next prev parent reply other threads:[~2014-03-24 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 9:06 linux-imx/linux-wandboard 3.10.17 kernel and HDMI display Jacob Kroon
2014-03-24 15:10 ` Otavio Salvador
2014-03-24 15:44 ` Jacob Kroon
2014-03-24 23:54 ` Trevor Woerner
2014-03-25 6:53 ` Jacob Kroon
2014-03-24 16:16 ` John Weber [this message]
2014-03-24 16:44 ` Dmitriy B.
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=53305A45.3060405@gmail.com \
--to=rjohnweber@gmail.com \
--cc=jacob.kroon@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=trevor.woerner@linaro.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 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.