From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id AF8F4E008C3; Thu, 13 Nov 2014 14:22:48 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [193.201.172.117 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx1.mail.bg (mx1.mail.bg [193.201.172.117]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7F83FE00831 for ; Thu, 13 Nov 2014 14:22:45 -0800 (PST) Received: from [192.168.0.40] (unknown [93.152.132.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.mail.bg (Postfix) with ESMTPSA id 0AA3C600070C; Fri, 14 Nov 2014 00:22:44 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1415917364; bh=IVMgTgKp5HmrY3OQ4tPm+6bNQ+w3jHB16K0NHsfcRC0=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=vdDLLCh81QIp+6Ne6wOnbp+1hYce6D6KHOqZNprN4hgLxbZnkbCgsN73El3mWYDCc J/TgTMEqHkDZBOt1p0tgAkcty1qETt8xuqQHQPb+2CtwTcH1qGcWSLcahdPdGZVq3S wVXKxu/7TX+LXSWhNMpNHLoP2Zw/34bo8Rajfdwc= Message-ID: <54652F33.9070309@mail.bg> Date: Fri, 14 Nov 2014 00:22:43 +0200 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0 MIME-Version: 1.0 To: Daiane Angolini References: <5463E620.70400@mail.bg> <5464CA03.5090505@mail.bg> <5464EE91.70507@mail.bg> <546507CD.60309@mail.bg> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: No HDMI video on imx6qsabresd with dizzy 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, 13 Nov 2014 22:22:48 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Daiane, On 11/13/2014 10:50 PM, Daiane Angolini wrote: > On Thu, Nov 13, 2014 at 5:34 PM, Nikolay Dimitrov wrote: >> Hi guys, >> >> Thanks to Fabio the HDMI is now working. Here's how: >> >> 1. Disabled HDMI support in u-boot-fsl (actually disabled all video- >> related support, as it was easier/faster). >> 2. Added the usual video configuration to "mmcarg" env-var: >> >> video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB24 >> >> 3. Booted the board (had to set mmcdev to 0 as I boot from SD2). >> 4. Observed that Xorg was running on the HDMI screen. >> 5. Played video via gstreamer and observed it's rendering on the screen >> without issues. >> >> After discussion with Andreas, I tested the following resolutions and >> they worked OK: >> >> - 640x480 >> - 800x600 >> - 1024x768 >> - 1280x720 >> (just don't have the time to test more as these were OK for my tests) >> >> @Daiane: I checked the description for bug #6703, but I don't observe >> the issue here. I left my HDMI cable connected all the time, and it >> still works. I even power-cycled the board to make sure that the HDMI >> hardware is not left initialized from a previous boot. My understanding >> is that the reason it works is Fabio's suggestion to disable U-Boot >> HDMI support. > > You are right, Nikolay, and if you see [1], the second comment, I > suggest turning of HDMI as a workaround, but using LVDS instead. > > However, I got confused when you said you have never reproduced the > error regarding plug/unplug the cable. > Do you mean you was not able to reproduce it *after* get it fixed, or > you have never been able? Sorry for the confusion. After I modified U-Boot, I didn't observed the issue. Btw, after seeing your comment I went and reverted the change just to be sure what's happening. And it turned out that you're right, the issue can again be reproduced as described in #6703. Just to be more clear, here's what I've tested: 1. Unmodified U-Boot, HDMI cable connected during power-on: kernel hangs 2. Unmodified U-Boot, HDMI cable connected later: works OK 3. Disabled U-Boot video, HDMI cable connected during power-on: works OK 4. Disabled U-Boot video, HDMI cable connected later: works OK > I would like to have you updating the bug with your workaround. Could > you, please leave a comment there with your how-to? Sure, np. Regards, Nikolay