[meta-freescale] Issues with sync-boundary-changes.patch on imx6qsabrelite
Eric Nelson
eric.nelson at boundarydevices.com
Fri Mar 1 06:15:22 PST 2013
On 03/01/2013 01:28 AM, Andrei Gherzan wrote:
>
>
>
> On Fri, Mar 1, 2013 at 10:06 AM, Andrei Gherzan <andrei at gherzan.ro
> <mailto:andrei at gherzan.ro>> wrote:
>
>
>
>
> On Thu, Feb 28, 2013 at 8:37 PM, Eric Nelson
> <eric.nelson at boundarydevices.com
> <mailto:eric.nelson at boundarydevices.com>> wrote:
>
> On 02/28/2013 11:16 AM, Eric Nelson wrote:
>
> On 02/28/2013 08:34 AM, Andrei Gherzan wrote:
>
>
> On Thu, Feb 28, 2013 at 5:30 PM, Eric Nelson
> <eric.nelson at boundarydevices.__com
> <mailto:eric.nelson at boundarydevices.com>
> <mailto:eric.nelson at __boundarydevices.com
> <mailto:eric.nelson at boundarydevices.com>>> wrote:
>
> Hi Otavio and Andrei,
>
> On 02/28/2013 08:01 AM, Otavio Salvador wrote:
>
> On Thu, Feb 28, 2013 at 11:42 AM, Andrei Gherzan
> <andrei at gherzan.ro <mailto:andrei at gherzan.ro>
> <mailto:andrei at gherzan.ro <mailto:andrei at gherzan.ro>>>
> wrote:
>
> While using imx6, I faced 2 issues after
> updating the kernel
> to ver. / rel.
> 1.1.0:
>
> 1. If i boot the board with hdmi monitor
> connected the boot
> process hangs
> with:
>
> ---
> MIPI DSI driver module loaded
> mxc_sdc_fb mxc_sdc_fb.0: register mxc
> display driver hdmi
> mxc_hdmi mxc_hdmi: Detected HDMI controller
> 0x13:0xa:0xa0:0xc1
> fbcvt: 1920x1080 at 60: CVT Name - 2.073M9
> imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH
> RESOLUTION: 1(0,1),
> 5B(2~5), 5F(6,7)
> Console: switching to colour frame buffer
> device 240x67
> mxc_sdc_fb mxc_sdc_fb.1: register mxc
> display driver lcd
> mxc_sdc_fb mxc_sdc_fb.2: register mxc
> display driver ldb
> _regulator_get: get() with no identifier
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 0(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 1(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 2(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 3(VIC 1):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 4(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 5(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 6(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 7(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 8(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 9(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 10(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 11(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 12(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 13(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 14(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 15(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 16(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 17(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 18(VIC 0):
> mxc_hdmi mxc_hdmi:
> mxc_hdmi_edid_rebuild_____modelist: Added
> mode 19(VIC 0):
> fbcvt: 1920x1080 at 60: CVT Name - 2.073M9
> mxc_sdc_fb mxc_sdc_fb.3: register mxc
> display driver ldb
>
> >
>
> This all looks valid, though things shouldn't hang
> here.
> ---
>
> Additional infos:
>
> $ cat
> /sys/devices/platform/mxc_sdc_____fb.0/graphics/fb0/modes
> V:640x480p-60
> U:640x480p-60
> Was this from a boot without the HDMI monitor
> connected? The mxc_hdmi
> driver should list all of the display resolutions
> supported by the
> monitor as reported by EDID.
>
>
> Nope. This is from a boot with HDMI monitor connected.
>
> Kernel command line: console=ttymxc1,115200
> console=ttymxc1,115200
> root=/dev/sda2 rootwait
>
> video=mxcfb0:dev=hdmi,____1920x1080M at 60,if=RGB24
>
>
> When trying to reproduce things, I noted a
>
> -- You have two 'console=ttymxc1,115200' clauses here
>
> -- You appear to be using SATA (/dev/sda2). For SD card boot,
> this should be /dev/mmcblk0p2 with a Yocto-standard image
>
> -- There's some extraneous stuff (__) in your video= clause
>
> I just booted with a slightly modified kernel command-line
> to try
> and match yours:
> Kernel command line: console=ttymxc1,115200
> video=mxcfb0:dev=hdmi,__1920x1080M at 60,if=RGB24 fbmem=48M
> vmalloc=400
> root=/dev/mmcblk0p1 rootwait
>
> What I found is that things booted, and I got a login prompt
> on the
> serial console, but my display isn't functioning properly.
>
>
> Hi Andrei,
>
> A couple of other things I noticed:
> - The serial port clock appears to get screwed up at around
> the point at which you say things hang. This is due to
> a recurring issue related to re-parenting of some of the
> clocks and will need to be addressed.
>
> For me, this causes a bunch of garbage, but my serial
> port and terminal emulator recover after ~1k of garbage.
>
> You might want to try restarting the terminal emulator
> you're using.
>
> - I don't trust my Yocto image. I tried to pull in the
> 1.1.0 patch set unsuccessfully and even the stock
> 720P resolution isn't working for me. I get the Yocto
> splash screen, but my X Server is dying.
>
> I'll re-build, but it will take hours. Meanwhile, can
> you try using the stock 6x_bootscript, which should
> come up at 720P?
>
>
> Where can I find this stock script? I would kindly test it.
>
>
> There is another strange issue. By not applying this patch the issues on
> hdmi are not reproducible anymore but the second issue is still
> reproducible on lvds...
>
Which patch and which issue?
This chain has gotten rather long.
Please advise,
Eric
More information about the meta-freescale
mailing list