On Mon, Jun 24, 2019 at 11:37 AM Michel Dänzer <michel@xxxxxxxxxxx> wrote: > On 2019-06-21 5:52 p.m., Michel Dänzer wrote: > >> That was the entire point of kms, and it succeed really well. That's > >> why I don't think amdgpu doing their own flavour pick is going to help > >> anyone here, > > Other drivers are welcome to emulate amdgpu's design making the above > > possible. :) > > Seriously though, I don't think any changes outside of libdrm/Mesa > should be needed with other drivers either. Fundamentally there's > nothing magic about it, just sharing BOs via PRIME between the render > node file description and that passed in via the EGL/GBM/... API. The libdrm/mesa design isn't the hard part, we have that even as a helper for etnaviv and all those drivers. Being inconsistent here is a think more a nuisance for integrators, who might want to sandbox gpu clients real hard and really want to know what access rights they need to give out. But then we have much, much bigger fish to fry from a cross-driver consistency pov, so *shrug*. Just feels somewhat silly we can't even get agreement or some kind of consistent plan on something fairly simple like this. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ amd-gfx mailing list amd-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/amd-gfx
