linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jun Nie <niej0001@gmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	Tomasz Stanislawski <t.stanislaws@samsung.com>,
	linux-fbdev@vger.kernel.org,
	Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
	Pawel Osciak <pawel@osciak.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Marcus Lorentzon <marcus.lorentzon@linaro.org>,
	dri-devel@lists.freedesktop.org,
	Alexander Deucher <alexander.deucher@amd.com>,
	Rob Clark <rob@ti.com>,
	linux-media@vger.kernel.org,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: Kernel Display and Video API Consolidation mini-summit at ELC 2012 - Notes
Date: Thu, 17 May 2012 02:46:37 +0000	[thread overview]
Message-ID: <CAGA24M+OEwi-ayBrXcMPg5PzndRF4mSr2dOOQAxhDCu6ShZLjQ@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1202201633100.2836@axis700.grange>

    Is there any discussion on HDCP on the summit? It is tightly
coupled with HDMI and DVI and should be managed together with the
transmitter. But there is not code to handle HDCP in DRM/FB/V4L in
latest kernel. Any thoughts on HDCP? Or you guys think there is risk
to support it in kernel? Thanks for your comments!

Jun

  parent reply	other threads:[~2012-05-17  2:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201201171126.42675.laurent.pinchart@ideasonboard.com>
     [not found] ` <1654816.MX2JJ87BEo@avalon>
2012-02-16 23:25   ` Kernel Display and Video API Consolidation mini-summit at ELC 2012 - Notes Laurent Pinchart
2012-02-17  9:55     ` Daniel Vetter
2012-02-17 18:46       ` Laurent Pinchart
2012-02-22 16:03         ` James Simmons
2012-02-22 16:24           ` Daniel Vetter
2012-02-22 16:28             ` Rob Clark
2012-02-23  7:34               ` Michel Dänzer
2012-02-22 16:36             ` Chris Wilson
2012-02-22 16:40               ` Clark, Rob
2012-02-22 17:26                 ` James Simmons
2012-02-23  0:15                 ` Alan Cox
2012-02-22 17:00           ` Adam Jackson
2012-02-20 16:09       ` Guennadi Liakhovetski
2012-02-20 16:19         ` David Airlie
2012-05-17  2:46         ` Jun Nie [this message]
2012-05-17  7:53           ` Hans Verkuil
2012-02-17 11:19     ` Semwal, Sumit
2012-02-17 18:49       ` Laurent Pinchart
2012-02-17 19:42     ` Adam Jackson
2012-02-18 17:53       ` Clark, Rob
2012-02-18  0:56     ` Keith Packard
2012-02-20 16:40     ` Guennadi Liakhovetski
2012-03-02 14:23     ` Heiko Stübner

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=CAGA24M+OEwi-ayBrXcMPg5PzndRF4mSr2dOOQAxhDCu6ShZLjQ@mail.gmail.com \
    --to=niej0001@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=magnus.damm@gmail.com \
    --cc=marcus.lorentzon@linaro.org \
    --cc=pawel@osciak.com \
    --cc=rob@ti.com \
    --cc=sakari.ailus@maxwell.research.nokia.com \
    --cc=t.stanislaws@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).