<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 3, 2019 at 6:18 PM Alyssa Rosenzweig <<a href="mailto:alyssa@rosenzweig.io">alyssa@rosenzweig.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> Small comment, you should plan on single build for all supported<br>
> generations.. I'm not entirely sure if this same header is eventually<br>
> planned to be #include'd from different C code w/ different defines<br>
> for gpu gen (afaict you just currently hard-code it at the top of this<br>
> header).. But distro's will be unhappy if it comes to different mesa<br>
> builds for 8xx vs 6xx ;-)<br>
<br>
Yeah, that's a moderately high-prio item, only blocking on other things<br>
being more interesting ;)<br>
<br>
> Also, I guess for your sanity at some point you'll want to autogen<br>
> cmdstream encoding and decoding from a single source. I get the<br>
> impression that envytools isn't the right thing for the bitpacked<br>
> format for mali cmdstream. Maybe the intel thing is better? But I<br>
> didn't get very far w/ a2xx r/e before I realized that keeping hand<br>
> coded decoding and encoding in sync sucked.<br>
<br>
Sure, but.. autogen from.. what? As you note, Mali's "cmdstream" is<br>
wacky and doesn't line up with the model assumed by most of these tools.<br>
<br>
Also, if I have to read/write XML, I might lose my sanity faster ;P<br>
<br>
> Anyways, totally fine w/ those details getting worked out in-tree,<br>
> after merging.<br>
> <br>
> Acked-by: Rob Clark <<a href="mailto:robdclark@gmail.com" target="_blank">robdclark@gmail.com</a>><br>
<br>
Thank you!<br>
<br>
(Is there any particular ack we're waiting for for pushing?)<br></blockquote><div><br></div><div>I don't think so. You've gotten enough buy-in from the community so far that, if your build system and core (if any) changes aren't going to break anything, you should just land it and start doing in-tree development! Right after the 19.0 branch point (which was Wednesday) is a great time to do it too because any small breakages won't cause any release problems.</div><div><br></div><div>--Jason<br></div></div></div>