From: Ramalingam C <ramalingam.c@intel.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v3 3/9] drm: Add Content Protection property
Date: Thu, 7 Dec 2017 10:04:48 +0530 [thread overview]
Message-ID: <f85eaf61-881c-8cfa-29e1-eee75357af5e@intel.com> (raw)
In-Reply-To: <CAOw6vbLSz6TemejVc=Ou-qS+1+BjMrPFEqX3XvpGnd83SY=bHw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 730 bytes --]
On Wednesday 06 December 2017 09:56 PM, Sean Paul wrote:
>>> I'd rather keep the property as-is and expose an HDCP version property
>>> alongside it (or perhaps something more elaborate that includes bksv and the
>>> downstream bksvs). The reason I prefer that is it will also cover the 1.2 vs 1.4
>>> difference that is a more immediate need.
>> HDCP specification wants to differentiate 2.2 vs <2.2 as 2.2 is not a backward compatible.
>> Why do we need to differentiate 1.2 and 1.4? Any use case?
>>
> Someone on the Chrome side asked me to surface the version, apparently
> they care about 1.2 vs 1.4.
>
Sean, if you can get the reason for differentiating v1.2 and v1.4 at
chrome, it will be educative info. - Thanks
-Ram
[-- Attachment #1.2: Type: text/html, Size: 1372 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-12-07 4:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 5:14 [PATCH v3 0/9] drm/i915: Implement HDCP Sean Paul
2017-12-05 5:15 ` [PATCH v3 1/9] drm: Fix link-status kerneldoc line lengths Sean Paul
2017-12-05 5:15 ` [PATCH v3 2/9] drm/i915: Add more control to wait_for routines Sean Paul
2017-12-05 17:13 ` Daniel Vetter
2017-12-05 23:09 ` [Intel-gfx] " Chris Wilson
2017-12-05 5:15 ` [PATCH v3 3/9] drm: Add Content Protection property Sean Paul
2017-12-05 8:07 ` Hans Verkuil
2017-12-05 14:04 ` Ramalingam C
2017-12-05 14:36 ` Sean Paul
2017-12-05 16:10 ` Hans Verkuil
2017-12-05 17:11 ` C, Ramalingam
2017-12-06 16:26 ` Sean Paul
2017-12-07 4:34 ` Ramalingam C [this message]
2017-12-05 15:27 ` Daniel Vetter
2017-12-05 15:34 ` Daniel Vetter
2017-12-05 15:40 ` [Intel-gfx] " Chris Wilson
2017-12-05 5:15 ` [PATCH v3 4/9] drm: Add some HDCP related #defines Sean Paul
2017-12-05 23:12 ` [Intel-gfx] " Chris Wilson
2017-12-06 15:01 ` Alex Deucher
2017-12-05 5:15 ` [PATCH v3 5/9] drm/i915: Add HDCP framework + base implementation Sean Paul
2017-12-05 9:06 ` Ramalingam C
2017-12-05 17:00 ` Daniel Vetter
2017-12-05 5:15 ` [PATCH v3 6/9] drm/i915: Make use of indexed write GMBUS feature Sean Paul
2017-12-05 17:01 ` [Intel-gfx] " Daniel Vetter
2017-12-05 17:33 ` Ville Syrjälä
2017-12-05 5:15 ` [PATCH v3 7/9] drm/i915: Add function to output Aksv over GMBUS Sean Paul
2017-12-05 17:02 ` Daniel Vetter
2017-12-05 5:15 ` [PATCH v3 8/9] drm/i915: Implement HDCP for HDMI Sean Paul
2017-12-05 17:06 ` Daniel Vetter
2017-12-05 5:15 ` [PATCH v3 9/9] drm/i915: Implement HDCP for DisplayPort Sean Paul
2017-12-05 14:30 ` Ramalingam C
2017-12-05 17:12 ` 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=f85eaf61-881c-8cfa-29e1-eee75357af5e@intel.com \
--to=ramalingam.c@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hverkuil@xs4all.nl \
--cc=seanpaul@chromium.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