On Thu, Jan 8, 2015 at 9:58 PM, Gavin Lambert wrote:
> On 9 January 2015 13:08, quoth Benjamin Tissoires:
>> You can also make an udev rule which write 1040 in
>> /sys/bus/hid/devices/0003\:0EEF\:0001.*/quirks on plug in an udev rule (you
>> should probably rely on the path given by the udev rule
On 9 January 2015 13:08, quoth Benjamin Tissoires:
> You can also make an udev rule which write 1040 in
> /sys/bus/hid/devices/0003\:0EEF\:0001.*/quirks on plug in an udev rule (you
> should probably rely on the path given by the udev rule instead of writing
> the wildcard).
I get a "permission de
On Thu, Jan 8, 2015 at 6:19 PM, Gavin Lambert wrote:
> On 9 January 2015 11:55, quoth Benjamin Tissoires:
>> On Thu, Jan 8, 2015 at 5:20 PM, Gavin Lambert wrote:
>> > On 9 January 2015 04:17, you quoth:
>> >> So here, everything seems fine except for the tracking ID and the
>> BTN_TOUCH.
>> >> Th
On 9 January 2015 11:55, quoth Benjamin Tissoires:
> On Thu, Jan 8, 2015 at 5:20 PM, Gavin Lambert wrote:
> > On 9 January 2015 04:17, you quoth:
> >> So here, everything seems fine except for the tracking ID and the
> BTN_TOUCH.
> >> The kernel does not sends the touch begin and touch end informa
Hi,
On Thu, Jan 8, 2015 at 5:20 PM, Gavin Lambert wrote:
> On 9 January 2015 04:17, you quoth:
>> So here, everything seems fine except for the tracking ID and the BTN_TOUCH.
>> The kernel does not sends the touch begin and touch end information, thus the
>> device is not working :(
>>
>> Can yo
On Wed, Jan 7, 2015 at 10:40 PM, Gavin Lambert wrote:
> Hi,
>
> I have a new eGalax touchscreen (came with driver cd 5.1.0, if that helps).
> I'm trying to use it from a Raspberry Pi, so I can't use the prebuilt drivers
> on that CD. I've found the ARM-specific vendor drivers but I haven't
>
