From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by yocto-www.yoctoproject.org (Postfix) with ESMTPS id EBDADE00348 for ; Thu, 28 Feb 2013 10:37:42 -0800 (PST) Received: by mail-pa0-f54.google.com with SMTP id fa10so1290741pad.41 for ; Thu, 28 Feb 2013 10:37:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=XnHBW6KmzubX2LLM/YeJMFWawreJOQ4YtEoFIPwo3ns=; b=FwFpDgBO6jXMYPcFQ0kVKls6K+6BePQo+gcYhurgV0bTzOv1aV2e7IFF4j4jOy7Aks Z0L4fWDVvafzOXrIp1UiApNi0q/nCrfwpRdv8ZBSdEaedpctE19k/RrGF3N2gf+JMNuX WzeRHwQM1wrBn8Bfrs35XizwTDluidgaimfjqRoO3XEengV0t61OlxkhlaC0Ou7o9ouG 88/E2u4/VFR2kyZxRlYEQXsU1Ekb9+xeTkEGTHNLLH/cTus1cOHmjBOK7eWA8bs0/UA+ dlBTK3Tb6R0TM7L52rKUQqZdDXbIxrFwE0DSYdPqauHzMfxt+E7DddUWdSRY58/Wy/Ta e2lA== X-Received: by 10.66.52.116 with SMTP id s20mr14904211pao.70.1362076662446; Thu, 28 Feb 2013 10:37:42 -0800 (PST) Received: from [192.168.0.55] ([70.96.116.236]) by mx.google.com with ESMTPS id hu2sm9134127pbc.38.2013.02.28.10.37.40 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 10:37:41 -0800 (PST) Message-ID: <512FA3F2.8030801@boundarydevices.com> Date: Thu, 28 Feb 2013 11:37:38 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Andrei Gherzan References: <512F7827.5040901@boundarydevices.com> <512F9EFF.1000409@boundarydevices.com> In-Reply-To: <512F9EFF.1000409@boundarydevices.com> X-Gm-Message-State: ALoCoQlA75zphSzH9kBuTU3quTanbii7kp8AMEOMwfESmLlA6+tv6h2qjL5mEmOkr+l2M+ozGp+f Cc: "meta-freescale@yoctoproject.org" , Otavio Salvador Subject: Re: Issues with sync-boundary-changes.patch on imx6qsabrelite X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 18:37:43 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 >> > > 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 >> > 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@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@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@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@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? Regards, Eric