Rob Clark

@cubanismo btw, one question/thought.. are you anticipating that LUID/UUID is precise enough to identify, for example, exact model/revision of gpu, ie. to the point where the `alloc_dev_t` implementation would not...

@cubanismo ok, I wasn't expecting that either, but wanted to check that I wasn't misunderstanding your idea. I guess we _could_ invent a mechanism that devices could expose the necessary...

This does end up sounding more like a "buffer manager" than simply an allocator. Although possibly the only thing really needed that isn't already covered elsewhere (gbm, fence-fd's and the...

I was assuming that allocator backend was just a shim that calls into driver to do whatever. But yeah, I guess if that was exposed as a "liballoc" API then...

I guess my biggest concern is dataformat seems like way overkill for something like a v4l camera or video decoder. If we had some helpers that can map generic fourcc...

@jekstrand / @cubanismo / @fluppeteer, So some random thought, and something I mentioned in https://github.com/cubanismo/allocator/commit/d3c96b685f41ed92c467776e47cce9d748208aad but it seems like capability blocks are kinda the same thing as dataformat descriptors.. ie....

@jekstrand fwiw, I'm assuming we don't have to exchange this over the wire every frame so the conversion between dataformat and intel format enum is inconsequential. Admittedly I'm still at...

@jekstrand I guess an interesting question is what might we want in "capabilities block" that doesn't fit in dataformat? It seems everything that I can think of that wouldn't fit...

hmm, dataformat covering (standard) compressed formats does blur the lines a bit. My assumption was that vendor-id's and types were intended to cover vendor tiling and compression, similar to how...

> The OpenGLES3.2 specification says > > Section 14.3.2 > "Any fragment colors which are not written by the fragment shader are undefined." In this case, it is not that...