From: Thierry Reding <thierry.reding@avionic-design.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: set the AVI VIC of the HDMI mode
Date: Thu, 22 Nov 2012 07:50:55 +0100 [thread overview]
Message-ID: <20121122065055.GC22143@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <CAKMK7uE_SBdj4U-D9mEbA90bqewkcyBk0R0VXExpsmYc4=WnVw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1248 bytes --]
On Wed, Nov 21, 2012 at 05:09:31PM +0100, Daniel Vetter wrote:
> On Wed, Nov 21, 2012 at 5:08 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Wed, Nov 21, 2012 at 4:47 PM, Thierry Reding
> > <thierry.reding@avionic-design.de> wrote:
> >> Oh great, so I copied that table for nothing. Thanks for Cc'ing, I can
> >> reuse that in the HDMI infoframe series.
> >
> > Wrt the infoframe series, I think it'd be awesome if you could convert
> > i915 and radeon (iirc the existing drivers with the "best" avi
> > infoframe support) over to the new code. This gives some nice
> > validation, both by testing on actual hw and that the interface is
> > sane, since it'll be used by 2-3 different drivers then.
> >
> > I think the best way is to pick the infoframe implementation you best
> > like from one of these, move it into the helper, then improve it until
> > you're happy. And then convert over 1-2 other drivers. At least that's
> > been my approach for the recent dp helper refactoring.
>
> And if you could use that opportunity to integrate the kerneldoc for
> edid/eld and the new infoframe code into the drm docbook, that would
> be rather awesome ;-)
I suck at documentation =), but I'll see what I can do.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-11-22 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 15:39 [PATCH] drm/i915: set the AVI VIC of the HDMI mode Paulo Zanoni
2012-11-21 15:47 ` Thierry Reding
2012-11-21 16:08 ` Daniel Vetter
2012-11-21 16:09 ` Daniel Vetter
2012-11-22 6:50 ` Thierry Reding [this message]
2012-11-22 6:48 ` Thierry Reding
2012-11-22 8:00 ` Rafał Miłecki
2012-11-22 8:05 ` Thierry Reding
2012-11-22 6:46 ` Thierry Reding
2012-11-23 13:46 ` Paulo Zanoni
2012-11-23 13:50 ` 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=20121122065055.GC22143@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.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 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.