[Mesa-dev] [RFC 00/22] DRI3 v1.1, ANV dmabuf

Emil Velikov emil.l.velikov at gmail.com
Tue Jun 20 09:26:31 UTC 2017


Hi Daniel,

On 8 June 2017 at 19:43, Daniel Stone <daniels at collabora.com> wrote:
> Hi,
> With full support for modifiers in DRIimage, this patch series adds
> support for fully plumbing them through X11. A patchset proposing
> an extension to DRI3 to support multiple planes and modifiers can
> be found here:
> https://lists.x.org/archives/xorg-devel/2017-June/053854.html
>
> The Git trees, all of which are using the wip/2017-05/dri3-v1.1 branch,
> can be found here:
>
> git://git.collabora.com/git/user/daniels/xcb-proto
>   - contains support for lists of FDs, as well as the protocol itself
> git://git.collabora.com/git/user/daniels/libxcb
>   - support for lists of FDs
> git://git.collabora.com/git/user/daniels/dri3proto
>   - what it says on the box
> git://git.collabora.com/git/user/daniels/mesa
>   - this patchset, as well as the previous to enable modifier
>     import/queries on i965:
>     https://lists.freedesktop.org/archives/mesa-dev/2017-June/158092.html
> git://git.collabora.com/git/user/daniels/xserver
>   - X server support (note: has rough edges)
>
Since exact implementation details [on Mesa size] can take a while,
I'm thinking whether prioritising and merging the protocol changes
won't be a good idea.

By doing so, one can roll releases of said components, making it will
be easier for those to reach the build/test servers.

As a nice 'side-effect' we can/should bump the required version and
drop the ifdef guards through the codebase - be that Mesa or Xserver.
This way we'll have an early, explicit, error if the build/test
machine is not updated. As otherwise one will build X/Mesa w/o DRi3
1.1 support and waste time debugging why ;-)

-Emil


More information about the mesa-dev mailing list