From: Mark Zhang <markz-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Alex Courbot <acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2] ARM: tegra: ventana: enable internal display
Date: Mon, 19 Nov 2012 10:55:42 +0800 [thread overview]
Message-ID: <50A99FAE.3080207@nvidia.com> (raw)
In-Reply-To: <2481172.Lt8JIisq3X@percival>
Yep, I remember that I fetched EDID data by i2cget several months ago.
But I'll try this again today to make sure.
Mark
On 11/16/2012 03:51 PM, Alex Courbot wrote:
> On Friday 16 November 2012 15:44:51 Alexandre Courbot wrote:
>> Enable host1x and add the rgb output, providing EDID as a binary blob.
>
> I would really prefer to have the EDID data fetched from DDC, but all my
> attempts have failed so far. I don't even see the DDC wires on the platform
> design guide. Mark, are you sure the EDID data you fetched with i2cget was
> actually on Ventana? I can see that the DDC lines of T2 are connected to the
> corresponding lines of the HDMI interface, but nothing similar regarding
> internal display.
>
> Maybe we can work this out privately, on IRC?
>
> Alex.
>
next prev parent reply other threads:[~2012-11-19 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 7:44 [PATCH v2] ARM: tegra: ventana: enable internal display Alexandre Courbot
[not found] ` <1353051891-26725-1-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-11-16 7:51 ` Alex Courbot
2012-11-16 17:07 ` Stephen Warren
[not found] ` <50A672DF.1070003-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-11-19 9:35 ` Alex Courbot
2012-11-19 2:55 ` Mark Zhang [this message]
2012-11-16 20:49 ` Thierry Reding
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=50A99FAE.3080207@nvidia.com \
--to=markz-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@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.