[Mesa-dev] [PATCH 3/7] dri: Define DRI_MutableRenderBuffer extensions

[Chad Versace]

On Tue 14 Aug 2018, Tapani Pälli wrote:
> Hi Chad;
> 
> On 08/08/2018 06:53 PM, Tapani Pälli wrote:
> > 
> > 
> > On 07.08.2018 21:16, Chad Versace wrote:
> > > On Mon 06 Aug 2018, Chad Versace wrote:
> > > > On Fri 03 Aug 2018, Tapani Pälli wrote:
> > > > > One tiny nit below but for patches 3,4 and 5:
> > > > > 
> > > > > Reviewed-by: Tapani Pälli <tapani.palli at intel.com>
> > > > > 
> > > > > Special thanks for the documentation. I want to go through
> > > > > rest of changes
> > > > > within Android but I'm currently experiencing some horrible
> > > > > issues with the
> > > > > image building. I'm hoping to resolve those soon and get
> > > > > back to business.
> > > 
> > > Any luck with the Android patches?
> > 
> > I have the build working (for O) now but can test stuff only tomorrow,
> > will get back to you then.
> > 
> > > btw, I plan to start working on and/or reviewing
> > > VK_ANDROID_external_memory_android_hardware_buffer this week.
> > > I'll coordinate with you when I start.
> > 
> > OK cool, Celadon is in process of migrating to P and when that is
> > successfully done I'll get back to looking at this too.
> > 
> 
> As an update, I have P building and running fine now. I've run dEQP tests
> and noticed at least these 3 things I've missed and require
> changes/implementation:
> 
> * vkGetPhysicalDeviceImageFormatProperties2
> * vkGetPhysicalDeviceExternalBufferProperties
> * usage of AHardwareBuffer as backing store for VkBuffer objects
> 
> I'm going to work on these areas and try to get dEQP happier. My test app
> using the extension still seems to work fine, it does not use any APIs above
> but just import/export AHardwareBuffer in context of vkImage.

Great! Thanks for the update. (I will be travelling to Europe all next
week, and was out for most of this week. So, I'm behind on reviewing
everything, and may remain behind until I return from Europe).