On Sat, Oct 12, 2019 at 03:19:52AM +, Software Orchestration wrote:
> On Friday, October 11, 2019, 7:38:57 PM PDT, Peter Hutterer
> wrote:
> > if your device has a /dev/input/eventX node anyway, then yes, evdev is
> > the way to go. You may not need any modification at all, evdev may do
On Friday, October 11, 2019, 7:38:57 PM PDT, Peter Hutterer
wrote:
> if your device has a /dev/input/eventX node anyway, then yes, evdev is
> the way to go. You may not need any modification at all, evdev may do
> the trick.
I think I'm starting to understand how all of this starts up, the
On 12/10/19 10:43 , Software Orchestration wrote:
On Friday, October 11, 2019, 3:33:52 PM PDT, Peter Hutterer
wrote:
the headers may have shuffled things around a bit - without knowing your
source code I can't really comment on what has changed for you. but I
don't expect there to be anythin
On Friday, October 11, 2019, 3:33:52 PM PDT, Peter Hutterer
wrote:
> the headers may have shuffled things around a bit - without knowing your
> source code I can't really comment on what has changed for you. but I
> don't expect there to be anything that's not resolved by including some
> st
On 11/10/19 20:29 , Software Orchestration wrote:
On Thursday, October 10, 2019, 9:35:47 PM PDT, Peter Hutterer
wrote: > I'd argue that any input driver that worked
in the past should still work
with current X servers, provided that you switch the SIGIO bits over to
handle input threads i
On Thursday, October 10, 2019, 9:35:57 PM PDT, Peter Hutterer
wrote:
> provided that you switch the SIGIO bits over to handle input threads instead.
I saw this page on the Xorg site:
https://www.x.org/wiki/Development/Documentation/XorgInputHOWTO/
But if I'm not mistaken, from what Peter was
On Thursday, October 10, 2019, 9:35:47 PM PDT, Peter Hutterer
wrote:
> provided that you switch the SIGIO bits over to handle input threads instead.
I see the eventcomm.c file in the synaptics driver:
https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics/blob/master/src/eventcomm.c
On Thursday, October 10, 2019, 9:35:47 PM PDT, Peter Hutterer
wrote: > I'd argue that any input driver that worked
in the past should still work
> with current X servers, provided that you switch the SIGIO bits over to
> handle input threads instead.
>
> There are very few features that have
On Thu, Oct 10, 2019 at 02:27:36AM +, Software Orchestration wrote:
>
> Alan Coopersmith wrote: > I have no idea who
> decided what releases to list there as supported, but X.Org
> > certainly isn't supporting all those releases upstream - though some
> > downstream
> > distros may be doi
> I think I could get 1.20 on Ubuntu 19.08, do you know if that's the case?
I should add, the client doesn't want to got to a non-LTS distribution. Doesn't
sound like there's any compelling reason to go there, and hopefully the same
code would run on 1.20 when the time comes._
Alan Coopersmith wrote: > I have no idea who
decided what releases to list there as supported, but X.Org
> certainly isn't supporting all those releases upstream - though some
> downstream
> distros may be doing so. X.Org itself is mainly maintaining the 1.20 series
> now:
> https://gitlab.f
On 10/9/19 6:05 PM, Software Orchestration wrote:
Hi, I have a client that has a working serial input driver on Ubuntu 14.04,
which is running the Xorg 1.15.1 server.
I'm tasked with getting this to work on Ubuntu 18.04 which is running Xorg
1.19.6
In looking at the X.Org Server wiki page:
h
12 matches
Mail list logo