Rob Clark

I think if we don't do (1) then that means knowing how map capabilities (by which I think you mean use-cases??) to a set of devices. Which gets us back...

I guess I was hoping to avoid the bootstrap problem by declaring that the client somehow automagically figured out which APIs (via glvnd/vk-loader/etc), and v4l devices, and whatever else, since...

@jekstrand I punted on trying to define exactly how loader works (json or whatever).. that is kinda a boring detail once we figure out whether liballoc backend is the thing...

@jekstrand right, I mentioned as much in USAGE.md: "In cases where the underlying device file is not exposed (such as OpenMAX or OpenCL, or OpenGL when not running on top...

@jekstrand fyi, have a look at https://github.com/robclark/allocator/blob/master/USAGE.md .. I still need to update it for the `capability_set_t` stuff (ie. keep constraints coupled to capabilities), but it does at least show...

@Benjamin-Gaignard I think that is a question for GStreamer dev's.. I was planning to ask Wim to have a look, but probably not until the concept is a bit more...

@Benjamin-Gaignard well, the complication is when two devices can exchange vendor compressed/tiled formats, possibly with associated pitch constraints, etc.. that sort of information is not available in the kernel.

@Benjamin-Gaignard I did suggest a fairly simplified version of that quite some time back to deal with the simple "do I need contiguous or not" case. But there are more...

@jekstrand I think I'd go for your entry 3 (although I think of them more of alloc device instances, ie `alloc_dev_t`in [USAGE.md](https://github.com/cubanismo/allocator/blob/master/USAGE.md). I don't think "liballoc core" should actually be...

@jekstrand to be clear (and maybe I should spiff out [USAGE.md](https://github.com/cubanismo/allocator/blob/master/USAGE.md) a bit more) I don't think `alloc_dev_t` would be passed across the wire, but rather the serialized `capabilities_set_t`. Ie....