On Thu, Dec 07, 2017 at 02:30:52PM +0000, Alan Cox wrote: > > 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 ? The cros side is ofc all open source. dri-devel is extremely strict with not taking anything that doesn't fullfil this requirement, probably more strict than anyone else. Sean has the link in the cover letter of his patch series. For more context, here's our documented expectations about the userspace side of any uapi addition to drm: https://dri.freedesktop.org/docs/drm/gpu/drm-uapi.html#open-source-userspace-requirements Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
