[meta-freescale] [meta-fsl-arm-extra PATCH v3 2/3] linux-cubox-i: Add Vivante GPU 4.6.9p13 support

Eric Nelson eric.nelson at boundarydevices.com
Thu Jan 30 07:06:46 PST 2014


Hi Carlos,

On 01/30/2014 03:18 AM, Carlos Rafael Giani wrote:
> I did a quick test with a DVI monitor connected to the machine with a
> HDMI-DVI cable. In X11, I get only 1024x768, even though the monitor's
> native resolution is 1280x720. The boot splash and framebuffer console
> work in native 1280x768.
>

I think this is a separate issue. What I saw was 1280x720 properly
negotiated at boot time (the Yocto splash used 1280x720), but
when X started, it requested a mode change to 640x480.

In fact, if I stop X with "/etc/init.d/xserver-nodm stop", the
resolution goes back to 1280x720.

> I have seen a similar problem back then with both framebuffer and X11.
> It was the reason for the cea mode patch in the cubox-i kernel (the
> patch is included in meta-fsl-arm-extra). I suspect something similar is
> going on with the newer Vivante drivers.
>

This is certainly a separate issue, but perhaps related in a weird
way. We also allow non-CEA modes, but have a separate flag to
disable them (mxc_hdmi.only_cea). The reason for this is that
the HDMI audio channel is not clocked properly for non-CEA modes.

Our default boot script disables non-CEA modes by default:
	https://github.com/boundarydevices/u-boot-imx6/blob/production/board/boundary/nitrogen6x/6x_bootscript-yocto.txt#L111

The reason I say this is perhaps related is that our Nitrogen6X-Lite
board didn't have this flag set in its boot script, and negotiated
an 1152x864 resolution.

When it did, the X startup **did not** revert to 640x480.

Regards,


Eric


More information about the meta-freescale mailing list