DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
Signed-off-by: Chia-I Wu
---
.../linux-dmabuf/linux-dmabuf-unstable-v1.xml | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
b/unstable
for each modifier returned by
eglQueryDmaBufModifiersEXT.
Signed-off-by: Chia-I Wu
---
.../linux-dmabuf/linux-dmabuf-unstable-v1.xml | 20 +--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
b/unstable/linux-dmabuf
Talked with Daniel offline. I sent a different version to revive the
format event.
On Mon, Apr 1, 2019 at 10:41 AM Chia-I Wu wrote:
> DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
>
> Signed-off-by: Chia-I Wu
> ---
> .../linux-dmabuf/linux-dmabuf-
dvertise formats and
"modifier" events are used to advertise modifiers.
The prior patch describes the behavior of weston, and this version
describes the behavior of mutter.
On Wed, Apr 10, 2019 at 12:20 AM Pekka Paalanen wrote:
> On Tue, 9 Apr 2019 15:22:13 -0700
> Chia-I Wu wr
On Wed, Apr 10, 2019 at 12:40 PM Simon Ser wrote:
> On Wednesday, April 10, 2019 9:25 PM, Chia-I Wu wrote:
> > Both implementations support formats that have no explicit modifiers.
> > But when it comes to buffer creation, modifier_hi/lo is required
> > again. It is un
On Thu, Apr 11, 2019 at 7:12 AM Simon Ser wrote:
> On Thursday, April 11, 2019 11:48 AM, Pekka Paalanen
> wrote:
> > Hi,
> >
> > at first hand, I would keep Weston's behaviour, because that is what
> > the current protocol specification says exactly. The specification text
> > is very clear on t
I agree using DRM_FORMAT_MOD_INVALID for implicit modifier is simplest.
Let's move the discussion to the other patch which does that.
On Fri, Apr 12, 2019 at 2:17 AM Pekka Paalanen wrote:
> On Thu, 11 Apr 2019 15:33:06 -0700
> Chia-I Wu wrote:
>
> > On Thu, Apr 11, 2019
Tue, Apr 9, 2019 at 3:23 PM Chia-I Wu wrote:
> Talked with Daniel offline. I sent a different version to revive the
> format event.
>
> On Mon, Apr 1, 2019 at 10:41 AM Chia-I Wu wrote:
>
>> DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
On Tue, Apr 16, 2019 at 2:52 AM Pekka Paalanen wrote:
>
> On Fri, 12 Apr 2019 10:50:49 -0700
> Chia-I Wu wrote:
>
> > Moving the discussion to this patch...
> >
> > This patch clarifies how implicit modifier can be supported, modelling
> > after Weston&
DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
It provides legacy support and makes it easier to replace wl_drm.
Signed-off-by: Chia-I Wu
---
.../linux-dmabuf/linux-dmabuf-unstable-v1.xml| 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git
DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
It provides legacy support and makes it easier to replace wl_drm.
v3: DRM_FORMAT_MOD_INVALID must be advertised to be supported (which
requires a version bump)
Signed-off-by: Chia-I Wu
---
.../linux-dmabuf/linux-dmabuf
On Tue, Apr 16, 2019 at 11:54 AM Simon Ser wrote:
>
> On Tuesday, April 16, 2019 8:06 PM, Chia-I Wu wrote:
> > DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
> > It provides legacy support and makes it easier to replace wl_drm.
> >
>
DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
It provides legacy support and makes it easier to replace wl_drm.
v3: DRM_FORMAT_MOD_INVALID must be advertised to be supported (which
requires a version bump)
v4: no version bump, but a note for now
Signed-off-by: Chia-I
I hope this captures the discussion: clarify DRM_FORMAT_MOD_INVALID and a note
On Wed, Apr 17, 2019 at 9:40 AM Chia-I Wu wrote:
>
> DRM_FORMAT_MOD_INVALID means to derive the modifier from the dmabuf.
> It provides legacy support and makes it easier to replace wl_dr
Hi,
Can you commit this patch for me, if all looks good?
On Wed, Apr 17, 2019 at 9:41 AM Chia-I Wu wrote:
>
> I hope this captures the discussion: clarify DRM_FORMAT_MOD_INVALID and a note
>
> On Wed, Apr 17, 2019 at 9:40 AM Chia-I Wu wrote:
> >
> > DRM_FORMAT_MOD_INV
On Thu, May 2, 2019 at 4:36 AM Daniel Stone wrote:
>
> Hi,
>
> On Wed, 1 May 2019 at 09:53, Pekka Paalanen wrote:
> > On Wed, 24 Apr 2019 10:07:47 -0700 Chia-I Wu wrote:
> > > Can you commit this patch for me, if all looks good?
> >
> > I was almost a
On Tue, May 25, 2021 at 2:18 PM Jason Ekstrand wrote:
> Modern userspace APIs like Vulkan are built on an explicit
> synchronization model. This doesn't always play nicely with the
> implicit synchronization used in the kernel and assumed by X11 and
> Wayland. The client -> compositor half of th
On Sat, Jan 29, 2011 at 10:19 PM, Arthur Zhu
wrote:
>
> drmdpy->event_handler->new_drm_screen(&drmdpy->base, name, drmdpy->fd);
>
> Dose there have a chance to call new_sw_screen?
You cannot use swrast with DRM. Judging by the log below, you have an
i915 card. It is best supported by egl_dri2, w
ed some kind of warnings about package missing or just don't
> check them up to users?
Yeah, something like --enable-egl-dri2 would be helpful. Mind to work
on a patch?
> Best Regards,
> Arthur
>
>
> 2011/1/30 Chia-I Wu
>>
>> On Sat, Jan 29, 2011 at 10:19 PM, Arthur
2011/2/6 Arthur Zhu :
> From 7f26f3b6692a8a8061c0d817388505d4190e88a0 Mon Sep 17 00:00:00 2001
> From: Arthur Zhu
> Date: Mon, 7 Feb 2011 13:50:55 +0800
> Subject: [PATCH] Adding --enable-egl-dri2-x11&drm option.
>
> ---
> configure.ac | 34 +-
> 1 files changed,
20 matches
Mail list logo
