<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>Hi Andreas,</div><div><br></div><div>that might indeed be something we want to do for Vulkan. I think moving the defines is fine, however I think that before we start moving data structures and types around we should probably have a very good understanding of what we'll need for Vulkan, and that probably requires that we have a functional enough driver first so we are certain that the data structures we currently have in the GL driver match exactly and optimally what we need for Vulkan and we are not just early guessing. The other reason is that in early stages of development it is just easier to copy what you need and modify it on the go as you make progress in the driver without having to care too much about whether they are shared structures/types affecting another driver and then refactor or generlaize the aspects that you realize can be shared across both drivers a bit later in the process when things are more mature and we have a better understanding of what we can share effectively. Does this make sense to you?</div><div><br></div><div>Iago</div><div><br></div><div>On Mon, 2019-12-09 at 18:18 +0100, abergmeier@gmx.net wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div style="font-family: Verdana;font-size: 12.0px;"><div>Anyone objecting to moving struct v3d_format and native defines from Gallium to Broadcom?</div>
<div>I think it would make sense to use it similarly in Vulkan.</div>
<div> </div>
<div>Cheers</div>
<div>Andreas</div></div>
<pre>_______________________________________________</pre><pre>mesa-dev mailing list</pre><pre><a href="mailto:mesa-dev@lists.freedesktop.org">mesa-dev@lists.freedesktop.org</a></pre><pre><a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a></pre></blockquote></body></html>