DRI3000 (DRI3) Begins To Take Shape Again

[phoronix]

Phoronix: DRI3000 (DRI3) Begins To Take Shape Again

Immediately following XDC2012 there was a lot of talk about "DRI3", but nothing materialized in time for the forthcoming X.Org Server 1.14 release. The DRI3 plans haven't died off but now Keith Packard is talking about this next Direct Rendering Infrastructure update as DRI3000...

http://www.phoronix.com/vr.php?view=MTMwNjc

[renox]

> DRI3 still revolves around using POSIX file descriptors for passing kernel objects between the X Server and the application.

I wouldn't have thought that Plan9's concept are useful even on low level frameworks!

[uid313]

> DRI3 still revolves around using POSIX file descriptors for passing kernel objects between the X Server and the application.

I wouldn't have thought that Plan9's concept are useful even on low level frameworks!

"Everything is a file" is one of the defining features of Unix.

Unix's successor Plan 9 took this concept into distributed computing with the 9P protocol.

[uid313]

Interesting to see new work being done for X.org even though there is development going on for Wayland.

[garegin]

Dri is used with wayland.

[Ericg]

Dri is used with wayland.

Kernel-side infrastructure of it, maybe. But not the exact extensions, they can't. The extensions are X specific. Unless you're talking about the XWayland backend, but thats different.

[garegin]

Kernel-side infrastructure of it, maybe. But not the exact extensions, they can't. The extensions are X specific. Unless you're talking about the XWayland backend, but thats different.

I hope supporting both x and wayland doesn't slow things down. Progress in already at a glacial pace.

[Ericg]

I hope supporting both x and wayland doesn't slow things down. Progress in already at a glacial pace.

XWayland is just a shim-layer that gets created when you have an X Client that cant also be a Wayland Client. It creates an X server the exact size of the window in question and X is tricked into thinking its in charge when in reality Wayland is a puppeteer over head directing things to be how they want and how they SHOULD be in the Wayland world.

Its actually a fairly elegant solution since X clients dont have to change at all and I dont think its in the way of anything in the Wayland world since there's no guarantees that an X Client will be up at any given time. Its basically just an optional code-path that only gets called if an X client somehow appears.


EDIT: Or did you mean "Supporting" as in developer manpower? I doubt it... All the X devs are Wayland devs for the most part, they know Wayland is the future and that updating X is pretty much just a "Here's some work for us to better the community until KDE hits 5.0 and every Qt and KDE program becomes X/Wayland compatible" lol

[garegin]

XWayland is just a shim-layer that gets created when you have an X Client that cant also be a Wayland Client. It creates an X server the exact size of the window in question and X is tricked into thinking its in charge when in reality Wayland is a puppeteer over head directing things to be how they want and how they SHOULD be in the Wayland world.

Its actually a fairly elegant solution since X clients dont have to change at all and I dont think its in the way of anything in the Wayland world since there's no guarantees that an X Client will be up at any given time. Its basically just an optional code-path that only gets called if an X client somehow appears.


EDIT: Or did you mean "Supporting" as in developer manpower? I doubt it... All the X devs are Wayland devs for the most part, they know Wayland is the future and that updating X is pretty much just a "Here's some work for us to better the community until KDE hits 5.0 and every Qt and KDE program becomes X/Wayland compatible" lol

do you think distro can ship xwayland by the end of the year when it gets merged? kde 5 is a long way off.

[Ericg]

do you think distro can ship xwayland by the end of the year when it gets merged? kde 5 is a long way off.

Hopefully XWayland will get merged into the next Xorg release, hopefully.