From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Liviu Dudau <liviu-I3yL/QOVVjH10XsdtD+oqA@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Trimslice Barebone fails to detect HDMI connection, no DDC i2c channel present
Date: Wed, 11 Dec 2013 15:17:23 -0700 [thread overview]
Message-ID: <52A8E473.8050502@wwwdotorg.org> (raw)
In-Reply-To: <20131211214911.GA24176-hOhETlTuV5niMG9XS5x8Mg@public.gmane.org>
On 12/11/2013 02:49 PM, Liviu Dudau wrote:
> Hello,
>
> Prompted by a discussion on G+, here is a report of an issue I'm seeing
> with mainline kernel (commit 78fd82238d0e57).
>
> The kernel fails to detect the DDC i2c interface (on Trimslice that's
> on Tegra2 I2C-0 interface), so I'm getting no output on the HDMI
That probably should be I2C-1 for HDMI; I2C-0 is likely the DVI port's
DDC interface. But since you tested all ports, this isn't the cause of
the problem.
> U-Boot 2014.01-rc1-dirty (Nov 26 2013 - 22:29:37)
Are you using an unmodified upstream U-Boot? The environment you posted
doesn't match upstream's environment, and the "-dirty" implies you have
some local modifications.
If you break into U-Boot, can you read the EDID using the "i2c" command?
In Linux, can you "i2cget" from bus 1 device 0x50 even if "i2cdetect"
didn't see the EDID?
Is the monitor you have plugged in known-working without any
EDID-related issues?
next prev parent reply other threads:[~2013-12-11 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 21:49 Trimslice Barebone fails to detect HDMI connection, no DDC i2c channel present Liviu Dudau
[not found] ` <20131211214911.GA24176-hOhETlTuV5niMG9XS5x8Mg@public.gmane.org>
2013-12-11 22:17 ` Stephen Warren [this message]
[not found] ` <52A8E473.8050502-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-12-11 22:54 ` Liviu Dudau
[not found] ` <20131211225401.GB24176-hOhETlTuV5niMG9XS5x8Mg@public.gmane.org>
2013-12-11 23:02 ` [Solved] " Liviu Dudau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A8E473.8050502@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liviu-I3yL/QOVVjH10XsdtD+oqA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.