From: Thierry Reding <thierry.reding@avionic-design.de>
To: Mark Zhang <markz@nvidia.com>
Cc: airlied@redhat.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] drm: Add NVIDIA Tegra30 support
Date: Fri, 16 Nov 2012 07:43:31 +0100 [thread overview]
Message-ID: <20121116064331.GA21671@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <1353041889-3114-1-git-send-email-markz@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
On Fri, Nov 16, 2012 at 12:58:09PM +0800, Mark Zhang wrote:
> This patch is based on Thierry's drm patch for Tegra20:
> - [PATCH v2 0/6] Device tree updates for host1x support
> - [PATCH v3 0/2] NVIDIA Tegra DRM driver
>
> It adds the support for NVIDIA Tegra30.
>
> Signed-off-by: Mark Zhang <markz@nvidia.com>
Hi Mark,
I already carry a similar patch in my tegra/next branch and was going to
post that once I get word back that tegra-drm actually works on Tegra30.
You do have the hardware available, right? Did you test this patch on
top of the latest (v3) tegra-drm patches and arch/arm/mach-tegra (v2)
patches I sent a few hours ago?
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-16 6:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 4:58 [PATCH] drm: Add NVIDIA Tegra30 support Mark Zhang
2012-11-16 6:43 ` Thierry Reding [this message]
2012-11-16 6:48 ` Mark Zhang
2012-11-16 7:11 ` Thierry Reding
2012-11-16 7:15 ` Mark Zhang
2012-11-16 16:29 ` Stephen Warren
2012-11-19 6:18 ` Mark Zhang
2012-11-19 6:45 ` Thierry Reding
2012-11-19 7:17 ` Mark Zhang
2012-11-16 16:43 ` Stephen Warren
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=20121116064331.GA21671@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=markz@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).