[PATCH] Evdev input on Xglx

[Tiago Vignatti]

Hi, Guys (specially Zephaniah). I need your opinion before start my work 
on this.

What do you think about create something like the x-input-evdev that
Davidr said? My goal is Xgl and for the first reference, I think I can
use the xf86-input-evdev functions related to those who Xgl use and thus
I can build the x-input-evdev. This isn'ta hard work, I think.

I'll appreciate any help and thanks in advance!

T Vignatti


David Reveman escreveu:
> On Wed, 2006-05-31 at 15:27 -0300, Tiago Vignatti wrote: 
>> Zephaniah E. Hull wrote:
>>> On Fri, Apr 14, 2006 at 11:17:02AM +0200, David Reveman wrote:
>>>> On Tue, 2006-04-11 at 15:33 -0300, Tiago Vignatti wrote: 
>>>>> This one adds the evdev input on Xglx. I don't know if it is a "feature
>>>>> bloat", but it really helps to make nested multiseat systems with 3D and xv 
>>>>> support.
>>>> I think it's useful. However, I'd like to move the evdev input code into
>>>> hw/xgl/xglinput.c so that both xglx and xegl can use it.
>>> I'd really consider it a lot more useful to take a look and see what it
>>> would take to shoehorn support for xf86-input-evdev into xgl, however I
>>> have not really played with xgl enough to know how big of a job this
>>> would really be.
>>>
>>> (Obviously, without the hw/xfree86/common/XF86Input stuff it won't
>>> exactly be trivial, however given that the whole of input handling is
>>> going to get some changes, and that kdrive would like evdev support as
>>> well, putting some extra effort into things sometime here would make
>>> sense.
>>>
>>> In that case, it would really be nice if we could figure out something
>>> which won't break configs some more when things finally get shifted
>>> around.)
>>>
>>> Zephaniah E. Hull.
>> Hi David.
>>
>> Let me take this issue back. You said that you want to move the evdev 
>> input code into hw/xgl/xglinput.c, thus xglx and xegl can use it. Right? 
> 
> Right.
> 
>> Ok, but what is the nice choose: (1) build a brand new xgl evdev input, 
>> like dmx or kdrive did, or (2) use the xf86-input-evdev driver, as 
>> Zephaniah said?
> 
> I haven't looked at the evdev input code yet but using xf86-input-evdev
> driver sounds like a good idea. However, I guess it will require that a
> lot of xfree86 ddx stuff is removed from xf86-input-evdev, making it
> x-input-evdev with a xfree86 backend or something like that.
> 
> I'm fine with including some brand new xgl evdev input code in
> xglinput.c for now if using xf86-input-evdev is too far away.
> 
> Help with getting any of this work done is greatly appreciated.
> 
> Thanks,
> 
> -David


-- 
Tiago Vignatti
C3SL - Centro de Computação Científica e Software Livre
www.c3sl.ufpr.br