Re: [PATCH 4/6] libweston: fbdev: set fb device info upon the first run.

2017-10-02 Thread Pekka Paalanen
On Mon, 02 Oct 2017 23:14:26 -0400 nerdopolis wrote: > On Tuesday, September 26, 2017 9:45:43 AM EDT Pekka Paalanen wrote: > > On Thu, 14 Sep 2017 23:08:51 -0400 > > nerdopolis wrote: > > > > > On Wednesday, September 6, 2017 8:17:21 AM EDT nerdopolis wrote: > > > > This attempts to wake up

Re: [PATCH 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

2017-10-02 Thread Pekka Paalanen
On Mon, 02 Oct 2017 23:10:14 -0400 nerdopolis wrote: > On Tuesday, September 26, 2017 9:17:37 AM EDT you wrote: > > On Wed, 6 Sep 2017 08:17:18 -0400 > > nerdopolis wrote: > > > > > --- > > > > Hi, > > > > the commit message should contain at least briefly why we want this. I > > have a

Re: [PATCH 4/6] libweston: fbdev: set fb device info upon the first run.

2017-10-02 Thread nerdopolis
On Tuesday, September 26, 2017 9:45:43 AM EDT Pekka Paalanen wrote: > On Thu, 14 Sep 2017 23:08:51 -0400 > nerdopolis wrote: > > > On Wednesday, September 6, 2017 8:17:21 AM EDT nerdopolis wrote: > > > This attempts to wake up secondary framebuffer devices > > > (/dev/fb1 and up) as usually these

Re: [PATCH 1/6] libweston: set the seat automatically based on the XDG_SEAT environment variable

2017-10-02 Thread nerdopolis
On Tuesday, September 26, 2017 9:17:37 AM EDT you wrote: > On Wed, 6 Sep 2017 08:17:18 -0400 > nerdopolis wrote: > > > --- > > Hi, > > the commit message should contain at least briefly why we want this. I > have a feeling this is the right thing to do, but I can't quite put the > reason into

[PATCH] documentation: clarify the need for wl_surface.damage

2017-10-02 Thread Mahdi Khanalizadeh
Add an explanation for wl_surface.attach why a wl_surface.damage request is necessary. Explicitly declare it implementation defined behaviour if the wl_surface.damage request is omitted to give the compositor some leeway on how it handles attaches. Signed-off-by: Mahdi Khanalizadeh --- protocol/

Re: [PATCH weston v12 05/40] compositor-drm: Use drm_plane for scanout plane

2017-10-02 Thread Pekka Paalanen
On Tue, 26 Sep 2017 18:15:38 +0100 Daniel Stone wrote: > Use a real drm_plane to back the scanout plane, displacing > output->fb_{last,cur,pending} to their plane-tracked equivalents. > > Signed-off-by: Daniel Stone > --- > libweston/compositor-drm.c | 167 > +++---

Re: [PATCH] xdg-foreign-v2: Fix various documentation issues from the API change

2017-10-02 Thread Marco Martin
ping? shouldn't the 3 patches in total be pushed now? -- Marco Martin On Tue, Sep 26, 2017 at 3:53 PM, Jonas Ådahl wrote: > It stilled referred to the removed requests, so change those places to > refer to the renamed ones. > > While at it, also change documentation to refer directly to > xdg_to

Re: [PATCH weston v12 03/40] [TEST] compositor-drm: Allow disabling universal planes

2017-10-02 Thread Pekka Paalanen
On Fri, 29 Sep 2017 14:21:02 +0100 Emil Velikov wrote: > On 26 September 2017 at 18:15, Daniel Stone wrote: > > Add a test environment variable to allow disabling universal planes. > > > > Signed-off-by: Daniel Stone > > --- > > libweston/compositor-drm.c | 6 -- > > 1 file changed, 4 inse

Re: [PATCH] shared: struct timespec is in time.h

2017-10-02 Thread Pekka Paalanen
On Sun, 1 Oct 2017 14:31:10 +0200 "Yann E. MORIN" wrote: > On the musl C library, tests/timespec-text.c does not build, with the > following error: > > In file included from tests/timespec-test.c:36:0: > ./shared/timespec-util.h:41:21: warning: ‘struct timespec’ declared > inside pa

Re: [PATCH wayland] protocol: Suggest get_registry not be called frequently

2017-10-02 Thread Pekka Paalanen
On Fri, 29 Sep 2017 21:20:13 +0100 Daniel Stone wrote: > On 29 September 2017 at 19:46, Derek Foreman wrote: > > I've heard some complaints that wl_display.get_registry "leaks" > > server memory because wl_registry has no destructor. While this isn't > > strictly true - all those resources are