All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 Peter Bergin <peter.bergin@tritech.se>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Troy <troy.kisky@boundarydevices.com>
Subject: Re: No HDMI signal from Nitrogen6x board with daisy
Date: Fri, 23 May 2014 18:23:19 -0700	[thread overview]
Message-ID: <537FF487.4060702@boundarydevices.com> (raw)
In-Reply-To: <537FEE9F.4040301@boundarydevices.com>

On 05/23/2014 05:58 PM, Eric Nelson wrote:
> Sorry Peter,
>
 > <snip>
 >
> Can you try running this by hand?
>
> U-Boot > setenv bootargs enable_wait_mode=off
> video=mxcfb0:dev=hdmi,1920x1080MR@60,if=RGB24 video=mxcfb1:off
> video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200
> vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2
> mxc_hdmi.only_cea=1
> U-Boot > mmc dev 0 && fatload mmc 0 10800000 uImage && bootm 10800000
>
> I suspect we introduced a bug when pulling our "only_cea" patch
> over to 3.10.17.
>

Sorry about that. I pasted the 3.0.35 kernel parameters and
load commands.

Testing on the same version as you are, I found the same thing
though.

U-Boot > setenv bootargs enable_wait_mode=off 
video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:off 
video=mxcfb2:off video=mxcfb3:off fbmem=28M console=ttymxc1,115200 
vmalloc=400M consoleblank=0 rootwait root=/dev/mmcblk0p2
U-Boot > mmc dev 0 && \
	fatload mmc 0 10800000 uImage && \
	fatload mmc 0 12000000 imx6q-nitrogen6x.dtb && \
	bootm 10800000 - 12000000

Using the clause 'mxc_hdmi.only_cea=1' yields 1080P.
Without it, I get 1024x768.

So the bug is general and not specific to 3.10.17...

It's still not clear why you're getting no display at all
though, or where those IPU_INT_STAT_x or "timeout waiting
for flip irq" messages are coming from.

Can you try out the commands above?

Please advise,


Eric


  reply	other threads:[~2014-05-24  1:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  7:23 No HDMI signal from Nitrogen6x board with daisy Peter Bergin
2014-05-23 12:16 ` Otavio Salvador
2014-05-24  0:18   ` Eric Nelson
2014-05-24  0:58     ` Eric Nelson
2014-05-24  1:23       ` Eric Nelson [this message]
2014-05-26  6:43         ` Peter Bergin
2014-05-27 21:11           ` Eric Nelson
2014-05-28  6:51             ` Peter Bergin
2014-05-28 14:02               ` Eric Nelson
2014-05-28 15:45                 ` Haakon Stende
2014-05-28 16:09                 ` Peter Bergin
2014-05-31  1:54                   ` Eric Nelson
2014-05-31 21:16                     ` Eric Nelson

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=537FF487.4060702@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=peter.bergin@tritech.se \
    --cc=troy.kisky@boundarydevices.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.