On Wed, Jul 5, 2017 at 4:50 PM, Dave Airlie <airl...@gmail.com> wrote:
> > > > > > This is something I've been on the fence about for a while, mostly > > because the vulkan and gl driver for mesa come out of the same source > > base. > > In addition to the issues raised by Jason, radv isn't the only Vulkan > driver for AMD GPUs. > > > I don't think Andres patch should be made jump through hoops for a driver > that isn't open source. AMD are free to provide patches to support this use > case but asking anyone outside AMD to care for a piece of software that > isn't > open source, isn't a very nice thing to do. > > From reading Jason's requests it does look like just leave it to the > drivers to > sort out is the best option, > Thank you. I think that's the best option too. > and for radeonsi/radv we could go with a static > string as we at least share addrlib in this world. Beyond that I think AMD > would > need to propose later patch for interop with the pro driver. > But what if addrlib changes? :-) If you have any arbitrary decisions in surface layout that are made using a heuristic, then you need to at least make this some sort of addrlib version. Now I'm just trolling...
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
