Le 05/06/2024 à 22:29, Mark Thompson a écrit :
> On 30/05/2024 20:43, averne wrote:
>> This includes a new pixel format for nvtegra hardware frames, and several
>> objects for interaction with hardware blocks.
>> In particular, this contains code for channels (handles to hardware
>> engines), map
On 30/05/2024 20:43, averne wrote:
> This includes a new pixel format for nvtegra hardware frames, and several
> objects for interaction with hardware blocks.
> In particular, this contains code for channels (handles to hardware engines),
> maps (memory-mapped buffers shared with engines), and co
Le lauantaina 1. kesäkuuta 2024, 0.06.55 EEST averne a écrit :
> As for your second question, I probably should've given some
> context about this decision. Initially I thought about writing a
> vaapi driver, but for a number of reasons I decided against it.
VA-API would be difficult anyway as it
Le 31/05/2024 à 10:32, Rémi Denis-Courmont a écrit :
>
>
> Le 30 mai 2024 22:43:07 GMT+03:00, averne a écrit :
>> This includes a new pixel format for nvtegra hardware frames, and several
>> objects for interaction with hardware blocks.
>> In particular, this contains code for channels (handles
Le 30 mai 2024 22:43:07 GMT+03:00, averne a écrit :
>This includes a new pixel format for nvtegra hardware frames, and several
>objects for interaction with hardware blocks.
>In particular, this contains code for channels (handles to hardware engines),
>maps (memory-mapped buffers shared with
This includes a new pixel format for nvtegra hardware frames, and several
objects for interaction with hardware blocks.
In particular, this contains code for channels (handles to hardware engines),
maps (memory-mapped buffers shared with engines), and command buffers
(abstraction for building co
