The C for Media (Metal) Runtime provides the Vebox interface (CmVebox) with parameters passing as a CmBufferUP object. It's not clear how to convert from (assumedly) CM_VEBOX_PARAM_G10 to memory buffer correctly (for further feeding this to device->CreateBufferUP() and vebox->SetParam() accordingly). An attempt to copy the CM_VEBOX_PARAM_G10 structure instance memory as it is (contains pointers!) leads to a GPU hang / vecs0 resetting on reading the output surface.
i915 0000:00:02.0: [drm] GPU HANG: ecode 12:8:2cff3ffc, in cm-test [5023]
A working CM RT example with Vebox is very appreciated, as it's a part of the official API.
The C for Media (Metal) Runtime provides the Vebox interface (CmVebox) with parameters passing as a CmBufferUP object. It's not clear how to convert from (assumedly) CM_VEBOX_PARAM_G10 to memory buffer correctly (for further feeding this to device->CreateBufferUP() and vebox->SetParam() accordingly). An attempt to copy the CM_VEBOX_PARAM_G10 structure instance memory as it is (contains pointers!) leads to a GPU hang / vecs0 resetting on reading the output surface.
i915 0000:00:02.0: [drm] GPU HANG: ecode 12:8:2cff3ffc, in cm-test [5023]
A working CM RT example with Vebox is very appreciated, as it's a part of the official API.