From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 822CFE016F4 for ; Mon, 14 Oct 2013 17:30:26 -0700 (PDT) Received: by mail-pb0-f47.google.com with SMTP id rr4so7954657pbb.20 for ; Mon, 14 Oct 2013 17:30:26 -0700 (PDT) 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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vKDvha+d5/E1y0ranx9XUL6QdxTfM6nerRYw6kzSxLw=; b=Uf5nYsF3yyUJskwXMJllm406BugQwBRlIsZ8Fycm4SzahgI7BZwUpZWAHBqp/1hr2X DIFJp5nuTvNZpvJewthrPG5Gpg43kg18xUsGzLRkJx7Fy6TW+sRmiTD2W7hrEM44kDTo dz4MyCsOQMJT3dy7VBwmZO8aMkfH6PSt29Ch2FnKSERpfwANIDhSEe30o71DzlOwll6q GbfUCXFBiNlkMl83gPdiPhrD0h5fb2OywIAtWrxoIgcE4Zl9ELYYwqLKddw2A/zOQm2+ LQsamSf0PI16ih0ytTTjSQl+urWRXiFHXkRyee4bFsFPWhssWHDRgHvhgpWwOanCRlkk Ntaw== X-Gm-Message-State: ALoCoQmTnfioaBv6pyHDI1poQZ7wHUu6/iWxkCazMCR1rdo/b+6cLQs4ILbmwTC3NxBT7vi10/vw X-Received: by 10.68.137.138 with SMTP id qi10mr11942698pbb.113.1381797026126; Mon, 14 Oct 2013 17:30:26 -0700 (PDT) Received: from [29.6.1.4] ([70.96.116.236]) by mx.google.com with ESMTPSA id kd1sm94401170pab.20.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Oct 2013 17:30:25 -0700 (PDT) Message-ID: <525C8C9E.5010708@boundarydevices.com> Date: Mon, 14 Oct 2013 17:30:22 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: =?UTF-8?B?Sm9zZSBNwqogRmVycmVpcm8=?= , meta-freescale@yoctoproject.org References: <5257E0EE.80802@horus.es> <5258163C.6050705@boundarydevices.com> <5258403F.5070000@horus.es> <52584650.3040201@boundarydevices.com> <525849BC.3010806@horus.es> <5258777B.9030103@boundarydevices.com> <525BBC2B.3080807@horus.es> In-Reply-To: <525BBC2B.3080807@horus.es> Subject: Re: HDMI on SABRE Lite (was FlexCAN not working) 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, 15 Oct 2013 00:30:31 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Jose, On 10/14/2013 02:40 AM, Jose Mª Ferreiro wrote: > > El 12/10/2013 0:11, Eric Nelson escribió: >> On 10/11/2013 11:55 AM, Jose Mª Ferreiro wrote: >> >>> >>> You are correct. I didn´t look well for it. It seems as it depends on a >>> third GPIO signal to select one transceiver or the other. We will test >>> it on monday. >>> >>> I would like to use linux-boundary, wich was the default, but we have to >>> change to linux-imx due to video issues that did not work on >>> linux-boundary: something about mfw_isink i think. >>> >> >> Can you elaborate? I'm not aware of any board-specific code in >> mfw_isink, and certainly not in the Nitrogen6x code. > > Hi and sorry, Eric > > I was wrong. We were testing several things at the time. The problem was > not with mfw_isink. The problem was with HDMI. We have a Samsung > S22B300H monitor connected to our Sabrelite board through HDMI. > Okay, so we switched topics here. > When linux-boundary is starting it shows many hdmi messages until it > gets hanged when trying to start XServer. At both resolutions: 1920x1080 > and 1280x720 (attached startup log). With linux-imx, it starts without > problems and the image is good. > From the log, it appears that the HDMI driver is detecting a disconnect and re-connect. If you're not seeing this with the fslc kernel, the problem must stem from this patch, which added support for DVI monitors into the HDMI driver: https://github.com/boundarydevices/linux-imx6/commit/c0439e262bb6c23887d96466b2ab7916aa0488d9 > If we connect a DVI monitor to the HDMI SabreLite output we can work > with linux-boundary at 1280x 720 but we have no image with 1920x1080. > That's odd. We put this patch in place to support DVI. On the older fslc kernel, most DVI monitors would fail the detect logic as described here: http://boundarydevices.com/dvi-support-on-i-mx6-boards/ Are you in a position to revert the patch above? Do you see the Linux penguins during the boot process? If so, I've been wanting to test a patch to ignore disconnect events and this may be a good time to do so. Since many of our customers are operating signage apps and the like, it's useful to simply force detection and be done with the process. Please advise, Eric