Re: driving 2 displays

On 28.08.2012 08:58, Usagi Yojimbo wrote:
>>> So you need a meta driver that look like one display for the core code but reuse two different driver to control the physical lcd?
>>> Or should that be know by the core without a virtual driver in between?
> Hi,
>
> I think the meta/virtual driver should be the best solution.
> If it is configurable, one can drive 2 different HW's, like I would do.
>
>
> Usagi
>

Hi,

I am not convinced that a meta driver is a good solution. While it is
simple to write a driver, I see two reasons not to use a driver for this:

First, it needs to duplicate much of the driver loading code that is
present in LCDd core. Second it only handles the screen coordinates ->
display driver mapping. All other functions have to be implemented, but
will be pass-through only.

As the core already can load multiple driver (like you are using), I
believe teaching the core about a virtual display that may consist of
several physical ones fits better into the currrent design.

This functionality will have to be developed for both solutions, but
when implemented in the core you don't have to mess around with driver
loading and functions not related to drawing.

Regards,
Markus