Thanks Diego,
On 01/29/2014 08:56 AM, Diego wrote:
Eric Nelson wrote:
I'm not sure if this is the right patch to tag, but during my testing of
the Vivante/X integration, I saw some issues related to mode settings.
On Nitrogen6x Quad core, I'm seeing X start up with a mode of 640x480,
on the HDMI device even though the kernel command line is configured
for 720P.
The same is not true with the same monitor and Nitrogen6_Lite (Solo
processor):
The prime leads are these from Xorg.0.log (attached):
[3585503.788] (II) VIVANTE(0): Output DISP3 BG - DI1 connected
[3585503.788] (II) VIVANTE(0): Using exact sizes for initial modes
[3585503.788] (II) VIVANTE(0): Output DISP3 BG - DI1 using initial mode
V:640x480p-60
[3585504.480] (II) VIVANTE(0): imxDisplayPreInit: virtual set 640 x 480,
display width 0
[3585504.480] (II) VIVANTE(0): FBDevPreInit: adjust display width 640
Oddly, the display reverts to 720p (1280x720) if I stop X.
This appears using either kernel version 3.0.35 or 3.10.17.
I'm continuing to investigate, but thought I'd send out a note
in case others are seeing similar behaviour or know what might
be involved here.
I confirm I have the same issue, X is starting per default at 640x480 on HDMI,
which is not a good default.
I can subsequently change the resolution to 1280x720 or 1920x1080 with xrandr.
I just tested on SABRE SD to remove the possibility that one of
our kernel patches was coming into play and found the same result:
root@imx6qsabresd:~# cat /proc/cmdline
video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:off
video=mxcfb2:off video=mxcfb3:off console=ttymxc0,115200
root=/dev/mmcblk0p2 rootwait rw
root@imx6qsabresd:~# cat /sys/class/graphics/fb0/mode
U:640x480p-60
Regards,
Eric
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
