mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@avionic-design.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Christian König" <deathsimple@vodafone.de>,
	linux-tegra@vger.kernel.org, "Dave Airlie" <airlied@redhat.com>,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm: tegra: Add HDMI support
Date: Fri, 9 Nov 2012 21:20:23 +0100	[thread overview]
Message-ID: <20121109202023.GA8615@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <CACna6rxOBENLVC8mgJdsSdAZdWranMiivSgq_8DzeTo0hzzWqg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

On Fri, Nov 09, 2012 at 05:04:09PM +0100, Rafał Miłecki wrote:
> 2012/11/9 Christian König <deathsimple@vodafone.de>:
> > On 09.11.2012 16:45, Rafał Miłecki wrote:
> >> I was told it won't work on different endian devices. See
> >> [RFC][PATCH] drm/radeon/hdmi: define struct for AVI infoframe
> >> http://lists.freedesktop.org/archives/dri-devel/2012-May/022544.html
> >
> >
> > Yeah, that's indeed true. And honestly adding just another implementation of
> > the HDMI info frames sounds like somebody should finally sit down and
> > implement it in a common drm_hdmi.c
> 
> Agree.

Any volunteers? If nobody else steps up I'm willing to put some work
into this. I'm a bit reluctant to do this right away since time is
already very short before the 3.8 merge window. If I promise to look at
this once the Tegra DRM driver is in, would people be willing to let it
slip for now?

I know this is not much of an argument and I'm all in favour of a
generic implementation, but I don't think endianess will be an issue in
the near future on Tegra. I don't believe there are any plans to make it
support big endian.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-11-09 20:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 13:59 [PATCH 0/2] NVIDIA Tegra DRM driver Thierry Reding
2012-11-09 13:59 ` [PATCH 1/2] drm: Add NVIDIA Tegra20 support Thierry Reding
2012-11-09 15:18   ` Rob Clark
2012-11-09 16:00     ` Thierry Reding
2012-11-09 16:26       ` Rob Clark
2012-11-09 21:03         ` Thierry Reding
2012-11-10 18:04           ` Terje Bergström
2012-11-09 22:27   ` Stephen Warren
2012-11-10  0:09   ` Stephen Warren
2012-11-10  9:11     ` Thierry Reding
2012-11-13  8:00   ` Terje Bergström
2012-11-13  8:03     ` Thierry Reding
2012-11-13  8:16       ` Terje Bergström
2012-11-09 13:59 ` [PATCH 2/2] drm: tegra: Add HDMI support Thierry Reding
2012-11-09 15:45   ` Rafał Miłecki
2012-11-09 16:00     ` Christian König
2012-11-09 16:04       ` Rafał Miłecki
2012-11-09 20:20         ` Thierry Reding [this message]
2012-11-10 21:01       ` Thierry Reding
2012-11-10 21:11         ` Thierry Reding
2012-11-11 14:46         ` Daniel Vetter
2012-11-12  7:24           ` Thierry Reding
2012-11-12  9:43             ` Daniel Vetter

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=20121109202023.GA8615@avionic-0098.mockup.avionic-design.de \
    --to=thierry.reding@avionic-design.de \
    --cc=airlied@redhat.com \
    --cc=deathsimple@vodafone.de \
    --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=zajec5@gmail.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

Powered by JetHome