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
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
