KonstantinSeurer/mesa: Mesa3D Graphics Library (Bleeding edge ray tracing branches)

Mesa3D Graphics Library (Bleeding edge ray tracing branches)

Go to file

Alyssa Rosenzweig 0fcddd4d2c pan/bi: Rework varying linking on Valhall Valhall introduces hardware-allocated varyings. Instead of allocating varying descriptors on the CPU with a slot based interface, the driver just tells the hardware how many bytes to allocate per vertex and loads/stores with byte offsets. This is much nicer! However, this requires us to rework our linking code to account for separable shaders. With separable shaders, we can't rely on driver_location matching between stages, and unlike on Midgard, we can't resolve the differences with curated command stream descriptors. However, we can rely on slots matching. So we should "just" determine the byte offsets based on the slot, and then separable shaders work. For GLES, it really is that easy. For desktop GL, it's not -- desktop GL brings unpredictable extra varyings like COL1 and TEX2. Allocating space for all of these unconditionally would hamper performance. To cope, we key fragment shaders to the set of non-GLES varyings written by the linked vertex shader. Then we may define an efficient ABI, where only apps only pay for what they use. Fixes various tests in dEQP-GLES31.functional.separate_shader.random.* on Valhall. Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16310>		2022-05-04 13:07:59 +00:00
.gitlab/issue_templates	issue_templates/Bug Report: Rename master branch to main	2021-05-05 12:20:11 -07:00
.gitlab-ci	meson: add a video codec support option	2022-04-28 22:27:27 +00:00
android	gallium/swr: Remove common code and build options	2021-12-06 23:37:50 +00:00
bin	bin: Add a script for filtering/sorting refcount logs	2022-05-02 16:58:20 +00:00
build-support	…
docs	docs: explain state emission in Anv	2022-05-03 17:12:45 +00:00
include	intel/dev: sync ADL-S pci ids with linux	2022-05-04 18:01:45 +10:00
src	pan/bi: Rework varying linking on Valhall	2022-05-04 13:07:59 +00:00
subprojects	meson: Update libelf wrap for Windows	2021-11-12 09:46:10 +00:00
.dir-locals.el	…
.editorconfig	editorconfig: Use 3-space tabs for .rst	2021-06-22 17:37:55 +00:00
.gitattributes	Add new rules to .gitattributes	2022-01-19 15:17:17 +00:00
.gitignore	…
.gitlab-ci.yml	ci: intel: Merge anv and iris into src/intel/ci	2022-04-27 12:35:13 +00:00
.mailmap	.mailmap: Switch Jason Ekstrand to @collabora.com	2022-01-26 20:08:31 +00:00
.travis.yml	travis: Download XQuartz from GitHub.	2021-05-29 10:25:16 +00:00
CODEOWNERS	ci: add Broadcom CI maintainer	2022-04-12 10:42:31 +00:00
README.rst	docs: promote #dri-devel on oftc over freenode	2021-05-24 09:21:48 +00:00
VERSION	VERSION: bump to 22.2-devel for next cycle	2022-04-13 23:40:25 +00:00
meson.build	meson: Tell glslang to be quiet.	2022-05-04 11:30:43 +00:00
meson_options.txt	meson: deprecate specifying osmesa-bits	2022-04-29 19:30:03 +00:00

README.rst

`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library
======================================================


Source
------

This repository lives at https://gitlab.freedesktop.org/mesa/mesa.
Other repositories are likely forks, and code found there is not supported.


Build & install
---------------

You can find more information in our documentation (`docs/install.rst
<https://mesa3d.org/install.html>`_), but the recommended way is to use
Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_):

.. code-block:: sh

  $ mkdir build
  $ cd build
  $ meson ..
  $ sudo ninja install


Support
-------

Many Mesa devs hang on IRC; if you're not sure which channel is
appropriate, you should ask your question on `OFTC's #dri-devel
<irc://irc.oftc.net/dri-devel>`_, someone will redirect you if
necessary.
Remember that not everyone is in the same timezone as you, so it might
take a while before someone qualified sees your question.
To figure out who you're talking to, or which nick to ping for your
question, check out `Who's Who on IRC
<https://dri.freedesktop.org/wiki/WhosWho/>`_.

The next best option is to ask your question in an email to the
mailing lists: `mesa-dev\@lists.freedesktop.org
<https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_


Bug reports
-----------

If you think something isn't working properly, please file a bug report
(`docs/bugs.rst <https://mesa3d.org/bugs.html>`_).


Contributing
------------

Contributions are welcome, and step-by-step instructions can be found in our
documentation (`docs/submittingpatches.rst
<https://mesa3d.org/submittingpatches.html>`_).

Note that Mesa uses gitlab for patches submission, review and discussions.