Am 07.01.19 um 14:05 schrieb Bas Nieuwenhuizen:
> On Mon, Jan 7, 2019 at 1:23 PM Christian König
> wrote:
>> Am 06.01.19 um 21:29 schrieb Bas Nieuwenhuizen:
>>> On Sun, Jan 6, 2019 at 9:23 PM Christian König
>>> wrote:
Am 06.01.19 um 10:46 schrieb Bas Nieuwenhuizen:
> For radv we want to
On Mon, Jan 7, 2019 at 1:23 PM Christian König
wrote:
>
> Am 06.01.19 um 21:29 schrieb Bas Nieuwenhuizen:
> > On Sun, Jan 6, 2019 at 9:23 PM Christian König
> > wrote:
> >> Am 06.01.19 um 10:46 schrieb Bas Nieuwenhuizen:
> >>> For radv we want to be able to pass in a master fd and be sure that
>
Am 06.01.19 um 21:29 schrieb Bas Nieuwenhuizen:
On Sun, Jan 6, 2019 at 9:23 PM Christian König
wrote:
Am 06.01.19 um 10:46 schrieb Bas Nieuwenhuizen:
For radv we want to be able to pass in a master fd and be sure that
the created libdrm_amdgpu device also uses that master fd, so we can
use it
On Sun, Jan 6, 2019 at 9:23 PM Christian König
wrote:
>
> Am 06.01.19 um 10:46 schrieb Bas Nieuwenhuizen:
> > For radv we want to be able to pass in a master fd and be sure that
> > the created libdrm_amdgpu device also uses that master fd, so we can
> > use it for prioritized submission.
> >
> >
Am 06.01.19 um 10:46 schrieb Bas Nieuwenhuizen:
For radv we want to be able to pass in a master fd and be sure that
the created libdrm_amdgpu device also uses that master fd, so we can
use it for prioritized submission.
radv does all interaction with other APIs/processes with dma-bufs,
so we sho
For radv we want to be able to pass in a master fd and be sure that
the created libdrm_amdgpu device also uses that master fd, so we can
use it for prioritized submission.
radv does all interaction with other APIs/processes with dma-bufs,
so we should not need the functionality in libdrm_amdgpu to
