GitLab

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

These three aren't acronyms.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Gitlab Markdown will allow us to use math if necessary.

I couldn't find a better way to set up a definition list, but at least
the index lists them now.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

v3:
- Add mention that AMD display pipeline color-processing block's impact
  on power are negligible in comparison to memory bandwidth and GPU
  power (Sebastian)

v2:
- Add link to README.md (Pekka)
- Make it clear that compositors don't currently do color space conversions.
  Applications will perform their own color space conversion when required,
  such as when playing back HDR videos. (Sebastian)
- Avoid some generalizations about color-managed compositor behavior while
  highlighting that a color-managed compositor will likely have a larger GPU
  and memory bandwidth usage (Pekka)
- Clarify the importance of 3D LUT for high-quality tone-, and gamut-mapping
  (Sebastian)
- Soften language of power-saving implications of RGB 10bpc scanout instead of
  FP16 scanout (Harry)
- Add blurb on de-linearizing content post-blending when needed (Sebastian)
- Use unambiguous language to refer to the display controller, instead of the
  actual display (Pekka)
- Spell out PWL, ...

Signed-off-by: François-Xavier Thomas <fx.thomas@gmail.com>

Add a story on what one would need to know to process and display a
pixel.

This is an introduction to people who are already familiar with computer
graphics in general, images in memory, and maybe window systems, but
never really thought what the values in a pixel actually mean or what
they are doing wrong with them.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Pekka Paalanen authored Oct 20, 2021 and Pekka Paalanen committed Nov 10, 2021

For images, it's nice to have also the sources in case someone needs to
edit the image later.

For math, these hints should help typesetting math with less pain.

Thanks to @mstoeckl

 for the KaTeX demo link.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

The only thing left in color.rst are the misc notes. Rename the file
accordingly.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

No changes to content. This finishes the color.rst splitting.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

That chapter considers HDR from the Wayland and window system
perspective, and it is quite WIP.

No changes to the content.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Tables of well-known EOTFs, chromaticities and whitepoints moved into a
file of their own, without changes.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

This continues splitting up color.rst.

No changes to the content.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

color.rst is a little long already, and we wish to get more
documentation that may be hard to integrate in color.rst (making it even
longer, not quite fitting with the topic, or needing features like math
markup). Therefore start splitting it up and collect a ToC straight in
the README.

This patch moves the design goals as-is into a new file. The design
goals are considered mature and unlikely to change, unlike some other
parts.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

None of these copyrights apply to any files in this repository.

Copyright lists in FOSS projects tend to be always out-of-date when
compared to what law says about when copyright forms. Law also requires
interpretation case by case whether something is copyrightable or not.
Hence, if someone bothered to add a copyright line then they surely
expect to hold some copyrights in the works, so any such list would be
the minimum of possible copyrights holders.

All the files remaining in this repository right now were written from
scratch well after any of the listed copyright years, so the listed
copyrights cannot be true. The history can be found in
wayland/wayland-protocols!14 .
To avoid confusion, they are removed.

The license text itself has unknown copyrights according to
https://opensource.org/licenses/MIT

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

This CI check ensures that S-o-b tags are present in each commit, there
are no fix-up commits, and that the merge request allows edits from
maintainers.

See https://freedesktop.pages.freedesktop.org/ci-templates/ci-fairy.html

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

I fixed up some sentences that were hard to read when going through the document.

There are no semantic changes.
Signed-off-by: Benjamin Otte <otte@redhat.com>

Pekka Paalanen authored Sep 27, 2021 and Pekka Paalanen committed Sep 28, 2021

Set up the usual project rules, following what wayland-protocols and
wayland use.

Granting permissions is eased given this is mostly for documentation.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Copied verbatim from
https://gitlab.freedesktop.org/swick/wayland-protocols/-/commits/color/


which matches the wayland-protocols license at version 1.20.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Delete files imported from wayland-protocols that are not needed in this
repository, leaving only the documentation.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

All commits up to this point were lifted from
https://gitlab.freedesktop.org/swick/wayland-protocols/-/commits/color/


as is, except deleting changes to Makefile.am as that file will not
exist here.

Move the color management doc to a more appropriate directory structure.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Naveen Kumar authored Oct 13, 2020 and Pekka Paalanen committed Sep 24, 2021

This patch:
* Addresses feedback & suggestions from Pekka, Swick
* This adds well-known EOTF, chromaticity and whitepoint names in
the protocol
* updates color.rst doc with list of tables & short description for
most of the well-known names
Signed-off-by: Naveen Kumar <naveen1.kumar@intel.com>

Fixes: swick/wayland-protocols#1
Fixes: wayland/wayland-protocols!14 (comment 616851)

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Vitaly Prosyak authored Sep 09, 2020 and Pekka Paalanen committed Sep 24, 2021

Signed-off-by: Vitaly Prosyak <vitaly.prosyak@amd.com>

Sebastian Wick authored Sep 08, 2020 and Pekka Paalanen committed Sep 24, 2021

Signed-off-by: Sebastian Wick <sebastian@sebastianwick.net>

Sebastian Wick authored Sep 08, 2020 and Pekka Paalanen committed Sep 24, 2021

Signed-off-by: Sebastian Wick <sebastian@sebastianwick.net>

Sebastian Wick authored Sep 08, 2020 and Pekka Paalanen committed Sep 24, 2021

color management: require compositors to understand all EOTF, chromaticity and whitepoint names from the protocol
Signed-off-by: Sebastian Wick <sebastian@sebastianwick.net>

Sebastian Wick authored Aug 31, 2020 and Pekka Paalanen committed Sep 24, 2021

* creating a color space now leads through the color_space_creator
  object which allows us to fail at ceating the color space
* there are now three ways to create a color space. From an ICC profile,
  from well-known names and parametrically.
* multiple color_management_outputs can now be created for a single
  wl_output
* color_space_changed is not send when the object is created anymore
* clearify that destroying a color space has no effect on the color
  space state associated with surfaces and outputs
* preferred color space is send only after it is determined or changed
* preferred color space is send to all matching wl_outputs
Signed-off-by: Sebastian Wick <sebastian@sebastianwick.net>

This adds a very high level overview of how color management is supposed
to work on Wayland, compared to how it worked on X11. The aim is to get
people discussing this protocol extension to the same page about the
general approach which is fundamentally different from X11.
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

Sebastian Wick authored Jan 23, 2020 and Pekka Paalanen committed Sep 24, 2021

This protocol specifies a way for a client to set the color space and
HDR metadata of a surface and to get information about the color spaces
and HDR capabilities of outputs.

For more information, see color.rst.
Signed-off-by: Sebastian Wick <sebastian@sebastianwick.net>
[Pekka: added color.rst]
Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>