From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 96157E0078C for ; Tue, 3 Dec 2013 10:31:08 -0800 (PST) Received: by mail-pb0-f46.google.com with SMTP id md12so21608727pbc.19 for ; Tue, 03 Dec 2013 10:31:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rRtJG4kNHoKi3mqkD019dx/hWV8iZIbKPaG180H/ons=; b=hpkscBQrCMcKEsB6Yh3bL2lfFx3Y1BZ2vCdxpkphz5d90qICCeqWzoIo8a4S+s0Vq5 85mDmM6pKivjWdOCc/TMSSI+MZtw/iAzArX98Xr6TC6jSyD6rwTOPGB2+Yho1s0rOnVm xSP/Rc9EutrbiHmsudPrUo6HZegVfjrSJhThbP/KJzCNPV2gh1jg9rrL9VhA/MpEhXAe gGm+YRgHMy26cL/mUK+fZhFZmgnfMh7xbDp/ROyPEQixObQPdktAWHNs+HRFLuz5dvpq p8GXgvEQJIsU6gk6jZMUTjfUTyOe8HY+33e8IIHDTL4XhLFuinuswlFpVA4l9gSChDOc 8a3w== X-Gm-Message-State: ALoCoQnppuTVHadZhsc2/64RqNxX6un92DA3gVC1u2l4iXDlcKX/20E8p8+4OHwb0Sc9xZQlqXNU X-Received: by 10.68.130.234 with SMTP id oh10mr40754899pbb.0.1386095468261; Tue, 03 Dec 2013 10:31:08 -0800 (PST) Received: from [192.168.0.53] ([63.226.49.26]) by mx.google.com with ESMTPSA id ju10sm63121287pbd.33.2013.12.03.10.31.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Dec 2013 10:31:07 -0800 (PST) Message-ID: <529E2368.2020507@boundarydevices.com> Date: Tue, 03 Dec 2013 11:31:04 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Tarek El-Sherbiny References: <529CBE41.2040805@boundarydevices.com> <529DEF57.9040805@boundarydevices.com> <529E098E.7020207@boundarydevices.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: i.MX6q Boot failure using MACHINE=nitrogen6x 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: Tue, 03 Dec 2013 18:31:11 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Tarek, Are you using multiple displays? If not, you're going to want these video=mxcfb1:off video=mxcfb2:off video=mxcfb2:off Otherwise you'll get a default LDB display. You can check this in /sys/class/graphics/fb2/. Did you try running the DVI monitor with "mxc_hdmi.only_cea=0" in your kernel command-line? I'm not sure what dmfc=3 is doing to the display, but I suspect that you're exceeding the bandwidth requirements with multiple displays configured. I'm also not certain what you're running into with the gstreamer build. Regards, Eric On 12/03/2013 10:33 AM, Tarek El-Sherbiny wrote: > Hi Eric, > > On the command line arguments I had dmfc=3. That was set to improve the > IPU performance as I need to play up to 16 streams simultaneously. > When I removed this option the boundary kernel is booting without the > horizontal lines problem. HDMI to DVI is still not working. > > cat /proc/cmdline > console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M > root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off > consoleblank=0 bpp=32 > > > This is fine for know but it would be nice to understand why dmfc is > conflict with boundary kernel. > Also I'm not sure how is this going to affect the IPU performance! > Hope you have an answer to this question so I can fully test the > application. > https://lists.yoctoproject.org/pipermail/meta-freescale/2013-December/005854.html > > Thanks, > Tarek > > > > The command line argument doesn't help: > > console=ttymxc1,115200 video=mxcfb0:dev=hdmi,1920x1080@60 fbmem=24M,10M > root=/dev/mmcblk0p1 rootfs=ext2 rw rootwait enable_wait_mode=off > consoleblank=0 dmfc=3 bpp=32 > > Also > > > > On Tue, Dec 3, 2013 at 4:40 PM, Eric Nelson > > wrote: > > Hi Tarek, > > > On 12/03/2013 08:12 AM, Tarek El-Sherbiny wrote: > > Hi Eric, > > root@nitrogen6x:~# cat /sys/class/graphics/fb0/modes > S:720x480p-60 > S:720x576p-50 > S:1280x720p-50 > S:1280x720p-60 > S:1280x1024p-60 > V:1024x768p-75 > V:1024x768p-70 > V:1024x768p-60 > V:800x600p-75 > V:800x600p-72 > V:800x600p-60 > V:640x480p-75 > V:640x480p-72 > V:640x480p-60 > U:720x400p-70 > D:1360x768p-60 > D:1280x720p-60 > V:640x480p-60 > > > This looks like a pretty standard set of modes for a > 4:3 aspect ratio monitor. > > > root@nitrogen6x:~# cat /sys/class/graphics/fb0/mode > S:1280x1024p-60 > > > This doesn't match one of the CEA modes: > https://github.com/__boundarydevices/linux-imx6/__blob/boundary-imx_3.0.35_4.1.__0/drivers/video/mxc/mxc_edid.__c#L41 > > > Can you boot with this command-line argument? > mxc_hdmi.only_cea=0 > > I think you'll either need that or you'll need to choose a > display resolution from the list. It appears that your monitor > and CEA both like 1280x720@60, though you'll likely get > letter-boxing. > > Regards, > > > Eric > > > > > -- > /Tarek/