From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Pavel Machek <pavel@ucw.cz>, Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/6] drm: Add Content Protection property
Date: Thu, 7 Dec 2017 14:30:52 +0000 [thread overview]
Message-ID: <20171207143052.533e1e94@alans-desktop> (raw)
In-Reply-To: <20171205104538.b4fxdjad3c46koas@phenom.ffwll.local>
> If you want to actually lock down a machine to implement content
> protection, then you need secure boot without unlockable boot-loader and a
> pile more bits in userspace.
So let me take my Intel hat off for a moment.
The upstream policy has always been that we don't merge things which
don't have an open usable user space. Is the HDCP encryption feature
useful on its own ? What do users get from it ?
If this is just an enabler for a lump of binary stuff in ChromeOS then I
don't think it belongs, if it is useful standalone then it seems it does
belong ?
Alan
next prev parent reply other threads:[~2017-12-07 14:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171130030907.26848-1-seanpaul@chromium.org>
2017-11-30 3:08 ` [RFC PATCH 1/6] drm: Add Content Protection property Sean Paul
2017-12-05 10:28 ` Pavel Machek
2017-12-05 10:45 ` Daniel Vetter
2017-12-05 17:34 ` Pavel Machek
2017-12-05 17:53 ` Alex Deucher
2017-12-05 18:01 ` Pavel Machek
2017-12-07 14:32 ` Alan Cox
2017-12-05 19:03 ` Sean Paul
2017-12-05 20:14 ` Daniel Stone
2017-12-07 14:30 ` Alan Cox [this message]
2017-12-08 8:55 ` Daniel Vetter
2017-11-30 3:08 ` [RFC PATCH 2/6] drm: Add some HDCP related #defines Sean Paul
2017-11-30 3:08 ` [RFC PATCH 3/6] drm/i915: Add HDCP framework + base implementation Sean Paul
2017-11-30 9:12 ` [Intel-gfx] " Chris Wilson
2017-12-01 7:23 ` Ramalingam C
2017-12-01 7:36 ` [Intel-gfx] " Daniel Vetter
2017-12-01 8:36 ` Ramalingam C
2017-12-01 14:13 ` Sean Paul
2017-12-01 14:16 ` Sean Paul
2017-11-30 3:08 ` [RFC PATCH 4/6] drm/i915: Add function to output Aksv over GMBUS Sean Paul
2017-11-30 3:09 ` [RFC PATCH 5/6] drm/i915: Implement HDCP for HDMI Sean Paul
2017-12-01 7:31 ` Ramalingam C
2017-11-30 3:09 ` [RFC PATCH 6/6] drm/i915: Implement HDCP for DisplayPort Sean Paul
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=20171207143052.533e1e94@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=pavel@ucw.cz \
--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