From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com [209.85.160.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by yocto-www.yoctoproject.org (Postfix) with ESMTPS id 0EB13E0070F for ; Fri, 1 Mar 2013 06:14:01 -0800 (PST) Received: by mail-pb0-f45.google.com with SMTP id ro8so1763421pbb.32 for ; Fri, 01 Mar 2013 06:14:00 -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=/czgRJSctW5Cm3tTYz6mWAcoHZtfoy6oN2pk4Y+AQJM=; b=ReV4/5J5gYlZWP0CwmeTtZaI/6j6nRwV3vpIOv4Y26no7cuMepLiDeTyKXIbYPkmFJ eGRKG+WgcmTi1yn4TrwIUBh7uLoFcFXEo7Vjzvwqpb2nW4KDxD+i4dFIoccl+iAUjX6k QBhSlgMxFDeLE8cZUxtuIJ9YXjr7BXtl0lB94wVFftkWfzi7jNp97Kep1V5ImbTn9HLA HPe5VgyVPokmJsY1f7IxPloIVMc1kHjF27LNPmhwJIAgyIExOnSHj7QVZmHxkhCD5h7x +xANRMkqCimG7DZzkkAl7HaW9oYKtnLBmaXiGqhNCohGX0IMgl7nR4HmftCaLYppnK/Q 1pXQ== X-Received: by 10.68.211.8 with SMTP id my8mr14777490pbc.7.1362147240709; Fri, 01 Mar 2013 06:14:00 -0800 (PST) Received: from [192.168.1.3] (ip98-165-108-80.ph.ph.cox.net. [98.165.108.80]) by mx.google.com with ESMTPS id i10sm12197995pbd.1.2013.03.01.06.13.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Mar 2013 06:13:59 -0800 (PST) Message-ID: <5130B7A4.5090303@boundarydevices.com> Date: Fri, 01 Mar 2013 07:13:56 -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> <512FA3F2.8030801@boundarydevices.com> In-Reply-To: X-Gm-Message-State: ALoCoQkPv8IZUUQch8q4fWFqM0FCIjQof4bKhtCGCs5C2A3h8OVDllCmYnctXsE80vxgQxzathTy 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: Fri, 01 Mar 2013 14:14:01 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 03/01/2013 01:06 AM, Andrei Gherzan wrote: > > > > On Thu, Feb 28, 2013 at 8:37 PM, Eric Nelson > > 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 > > >> 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? > > > Where can I find this stock script? I would kindly test it. > Hi Andre, This should be installed as a part of the Yocto SD card image. I built using "nitrogen6x" machine type and found that there's a copy of the script in: build/tmp/deploy/images/6x_bootscript-nitrogen6x How are you currently setting your bootargs in U-Boot? The stock script uses HDMI detection and sets up 720P along with other arguments: https://github.com/boundarydevices/u-boot-imx6/blob/production/board/boundary/nitrogen6x/6x_bootscript.txt Ahh. Never mind. I just found out how you're doing this, and oddly, it has my name as the author! https://github.com/Freescale/meta-fsl-arm-extra/commit/ebcb70c68a30bd0d07220d61a378488a512aa6c1 So you're setting and saving 'bootargs' with your video settings directly. If you add this bit, things should work for you. 'video=mxcfb1:off video=mxcfb2:off' Note that you might also need 'enable_wait_mode=off'. We saw some issues during early startup that still haven't been addressed as discussed here: http://boundarydevices.com/wait-a-second-hopefully-less/ Regards, Eric