On Thu, 16 Feb 2023 at 10:25, Simon Ser wrote:
>
> On Thursday, February 16th, 2023 at 10:11, Pekka Paalanen
> wrote:
>
> > Btw. does this also mean that if you use GETFB2 to get handle A, you
> > export that as dmabuf and import in the same open device instance, you
> > again get handle A?
>
>
Hi,
On Thu, 16 Feb 2023 at 09:25, Simon Ser wrote:
> On Thursday, February 16th, 2023 at 10:11, Pekka Paalanen
> wrote:
> > Btw. does this also mean that if you use GETFB2 to get handle A, you
> > export that as dmabuf and import in the same open device instance, you
> > again get handle A?
>
>
On Thu, 16 Feb 2023 09:25:38 +
Simon Ser wrote:
> On Thursday, February 16th, 2023 at 10:11, Pekka Paalanen
> wrote:
>
> > Btw. does this also mean that if you use GETFB2 to get handle A, you
> > export that as dmabuf and import in the same open device instance, you
> > again get handle A?
On Thursday, February 16th, 2023 at 10:11, Pekka Paalanen
wrote:
> Btw. does this also mean that if you use GETFB2 to get handle A, you
> export that as dmabuf and import in the same open device instance, you
> again get handle A?
I haven't tested it, but I believe that is correct.
> IOW, you
On Wed, 15 Feb 2023 17:03:54 +
Simon Ser wrote:
> On Wednesday, February 15th, 2023 at 14:41, Pekka Paalanen
> wrote:
>
> > I didn't know it was at all possible to have different GEM handles
> > pointing to the same object. DMABUF import is guaranteed to return the
> > existing GEM handle,
On Wednesday, February 15th, 2023 at 14:41, Pekka Paalanen
wrote:
> I didn't know it was at all possible to have different GEM handles
> pointing to the same object. DMABUF import is guaranteed to return the
> existing GEM handle, right? Why is GETFB2 different? Why does it not
> have the same p
On Wed, 15 Feb 2023 12:42:00 +
Simon Ser wrote:
> There are two important details missing from the docs:
>
> - If the memory object backing the FB already has a GEM handle,
> it's not re-used, a new one is generated.
> - Aliased planes will return the same GEM handle.
>
> Signed-off-by: S
There are two important details missing from the docs:
- If the memory object backing the FB already has a GEM handle,
it's not re-used, a new one is generated.
- Aliased planes will return the same GEM handle.
Signed-off-by: Simon Ser
Cc: Daniel Vetter
Cc: Pekka Paalanen
---
include/uapi/d
