From: Alex Courbot <acourbot@nvidia.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Dave Airlie <airlied@redhat.com>, Rob Clark <rob@ti.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] NVIDIA Tegra DRM driver
Date: Fri, 16 Nov 2012 13:34:34 +0900 [thread overview]
Message-ID: <8931573.Za4gdCbDYv@percival> (raw)
In-Reply-To: <1480191.1noyT4vz0N@percival>
On Friday 16 November 2012 11:36:36 Alex Courbot wrote:
> On Friday 16 November 2012 05:28:21 Thierry Reding wrote:
> > This third version of the patch series cleans up some minor issues that
> > were found in the previous versions, such as deferred probe not working
> > properly and the display remaining enabled after the driver is removed.
> >
> > I've also put the two patches in this series into the tegra/drm/for-3.8
> > branch of my repository on gitorious[0].
>
> Pulled from your branch and tried to test on my Ventana, but for some reason
> nothing ever gets displayed. The only DRM-related message I ever get in my
> log is
>
> [ 0.820483] [drm] Initialized drm 1.1.0 20060810
>
> Things were working perfectly with v2 - has something changed with e.g. the
> DT bindings?
Argh, the patches that add host1x nodes into tegra20.dtsi were not into your
for-3.8 branch. Things are fine now, therefore this series is
Tested-and-acked-by: Alexandre Courbot <acourbot@nvidia.com>
Thanks,
Alex.
next prev parent reply other threads:[~2012-11-16 4:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 21:28 Thierry Reding
2012-11-15 21:28 ` [PATCH v3 1/2] drm: Add NVIDIA Tegra20 support Thierry Reding
2012-11-15 21:28 ` [PATCH v3 2/2] drm: tegra: Add HDMI support Thierry Reding
2012-11-15 22:20 ` [PATCH v3 0/2] NVIDIA Tegra DRM driver Stephen Warren
2012-11-16 3:36 ` Alex Courbot
2012-11-16 4:34 ` Alex Courbot [this message]
2012-11-16 3:57 ` Mark Zhang
2012-11-16 4:00 ` Mark Zhang
2012-11-16 7:38 ` Terje Bergström
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=8931573.Za4gdCbDYv@percival \
--to=acourbot@nvidia.com \
--cc=airlied@redhat.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob@ti.com \
--cc=thierry.reding@avionic-design.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome