How to setup independent screens with the Intel driver?

[Boszormenyi Zoltan]

2015-10-30 20:08 keltezéssel, Chris Wilson írta:
> On Fri, Oct 30, 2015 at 08:00:46PM +0100, Boszormenyi Zoltan wrote:
>> 2015-10-30 19:15 keltezéssel, Chris Wilson írta:
>>> On Fri, Oct 30, 2015 at 06:17:50PM +0100, Boszormenyi Zoltan wrote:
>>>> In my case with this particular POS machine, the intended primary display,
>>>> the built-in LVDS with a touchscreen attached is apparently wired to pipe 1.
>>>>
>>>> With this driver behaviour, I can't configure it to be kept as the default :0.0 screen
>>>> if an external display is plugged in. Can this behaviour be changed?
>>> It would need another user parameter. There are several technical
>>> limitations that make automatic assignment difficult. So try
>>>
>>> commit 94d271b239d358f71ae0bcfcc31422a569d73d41
>>> Author: Chris Wilson <chris at chris-wilson.co.uk>
>>> Date:   Fri Oct 30 18:07:37 2015 +0000
>>>
>>>     sna: Allow pipes to be manually assigned to ZaphodHead
>>> -Chris
>> Thanks for your work, I just tested it. At startup, it seems to work:
>> 1. it doesn't complain about invalid pipe
>> 2. cursor appears on :0
>> 3. application appears on :0
>>
>> Then as soon as I touch the touchscreen, the cursor jumps to :1 and
>> further cursor movements are on :1 from that point.
> I'm baffled. xinput fun? cursors in the driver are allocated per-CRTC
> and handled at a screen level. As far as I am aware, the driver only
> has to position a cursor at a certain coordinate on the framebuffer (and
> so has to translate that into a CRTC location).

BTW, this is the touchscreen driver in question:
https://github.com/SICOM/xf86-input-eeti-egalax

It doesn't have anything directly screen related, I used xf86-input-void
as the driver skeleton.

>  
>> Attached is my current configuration, hopefully I got it right.
> Looks fine to me.
> -Chris
>