On Thu, 3 Aug 2023 at 16:46, Daniel Stone wrote:
> On Tue, 9 Nov 2021 at 09:13, Daniel Vetter wrote:
> > Seconded on just landing this without trying to perfect it first, because
> > I was just looking for it and didn't find it anywhere :-/
>
> Swing and a miss ...
>
> I've just sent out v2 with
On Tue, 9 Nov 2021 at 09:13, Daniel Vetter wrote:
> On Mon, Nov 08, 2021 at 04:18:22PM -0800, James Jones wrote:
> > On 9/6/21 5:28 AM, Simon Ser wrote:
> > > > Since there's a lot of confusion around this, document both the rules
> > > > and the best practice around negotiating, allocating,
On Tuesday, November 9th, 2021 at 10:13, Daniel Vetter wrote:
> On Mon, Nov 08, 2021 at 04:18:22PM -0800, James Jones wrote:
> > On 9/6/21 5:28 AM, Simon Ser wrote:
> > > > Since there's a lot of confusion around this, document both the rules
> > > > and the best practice around negotiating,
On Mon, Nov 08, 2021 at 04:18:22PM -0800, James Jones wrote:
> On 9/6/21 5:28 AM, Simon Ser wrote:
> > > Since there's a lot of confusion around this, document both the rules
> > > and the best practice around negotiating, allocating, importing, and
> > > using buffers when crossing
On Mon, Nov 08, 2021 at 04:21:04PM -0800, James Jones wrote:
> On 9/8/21 2:44 AM, Simon Ser wrote:
> > > stride
> > >
> >
> > I think what's clear is:
> >
> > - Per-plane property
> > - In bytes
> > - Offset between two consecutive rows
> >
> > How that applies to weird YUV formats is
On 9/8/21 2:44 AM, Simon Ser wrote:
stride
I think what's clear is:
- Per-plane property
- In bytes
- Offset between two consecutive rows
How that applies to weird YUV formats is the tricky question…
Btw. there was a fun argument whether the same modifier value could
mean
On 9/6/21 5:28 AM, Simon Ser wrote:
Since there's a lot of confusion around this, document both the rules
and the best practice around negotiating, allocating, importing, and
using buffers when crossing context/process/device/subsystem boundaries.
This ties up all of dmabuf, formats and
On Sun, Sep 05, 2021 at 01:27:42PM +0100, Daniel Stone wrote:
> Since there's a lot of confusion around this, document both the rules
> and the best practice around negotiating, allocating, importing, and
> using buffers when crossing context/process/device/subsystem boundaries.
>
> This ties up
> stride
>
I think what's clear is:
- Per-plane property
- In bytes
- Offset between two consecutive rows
How that applies to weird YUV formats is the tricky question…
> Btw. there was a fun argument whether the same modifier value could
> mean different things on different devices.
On Sun, 5 Sep 2021 13:27:42 +0100
Daniel Stone wrote:
> Since there's a lot of confusion around this, document both the rules
> and the best practice around negotiating, allocating, importing, and
> using buffers when crossing context/process/device/subsystem boundaries.
>
> This ties up all
On 05/09/2021 13:27, Daniel Stone wrote:
Since there's a lot of confusion around this, document both the rules
and the best practice around negotiating, allocating, importing, and
using buffers when crossing context/process/device/subsystem boundaries.
This ties up all of dmabuf, formats and
> Since there's a lot of confusion around this, document both the rules
> and the best practice around negotiating, allocating, importing, and
> using buffers when crossing context/process/device/subsystem boundaries.
>
> This ties up all of dmabuf, formats and modifiers, and their usage.
>
>
Since there's a lot of confusion around this, document both the rules
and the best practice around negotiating, allocating, importing, and
using buffers when crossing context/process/device/subsystem boundaries.
This ties up all of dmabuf, formats and modifiers, and their usage.
Signed-off-by:
13 matches
Mail list logo
