Re: i.MX6q Boot failure using MACHINE=nitrogen6x

[Eric Nelson <eric.nelson@boundarydevices.com>]

Hi Tarek,

Are you using multiple displays?

If not, you're going to want these
	video=mxcfb1:off video=mxcfb2:off video=mxcfb2:off

Otherwise you'll get a default LDB display. You can check this
in /sys/class/graphics/fb2/.

Did you try running the DVI monitor with "mxc_hdmi.only_cea=0" in your
kernel command-line?

I'm not sure what dmfc=3 is doing to the display, but I suspect
that you're exceeding the bandwidth requirements with multiple
displays configured.

I'm also not certain what you're running into with the
gstreamer build.

Regards,


Eric

On 12/03/2013 10:33 AM, Tarek El-Sherbiny wrote:
> Hi Eric,
>
> On the command line arguments I had dmfc=3. That was set to improve the
> IPU performance as I need to play up to 16 streams simultaneously.
> When I removed this option the boundary kernel is booting without the
> horizontal lines problem. HDMI to DVI is still not working.
>
> cat /proc/cmdline
> console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
> root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
> consoleblank=0 bpp=32
>
>
> This is fine for know but it would be nice to understand why dmfc is
> conflict with boundary kernel.
> Also I'm not sure how is this going to affect the IPU performance!
> Hope you have an answer to this question so I can fully test the
> application.
> https://lists.yoctoproject.org/pipermail/meta-freescale/2013-December/005854.html
>
> Thanks,
> Tarek
>
>
>
> The command line argument doesn't help:
>
> console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M
> root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off
> consoleblank=0 dmfc=3 bpp=32
>
> Also
>
>
>
> On Tue, Dec 3, 2013 at 4:40 PM, Eric Nelson
> <eric.nelson@boundarydevices.com
> <mailto:eric.nelson@boundarydevices.com>> wrote:
>
>     Hi Tarek,
>
>
>     On 12/03/2013 08:12 AM, Tarek El-Sherbiny wrote:
>
>         Hi Eric,
>
>         root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes
>         S:720x480p-60
>         S:720x576p-50
>         S:1280x720p-50
>         S:1280x720p-60
>         S:1280x1024p-60
>         V:1024x768p-75
>         V:1024x768p-70
>         V:1024x768p-60
>         V:800x600p-75
>         V:800x600p-72
>         V:800x600p-60
>         V:640x480p-75
>         V:640x480p-72
>         V:640x480p-60
>         U:720x400p-70
>         D:1360x768p-60
>         D:1280x720p-60
>         V:640x480p-60
>
>
>     This looks like a pretty standard set of modes for a
>     4:3 aspect ratio monitor.
>
>
>         root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode
>         S:1280x1024p-60
>
>
>     This doesn't match one of the CEA modes:
>     https://github.com/__boundarydevices/linux-imx6/__blob/boundary-imx_3.0.35_4.1.__0/drivers/video/mxc/mxc_edid.__c#L41
>     <https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.1.0/drivers/video/mxc/mxc_edid.c#L41>
>
>     Can you boot with this command-line argument?
>              mxc_hdmi.only_cea=0
>
>     I think you'll either need that or you'll need to choose a
>     display resolution from the list. It appears that your monitor
>     and CEA both like 1280x720@60, though you'll likely get
>     letter-boxing.
>
>     Regards,
>
>
>     Eric
>
>
>
>
> --
> /Tarek/