From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Thierry Reding <thierry.reding@gmail.com>,
Hans Verkuil <hansverk@cisco.com>
Subject: Re: [PATCH 1/2] drivers/video/hdmi: allow for larger-than-needed vendor IF
Date: Tue, 21 Nov 2017 17:27:26 +0200 [thread overview]
Message-ID: <20171121152726.GE10981@intel.com> (raw)
In-Reply-To: <dea1aedf-80f8-ad6d-2560-eb7a0b1936a3@xs4all.nl>
On Mon, Nov 20, 2017 at 04:02:14PM +0100, Hans Verkuil wrote:
> On 11/20/2017 03:51 PM, Ville Syrjälä wrote:
> > On Mon, Nov 20, 2017 at 02:41:28PM +0100, Hans Verkuil wrote:
> >> From: Hans Verkuil <hansverk@cisco.com>
> >>
> >> Some devices (Windows Intel driver!) send a Vendor InfoFrame that
> >> uses a payload length of 0x1b instead of the length of 5 or 6
> >> that the unpack code expects. The InfoFrame is padded with 0 by
> >> the source.
> >
> > So it doesn't put any 3D_Metadata stuff in there? We don't see to
> > have code to parse/generate any of that.
>
> I can't remember if it puts any 3D stuff in there. Let me know if you
> want me to check this later this week.
Would be nice to know.
I guess we should really add code to parse/generate that stuff too,
otherwise we're going to be lying when we unpack an infoframe with that
stuff present.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2017-11-21 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 13:41 [PATCH 0/2] video/hdmi: two fixes Hans Verkuil
2017-11-20 13:41 ` Hans Verkuil
2017-11-20 13:41 ` [PATCH 1/2] drivers/video/hdmi: allow for larger-than-needed vendor IF Hans Verkuil
2017-11-20 14:51 ` Ville Syrjälä
2017-11-20 14:51 ` Ville Syrjälä
2017-11-20 15:02 ` Hans Verkuil
2017-11-21 15:27 ` Ville Syrjälä [this message]
2017-11-23 11:57 ` Hans Verkuil
2017-11-20 13:41 ` [PATCH 2/2] hdmi: audio infoframe log: corrected channel count Hans Verkuil
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=20171121152726.GE10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansverk@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=thierry.reding@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 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.