Hi Harish,
Thanks for the correction and suggestions.
Please find my responses inline:
On 3/18/2019 9:40 PM, Harish Krupo wrote:
Hi Ankit,
Nautiyal, Ankit K writes:
From: Ankit Nautiyal
This patch adds HDR-metadata support in the color-management-protocol.
It enables a client to:
- know
From: Ankit Nautiyal
This patch adds HDR-metadata support in the color-management-protocol.
It enables a client to:
- know if an output is HDR capable.
- set HDR-metadata values, received from an HDR content, for a surface.
The HDR-metadata values : MAX_CLL, MAX_FALL, MAX_LUMINANCE,
MIN LUMINANC
Hi Pekka,
Thanks for the comments and suggestions.
Please my responses inline:
On 2/28/2019 7:51 PM, Pekka Paalanen wrote:
On Wed, 27 Feb 2019 10:27:16 +0530
"Nautiyal, Ankit K" wrote:
From: Ankit Nautiyal
This protcol enables a client to send the hdr meta-data:
MAX-CLL, MAX
Hi,
On 2/27/2019 2:28 PM, Erwin Burema wrote:
Hi,
On Wed, 27 Feb 2019 at 05:47, Nautiyal, Ankit K
wrote:
From: Ankit Nautiyal
This protcol enables a client to send the hdr meta-data:
MAX-CLL, MAX-FALL, Max Luminance and Min Luminance as defined by
SMPTE ST.2086.
The clients get these
From: Ankit Nautiyal
This protcol enables a client to send the hdr meta-data:
MAX-CLL, MAX-FALL, Max Luminance and Min Luminance as defined by
SMPTE ST.2086.
The clients get these values for an HDR video, encoded for a video
stream/file. MAX-CLL (Maximum Content Light Level) tells the brightest
p
On 2/14/2019 1:27 PM, Sebastian Wick wrote:
On 2019-02-14 08:13, Nautiyal, Ankit K via wayland-devel wrote:
Hi Sebastian,
I am trying to extend Ole's color management protocol [1] to enable a
client to pass HDR meta data.
Added the modified protocol as weston protocol for the time bein
Hi Sebastian,
I am trying to extend Ole's color management protocol [1] to enable a
client to pass HDR meta data.
Added the modified protocol as weston protocol for the time being. [2]
You have mention that the proposed protocol, ignores the HDR
calibration/profiling, so do you suggest there
On 2/1/2019 6:15 PM, Pekka Paalanen wrote:
On Mon, 28 Jan 2019 22:39:39 +0530
"Nautiyal, Ankit K" wrote:
Hi Simon Ser,
Thanks for your comments.
I am also not sure about whether the protocol belongs here or not, and
that's why I had first proposed the same in weston,
Thanks for the clarification Ole.
Regards,
Ankit
On 1/31/2019 2:22 PM, Niels Ole Salscheider wrote:
Hi Ankit,
please find my answers below.
Am Donnerstag, 31. Januar 2019, 06:54:03 CET schrieb Nautiyal, Ankit K:
Hi Ole,
I was going through the protocol you had proposed, and have some
Hi Ole,
I was going through the protocol you had proposed, and have some silly
questions, please pardon my ignorance.
From where can the client-applications get the ICC profile files? Does
the client application manufacture it for a given color space and a
standard template?
Or the composi
Hi Simon Ser,
Thanks for your comments.
I am also not sure about whether the protocol belongs here or not, and
that's why I had first proposed the same in weston, along with the
implementation and the client application -
Merge request:
_https://gitlab.freedesktop.org/wayland/weston/merge_reque
From: Ankit Nautiyal
This patch adds the protocol for providing content-protection to a
client application. The content-protection here refers to the 'on the
wire protection' e.g. HDCP1.4 HDCP2.2.
The client application can request for the content-protection,
specifying the type of the content: T
Hi Scott,
As this was under discussion in last patchset, summarizing it here again:
HDCP2.2 spec leaves the content-type classification to the
content-provider (client).
The same had been discussed earlier in #wayland, and the mailing list:
https://lists.freedesktop.org/archives/wayland-deve
On 11/22/2018 1:01 PM, C, Ramalingam wrote:
Hi Scott,
I am working on enabling the HDCP1.4 and 2.2 in kernel and Weston from
Intel. Would like to share some points here.
On 11/21/2018 7:35 AM, Scott Anderson wrote:
Hi,
As far as I understand, the different types and versions of
protectio
On 11/19/2018 12:51 PM, Simon Ser wrote:
On Monday, November 19, 2018 4:21 AM, wrote:
From: Scott Anderson
This protocol allows a client to ask the compositor to only allow it to
be displayed on a "secure" output (e.g. HDCP).
This is based on a chromium protocol of the same name [1].
This
From: Ankit Nautiyal
The weston.ini.man describes the mode-formats that a user can specify
for selecting a video mode. The DRM specific examples are already
provided in weston-drm.man, so this inofrmation is redundant and can
be removed.
This patch removes the DRM specific mode option details fr
On 7/6/2018 2:44 PM, Pekka Paalanen wrote:
On Tue, 19 Mar 2097 00:24:56 +0530
"Nautiyal, Ankit K" wrote:
From: Ankit Nautiyal
This patch adds information about the new resolution-format that can
be specified by a user in weston.ini to select a CEA mode. CEA defines
timing of a
Hi Pekka,
Sorry for the goof up :) I would certainly take care of this next time.
Thanks a lot for all the considerations.
Regards,
Ankit
On 7/6/2018 2:44 PM, Pekka Paalanen wrote:
On Tue, 19 Mar 2097 00:24:55 +0530
"Nautiyal, Ankit K" wrote:
From: Ankit Nautiyal
This pa
From: Ankit Nautiyal
This patch adds information about the new resolution-format that can
be specified by a user in weston.ini to select a CEA mode. CEA defines
timing of a video mode, which is considered as a standard for
HDMI certification and compliance testing. It defines each and every
param
From: Ankit Nautiyal
The flag bits 19-22 of the connector modes, provide the aspect-ratio
information. This information can be stored in flags bits of the
weston mode structure, so that it can used for setting a mode with a
particular aspect-ratio.
Currently, DRM layer supports aspect-ratio with
From: Ankit Nautiyal
This patch series adds support for parsing aspect-ratio information
for a connector vidoe mode, provided by the DRM layer.
The aspect ratio is stored in the flags bit of the connector modes,
which can be used to distinguish between CEA modes, that have the
aspect-ratio specif
pect ratio information.
Please find my comment inline.
Regards
Shashank
On 6/28/2018 7:09 PM, Pekka Paalanen wrote:
On Sun, 20 May 2018 18:33:01 +0530
"Nautiyal, Ankit K" wrote:
From: Ankit Nautiyal
The flag bits 19-22 of the connector modes, provide the aspect-ratio
information. Thi
responses inline for the remaining comments:
On 6/28/2018 7:09 PM, Pekka Paalanen wrote:
On Sun, 20 May 2018 18:33:01 +0530
"Nautiyal, Ankit K" wrote:
From: Ankit Nautiyal
The flag bits 19-22 of the connector modes, provide the aspect-ratio
information. This information can be store
Hi All,
I am working on wayland content-protection protocol extension, to enable
content-protection (HDCP1.4, HDCP2.2) in wayland.
DRM layer already has support for HDCP1.4 and patches for HDCP2.2 are in review
: https://patchwork.freedesktop.org/series/39596/
As per the IRC discussion on #wayl
From: Ankit Nautiyal
The flag bits 19-22 of the connector modes, provide the aspect-ratio
information. This information can be stored in flags bits of the
weston mode structure, so that it can used for setting a mode with a
particular aspect-ratio.
Currently, DRM layer supports aspect-ratio with
Hi Pekka,
Many thanks for the review comments, and suggestions. I will address
these in the next patch.
Please find my clarifications/comments inline below.
On 11/3/2017 3:52 PM, Pekka Paalanen wrote:
(I fixed the subject line to contain v3.)
On Mon, 16 Oct 2017 20:25:23 +0530
Nautiyal Ank
tags and merge from kernel side, followed by merge in weston.
Thanks,
Ankit
On 10/5/2017 6:41 PM, Pekka Paalanen wrote:
On Thu, 5 Oct 2017 16:28:37 +0530
"Nautiyal, Ankit K" wrote:
Hi Pekka,
Thanks a lot for your review comments and the suggestions, and pointing
out the things I had
Hi Pekka,
Thanks a lot for your review comments and the suggestions, and pointing
out the things I had missed.
I agree to most of the changes, please find my response inline.
I will shortly send the next version of the patch in a couple of days.
On 10/4/2017 2:13 PM, Pekka Paalanen wrote:
O
28 matches
Mail list logo
