From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by yocto-www.yoctoproject.org (Postfix) with ESMTPS id D55B7E002AB for ; Thu, 28 Feb 2013 10:16:36 -0800 (PST) Received: by mail-pa0-f43.google.com with SMTP id bh2so1292693pad.2 for ; Thu, 28 Feb 2013 10:16:36 -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=4jvidz1t1kX6vaO37/WxC4zxUaBjcJIs8z33sXtG7QI=; b=iNS6YPUBkFKciJXh8e6UgImKjSwKm7dl+kfDa8izfOGGrkNaCodyg2G6edfKmalTSm VjLoaN5kGdMzdsihXJrcdfJMgMWHXI0u/NVc7VXjRWE1NdhXm8f0KqUJI61NDR/2xh19 sx34ccsxDc23uWRhcL7zMrFTW+tfitNvY4aCgnFrh4rS8Px4xFqkdB7BqT1TR3hgvHbU B//59E4h0F6FexDarl4fkWvcJu8zcF9tZF780zM68TdmAmCKlYjYJAYBYxoqpkaI8dID CdFipJ5hkNJwJzpvi+noQkRVfJ1DJ/7u2ELFsF1Zbqg5W8DBVPPxVFAPclEYfYnGubas EJnA== X-Received: by 10.66.162.41 with SMTP id xx9mr14728118pab.168.1362075396614; Thu, 28 Feb 2013 10:16:36 -0800 (PST) Received: from [29.6.1.52] ([70.96.116.236]) by mx.google.com with ESMTPS id z6sm10006396pav.3.2013.02.28.10.16.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 10:16:35 -0800 (PST) Message-ID: <512F9EFF.1000409@boundarydevices.com> Date: Thu, 28 Feb 2013 11:16:31 -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> In-Reply-To: X-Gm-Message-State: ALoCoQlG5RnFAGaQ6jAPo/6lm2mCkXcNNHq499DXP05wL6pwwA8L/pSyAI3/5YyiY422AKulEI6M 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:16:36 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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. > > You'll need to add a an 'fbmem=' clause to the kernel command line. > For 1080P, I think this should be ~48M and you may need a 'vmalloc' > clause: > root=/dev/sda2 rootwait console=ttymxc1,115200 > video=video=mxcfb0:dev=hdmi,__1920x1080M@60,if=RGB24 fbmem=48M > vmalloc=400 > > 2. The first client connected to X server won't show > anything on screen. But > absolutely anything -without seeing any issues /errors / > warnings. > Restarting application everything works OK. And until reboot > no related > issues. After a reboot, the same behavior. > > So I've been struggling to get these fixed and search for > the source of the > problem. I was pretty sure that was something related to > kernel so I tried > some bisects with no luck. After some digging a realized the > issue was > something inside the sync-boundary-changes.patch. Without > this patch 1) and > 2) are fixed. > > I will take a look as we know the source of the problem now. > But maybe > somebody who already knows this patch can work with me in > parallel. > > > Eric, is it a known issue? > > > I'll try to reproduce when I get into the office. > > > Thanks. > > > -- > *Andrei Gherzan* > m: +40.744.478.414 | f: +40.31.816.28.12