Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-06 Thread Yann E. MORIN
Emilio, All, On 2014-02-03 16:57 +0100, poch...@gmail.com spake thusly: > From: Emilio Pozuelo Monfort > > The input initialization code assumes the outputs have already > been initialized; thus create the outputs first. This fixes a > segfault upon startup. It is also what the drm and fbdev bac

Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-05 Thread Kristian Høgsberg
On Mon, Feb 03, 2014 at 04:57:27PM +0100, poch...@gmail.com wrote: > From: Emilio Pozuelo Monfort > > The input initialization code assumes the outputs have already > been initialized; thus create the outputs first. This fixes a > segfault upon startup. It is also what the drm and fbdev backends

Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-04 Thread Pekka Paalanen
On Mon, 3 Feb 2014 16:57:27 +0100 poch...@gmail.com wrote: > From: Emilio Pozuelo Monfort > > The input initialization code assumes the outputs have already > been initialized; thus create the outputs first. This fixes a > segfault upon startup. It is also what the drm and fbdev backends > do.

Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-04 Thread Silvan Jegen
On Tue, Feb 04, 2014 at 09:42:55AM +0100, Yann E. MORIN wrote: > > From: Emilio Pozuelo Monfort > > > > The input initialization code assumes the outputs have already > > been initialized; thus create the outputs first. This fixes a > > segfault upon startup. It is also what the drm and fbdev bac

Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-04 Thread Pekka Paalanen
On Tue, 04 Feb 2014 08:47:55 +0100 Emilio Pozuelo Monfort wrote: > On 03/02/14 20:00, Pekka Paalanen wrote: > > On Mon, 3 Feb 2014 16:57:27 +0100 > > poch...@gmail.com wrote: > > > >> From: Emilio Pozuelo Monfort > >> > >> The input initialization code assumes the outputs have already > >> bee

Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-04 Thread Yann E. MORIN
Emilio, All, On 2014-02-03 16:57 +0100, poch...@gmail.com spake thusly: > From: Emilio Pozuelo Monfort > > The input initialization code assumes the outputs have already > been initialized; thus create the outputs first. This fixes a > segfault upon startup. It is also what the drm and fbdev bac

Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-03 Thread Emilio Pozuelo Monfort
On 03/02/14 20:00, Pekka Paalanen wrote: > On Mon, 3 Feb 2014 16:57:27 +0100 > poch...@gmail.com wrote: > >> From: Emilio Pozuelo Monfort >> >> The input initialization code assumes the outputs have already >> been initialized; thus create the outputs first. This fixes a >> segfault upon startup

Re: [PATCH weston] compositor-rpi: Fix input initialization

2014-02-03 Thread Pekka Paalanen
On Mon, 3 Feb 2014 16:57:27 +0100 poch...@gmail.com wrote: > From: Emilio Pozuelo Monfort > > The input initialization code assumes the outputs have already > been initialized; thus create the outputs first. This fixes a > segfault upon startup. It is also what the drm and fbdev backends > do.

[PATCH weston] compositor-rpi: Fix input initialization

2014-02-03 Thread pochu27
From: Emilio Pozuelo Monfort The input initialization code assumes the outputs have already been initialized; thus create the outputs first. This fixes a segfault upon startup. It is also what the drm and fbdev backends do. --- src/compositor-rpi.c | 19 --- 1 file changed, 8 ins