On Wed, 17 Apr 2019 at 13:37, Sebastian Wick
wrote:
>
>
>
> On April 17, 2019 12:38:15 PM GMT+02:00, Erwin Burema
> wrote:
> >On Wed, 17 Apr 2019 at 11:32, Pekka Paalanen
> >wrote:
> >>
> >> On Tue, 16 Apr 2019 23:42:30 +0200
> >> Erwin Burema wrote:
> >>
> >> > On Tue, 16 Apr 2019 at 17:03, P
On Wednesday, April 17, 2019 10:06 PM, Drew DeVault wrote:
> > On the mailing list front, I think wayland-devel@ is probably quiet
> > enough these days - and focused on common protocol-like stuff - that
> > we could probably just reuse that list.
>
> -1, it's way too noisy imo.
I'm fine with bot
Sorry for the delay, catching up on my emails now. Responding to Daniel
as the other emails don't have much actionable stuff, but I read
everything on this thread. Thanks for the feedback!
On 2019-04-08 6:18 PM, Daniel Stone wrote:
> On the members-only front, I think it's important for us to be
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_drm.
>
> v3: DRM_FORMAT_MOD_INVAL
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 Wu
> On Apr 17, 2019, at 03:27, Pekka Paalanen wrote:
>
> On Tue, 16 Apr 2019 14:28:16 -0400
> Jean-Francois Dagenais wrote:
>
>> In the end though, all I am really paid for is adding remote screen
>> capability
>> in our product which is quite a subset of a proper generic VNC backend. The
>> r
On April 17, 2019 12:38:15 PM GMT+02:00, Erwin Burema
wrote:
>On Wed, 17 Apr 2019 at 11:32, Pekka Paalanen
>wrote:
>>
>> On Tue, 16 Apr 2019 23:42:30 +0200
>> Erwin Burema wrote:
>>
>> > On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen
>wrote:
>> > >
>> > > On Tue, 16 Apr 2019 13:33:02 +
>>
On Wednesday, April 17, 2019 2:10 PM, Pekka Paalanen
wrote:
> On Tue, 16 Apr 2019 10:06:43 -0700
> 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.
> >
> > Signed-off-by: Chia-I Wu
>
On Tue, 16 Apr 2019 10:06:43 -0700
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.
>
> Signed-off-by: Chia-I Wu
> ---
> .../linux-dmabuf/linux-dmabuf-unstable-v1.xml| 16
On Wednesday, April 17, 2019 2:05 PM, Pekka Paalanen
wrote:
> On Wed, 17 Apr 2019 05:45:41 +
> Simon Ser cont...@emersion.fr wrote:
>
> > I think it would be good to clarify that the "format" event is not sent
> > in this version? And maybe make it a protocol error to send a
> > format/modifi
On Wed, 17 Apr 2019 05:45:41 +
Simon Ser wrote:
> I think it would be good to clarify that the "format" event is not sent
> in this version? And maybe make it a protocol error to send a
> format/modifier combination that wasn't advertised?
As I explained before, I wouldn't make the protocol
On Wednesday, April 17, 2019 1:54 PM, Pekka Paalanen
wrote:
> > I thought the plan was to bump the version to make it a protocol error?
>
> I didn't think it was. The idea was just to clarify existing protocol,
> not bump the revision to introduce new semantics.
>
> The v2 patch looks fine to me.
On Tue, 16 Apr 2019 18:54:48 +
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.
> >
> > Signed-off-by: Chia-I Wu
> > ---
> >
On Wed, 17 Apr 2019 at 11:32, Pekka Paalanen wrote:
>
> On Tue, 16 Apr 2019 23:42:30 +0200
> Erwin Burema wrote:
>
> > On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen wrote:
> > >
> > > On Tue, 16 Apr 2019 13:33:02 +
> > > Erwin Burema wrote:
> > >
> > > > On Tuesday, 16 April 2019, Pekka Paal
On Wednesday, April 17, 2019 1:23 PM, Barry Song <21cn...@gmail.com> wrote:
> Simon Ser cont...@emersion.fr 于2019年4月15日周一 下午5:18写道：
>
> > Hi,
> > Weston now uses GitLab 1 merge requests for contributions. Can you
> > resend your patch on GitLab?
>
> sure. do i just need to send it for master, or do
Simon Ser 于2019年4月15日周一 下午5:18写道：
>
> Hi,
>
> Weston now uses GitLab [1] merge requests for contributions. Can you
> resend your patch on GitLab?
sure. do i just need to send it for master, or do we also do a fix for
6.0 and 5.0 release?
>
> Thanks,
>
> [1]: https://gitlab.freedesktop.org/waylan
Hi guys,
I got some very weird result while using transient window in weston.
Let's start from a simplest qt program:
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
MainWindow w;
w.show();
QDialog d1(&w)
d1.setWindowTitle("transient& non toplevel dialog d1");
On Tue, 16 Apr 2019 23:42:30 +0200
Erwin Burema wrote:
> On Tue, 16 Apr 2019 at 17:03, Pekka Paalanen wrote:
> >
> > On Tue, 16 Apr 2019 13:33:02 +
> > Erwin Burema wrote:
> >
> > > On Tuesday, 16 April 2019, Pekka Paalanen wrote:
> > > > On Tue, 16 Apr 2019 13:11:06 +0200
> > > > Erwin
On Tue, 16 Apr 2019 14:28:16 -0400
Jean-Francois Dagenais wrote:
> In the end though, all I am really paid for is adding remote screen capability
> in our product which is quite a subset of a proper generic VNC backend. The
> resulting work would not be upstreamable, but would still be of value i
On Tue, 16 Apr 2019 10:04:18 -0700
Chia-I Wu wrote:
> 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,
20 matches
Mail list logo
