jo...@kwiboo.se; Sean Paul
>> >; Sharma, Shashank
>> >; Syrjala, Ville
>> >
>> >Subject: Re: [Intel-gfx] [v11 00/12] Add HDR Metadata Parsing and
>> >handling in DRM layer
>> >
>> >On Wed, May 29, 2019 at 3:59 PM Shankar, Uma
>wrote:
&g
rg>; Daniele Castagna ;
> >jo...@kwiboo.se; Sean Paul ; Sharma, Shashank
> >; Syrjala, Ville
> >Subject: Re: [Intel-gfx] [v11 00/12] Add HDR Metadata Parsing and handling
> >in DRM
> >layer
> >
> >On Wed, May 29, 2019 at 3:59 PM Shankar, Uma wrote
le
>Subject: Re: [Intel-gfx] [v11 00/12] Add HDR Metadata Parsing and handling in
>DRM
>layer
>
>On Wed, May 29, 2019 at 3:59 PM Shankar, Uma wrote:
>>
>>
>>
>> >-Original Message-
>> >From: Daniel Vetter [mailto:dan...@ffwll.ch]
>&g
rg>; Daniele Castagna ;
> >jo...@kwiboo.se; Sean Paul ; Sharma, Shashank
> >; Syrjala, Ville
> >Subject: Re: [Intel-gfx] [v11 00/12] Add HDR Metadata Parsing and handling
> >in DRM
> >layer
> >
> >When building the docs with make htmldocs:
>
le
>Subject: Re: [Intel-gfx] [v11 00/12] Add HDR Metadata Parsing and handling in
>DRM
>layer
>
>When building the docs with make htmldocs:
>
>./include/drm/drm_mode_config.h:841: warning: Incorrect use of
>kernel-doc format: * hdr_output_metadata_property: C
When building the docs with make htmldocs:
./include/drm/drm_mode_config.h:841: warning: Incorrect use of
kernel-doc format: * hdr_output_metadata_property: Connector
property containing hdr
./include/drm/drm_mode_config.h:918: warning: Function parameter or
member 'hdr_output_metadata_pr
l.l.veli...@gmail.com;
>brian.star...@arm.com; dcasta...@chromium.org; seanp...@chromium.org;
>Roper, Matthew D ; jo...@kwiboo.se
>Subject: Re: [v11 00/12] Add HDR Metadata Parsing and handling in DRM layer
>
>Op 22-05-2019 om 22:45 schreef Ville Syrjälä:
>> On Thu, May 16, 2019 at 07:
Op 22-05-2019 om 22:45 schreef Ville Syrjälä:
> On Thu, May 16, 2019 at 07:40:05PM +0530, Uma Shankar wrote:
>> This patch series enables HDR support in drm. It basically defines
>> HDR metadata structures, property to pass content (after blending)
>> metadata from user space compositors to driver.
On Thu, May 23, 2019 at 11:09:41AM +0300, Jani Nikula wrote:
> On Wed, 22 May 2019, Ville Syrjälä wrote:
> > Pushed the core/etc. bits to drm-misc-next so that other drivers
> > can base their work on that. We'll need a backmerge to get the
> > i915 stuff in via dinq.
>
> To avoid any confusion,
On Wed, 22 May 2019, Ville Syrjälä wrote:
> Pushed the core/etc. bits to drm-misc-next so that other drivers
> can base their work on that. We'll need a backmerge to get the
> i915 stuff in via dinq.
To avoid any confusion, drm-misc-next needs to get merged to drm-next,
which then needs to be bac
On Thu, May 16, 2019 at 07:40:05PM +0530, Uma Shankar wrote:
> This patch series enables HDR support in drm. It basically defines
> HDR metadata structures, property to pass content (after blending)
> metadata from user space compositors to driver.
>
> Dynamic Range and Mastering infoframe creatio
This patch series enables HDR support in drm. It basically defines
HDR metadata structures, property to pass content (after blending)
metadata from user space compositors to driver.
Dynamic Range and Mastering infoframe creation and sending.
ToDo:
1. We need to get the color framework in place fo
12 matches
Mail list logo
