Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Eugeni Dodonov <eugeni@dodonov.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: fixup infoframe support for sdvo
Date: Sun, 20 May 2012 17:13:28 +0200	[thread overview]
Message-ID: <20120520151327.GA5145@phenom.ffwll.local> (raw)
In-Reply-To: <CAC7Lmnv4=xWMQaQZBwhhALU6GBRU0+VEWxMPSmYO6VaSWtztDA@mail.gmail.com>

On Sun, May 20, 2012 at 11:17:36AM -0300, Eugeni Dodonov wrote:
> On Sat, May 12, 2012 at 3:22 PM, Daniel Vetter <daniel.vetter@ffwll.ch>wrote:
> 
> > At least the worst offenders:
> > - SDVO specifies that the encoder should compute the ecc. Testing also
> >  shows that we must not send the ecc field, so copy the dip_infoframe
> >  struct to a temporay place and avoid the ecc field. This way the avi
> >  infoframe is exactly 17 bytes long, which agrees with what the spec
> >  mandates as a minimal storage capacity (with the ecc field it would
> >  be 18 bytes).
> > - Only 17 when sending the avi infoframe. The SDVO spec explicitly
> >  says that sending more data than what the device announces results
> >  in undefined behaviour.
> > - Add __attribute__((packed)) to the avi and spd infoframes, for
> >  otherwise they're wrongly aligned. Noticed because the avi infoframe
> >  ended up being 18 bytes large instead of 17. We haven't noticed this
> >  yet because we don't use the uint16_t fields yet (which are the only
> >  ones that would be wrongly aligned).
> >
> > This regression has been introduce by
> >
> > 3c17fe4b8f40a112a85758a9ab2aebf772bdd647 is the first bad commit
> > commit 3c17fe4b8f40a112a85758a9ab2aebf772bdd647
> > Author: David Härdeman <david@hardeman.nu>
> > Date:   Fri Sep 24 21:44:32 2010 +0200
> >
> >    i915: enable AVI infoframe for intel_hdmi.c [v4]
> >
> > Patch tested on my g33 with a sdvo hdmi adaptor.
> >
> > Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=25732
> > Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> >
> 
> This looks correct, and the math matches the 17 bytes we need. So for the
> patch itself:
> Reviewed-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
Queued for -next, thanks for the review.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

      reply	other threads:[~2012-05-20 15:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12 18:22 [PATCH] drm/i915: fixup infoframe support for sdvo Daniel Vetter
2012-05-19 21:29 ` Daniel Vetter
2012-05-20 14:17 ` Eugeni Dodonov
2012-05-20 15:13   ` Daniel Vetter [this message]

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=20120520151327.GA5145@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=eugeni@dodonov.net \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox