Re: [PATCH 5/5] Move the optional output name property from drm_output to weston_output

2013-05-02 Thread Richard Hughes
On 2 May 2013 13:49, Kai-Uwe Behrmann wrote: > Why will come a need for a CMS to read hardcoded names from the config file? Well, colord won't, but not everybody wants/needs colord, e.g. on an embedded display where a color profile is never likely to change. For this case I've added a cms-static

Re: [PATCH 5/5] Move the optional output name property from drm_output to weston_output

2013-05-02 Thread Kai-Uwe Behrmann
Am 02.05.13, 10:10 +0100 schrieb Richard Hughes: In the future the CMS plugins will need to read the config file and setup a list of hardcoded names to ICC profiles. Why will come a need for a CMS to read hardcoded names from the config file? kind regards Kai-Uwe ___

[PATCH 5/5] Move the optional output name property from drm_output to weston_output

2013-05-02 Thread Richard Hughes
In the future the CMS plugins will need to read the config file and setup a list of hardcoded names to ICC profiles. --- src/compositor-drm.c | 11 --- src/compositor.c | 1 + src/compositor.h | 1 + 3 files changed, 6 insertions(+), 7 deletions(-) diff --git a/src/compositor-dr