From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Carlos Rafael Giani <dv@pseudoterminal.org>,
meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm-extra PATCH v3 2/3] linux-cubox-i: Add Vivante GPU 4.6.9p13 support
Date: Thu, 30 Jan 2014 08:06:46 -0700 [thread overview]
Message-ID: <52EA6A86.4090906@boundarydevices.com> (raw)
In-Reply-To: <52EA2712.10807@pseudoterminal.org>
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
next prev parent reply other threads:[~2014-01-30 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 20:10 [meta-fsl-arm-extra PATCH v3 0/3] Add Vivante 4.6.9p13 GPU support Otavio Salvador
2014-01-29 20:10 ` [meta-fsl-arm-extra PATCH v3 1/3] linux-wandboard (3.0.35): Add Vivante GPU 4.6.9p13 support Otavio Salvador
2014-01-29 20:10 ` [meta-fsl-arm-extra PATCH v3 2/3] linux-cubox-i: " Otavio Salvador
2014-01-30 10:18 ` Carlos Rafael Giani
2014-01-30 15:06 ` Eric Nelson [this message]
2014-01-29 20:10 ` [meta-fsl-arm-extra PATCH v3 3/3] linux-boundary (3.0.35): " Otavio Salvador
2014-01-30 22:33 ` [meta-fsl-arm-extra PATCH v3 0/3] Add Vivante 4.6.9p13 GPU support John Weber
2014-02-03 20:21 ` Otavio Salvador
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=52EA6A86.4090906@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=dv@pseudoterminal.org \
--cc=meta-freescale@yoctoproject.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.