Emilio, All,
On 2014-02-03 16:57 +0100, poch...@gmail.com spake thusly:
From: Emilio Pozuelo Monfort emilio.pozu...@collabora.co.uk
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
On Mon, Feb 03, 2014 at 04:57:27PM +0100, poch...@gmail.com wrote:
From: Emilio Pozuelo Monfort emilio.pozu...@collabora.co.uk
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
Emilio, All,
On 2014-02-03 16:57 +0100, poch...@gmail.com spake thusly:
From: Emilio Pozuelo Monfort emilio.pozu...@collabora.co.uk
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
On Mon, 3 Feb 2014 16:57:27 +0100
poch...@gmail.com wrote:
From: Emilio Pozuelo Monfort emilio.pozu...@collabora.co.uk
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
From: Emilio Pozuelo Monfort emilio.pozu...@collabora.co.uk
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
On Mon, 3 Feb 2014 16:57:27 +0100
poch...@gmail.com wrote:
From: Emilio Pozuelo Monfort emilio.pozu...@collabora.co.uk
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
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 emilio.pozu...@collabora.co.uk
The input initialization code assumes the outputs have already
been initialized; thus create the outputs first. This fixes a
