On Sun, Mar 15, 2009 at 6:05 PM, Peter Hutterer
wrote:
> On Fri, Mar 13, 2009 at 06:21:04AM -0500, David Hagood wrote:
>> On Fri, 2009-03-13 at 11:43 +1000, Peter Hutterer wrote:
>> > On Thu, Mar 12, 2009 at 01:40:29PM -0400, Chris Ball wrote:
>>
>> > I agree. getting something sensible in the ker
On Mon, Mar 16, 2009 at 06:28:40AM -0500, David Hagood wrote:
> On Mon, 2009-03-16 at 11:05 +1000, Peter Hutterer wrote:
> > that's probably because they advertise a button/axis combination that evdev
> > does interpret correctly, or because they're posting the axis information
> > wrongly. I had m
On Mon, 2009-03-16 at 11:05 +1000, Peter Hutterer wrote:
> that's probably because they advertise a button/axis combination that evdev
> does interpret correctly, or because they're posting the axis information
> wrongly. I had my hands on an HP Touchsmart for a short while and it was
> posting x/y
On Fri, Mar 13, 2009 at 06:21:04AM -0500, David Hagood wrote:
> On Fri, 2009-03-13 at 11:43 +1000, Peter Hutterer wrote:
> > On Thu, Mar 12, 2009 at 01:40:29PM -0400, Chris Ball wrote:
>
> > I agree. getting something sensible in the kernel prevents us from
> > replicating
> > the "one X driver p
On Fri, 2009-03-13 at 11:43 +1000, Peter Hutterer wrote:
> On Thu, Mar 12, 2009 at 01:40:29PM -0400, Chris Ball wrote:
> I agree. getting something sensible in the kernel prevents us from replicating
> the "one X driver per device" hilarity.
> Once we have that support in the kernel, we can look a
On Thu, Mar 12, 2009 at 01:40:29PM -0400, Chris Ball wrote:
> Hi David,
>
>> Does anybody have a good suggestion as to where this support should
>> go?
>
> My intuition is that adding the reporting to the kernel and hooking it
> up through the standard evdev driver would be the right way
> That's odd; perhaps they didn't get the right HAL properties added.
> The N-Trig (multi) touchscreen on the Dell Latitude XT and HP Touchsmart
> TX2 works out of the box for touch with evdev GIT HEAD. (Clicking via
> screen taps requires a patch to map BTN_TOUCH to BTN_LEFT, though.)
>
> - Chri
Hi,
> Interesting, because the touchpanels I've used were NOT recognized
> by evdev at all - attempting to use them with the evdev driver
> resulted in no input at all to the X server.
That's odd; perhaps they didn't get the right HAL properties added.
The N-Trig (multi) touchscreen on t
> Hi David,
>
> My intuition is that adding the reporting to the kernel and hooking it
> up through the standard evdev driver would be the right way to go; evdev
> already has single-touch support working fairly well.
Interesting, because the touchpanels I've used were NOT recognized by
evdev at a
Hi David,
> Does anybody have a good suggestion as to where this support should
> go?
My intuition is that adding the reporting to the kernel and hooking it
up through the standard evdev driver would be the right way to go; evdev
already has single-touch support working fairly well. I don'
I am working with a (somewhat new-ish) touchscreen system which supports
Multi-touch reporting, based upon an eGalix controller. Unfortunately,
this is NOT currently supported under Linux (when will these vendors wake
up to the fact that the embedded world is moving away from Windows(tm)?)
I don't
11 matches
Mail list logo
