On Mon, 26 Mar 2007, Dmitry Torokhov wrote:
On Monday 26 March 2007 17:42, Pete Zaitcev wrote:
I don't think that you need to concern yourself with this too much
at present. If X11 people (e.g. Kristian) present evidence that kernel
fails to deliver an event, then we'll look at it. However it
On Mon, 26 Mar 2007, Dmitry Torokhov wrote:
On Monday 26 March 2007 17:42, Pete Zaitcev wrote:
I don't think that you need to concern yourself with this too much
at present. If X11 people (e.g. Kristian) present evidence that kernel
fails to deliver an event, then we'll look at it. However it
Dmitry Torokhov wrote:
On 3/27/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
Dmitry Torokhov wrote:
>>
>> And why did the mouse numbers all get rearranged in 2.6.20, e.g.
>> mouse1 became mouse2 for many people?
>
> Input devices are not guaranteed to be stable.
>
So people with z-axis mice need
Dmitry Torokhov wrote:
On 3/27/07, Chuck Ebbert [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
And why did the mouse numbers all get rearranged in 2.6.20, e.g.
mouse1 became mouse2 for many people?
Input devices are not guaranteed to be stable.
So people with z-axis mice need to redo
On 3/27/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
Dmitry Torokhov wrote:
>>
>> And why did the mouse numbers all get rearranged in 2.6.20, e.g.
>> mouse1 became mouse2 for many people?
>
> Input devices are not guaranteed to be stable.
>
So people with z-axis mice need to redo their X config
Dmitry Torokhov wrote:
>>
>> And why did the mouse numbers all get rearranged in 2.6.20, e.g.
>> mouse1 became mouse2 for many people?
>
> Input devices are not guaranteed to be stable.
>
So people with z-axis mice need to redo their X config for each
kernel release when the device numbers
On 3/27/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
Dmitry Torokhov wrote:
>
> The driver grabs tochpad with EVIOCGRAB ioctl to prevent input events
> from bveing delivered to X through /dev/input/mice which is still in
> whidespread use. That's why evtest does not work. We could as Peter
>
Dmitry Torokhov wrote:
>
> The driver grabs tochpad with EVIOCGRAB ioctl to prevent input events
> from bveing delivered to X through /dev/input/mice which is still in
> whidespread use. That's why evtest does not work. We could as Peter
> (CCed) to implement an option to turn off grabbing so
Dmitry Torokhov wrote:
The driver grabs tochpad with EVIOCGRAB ioctl to prevent input events
from bveing delivered to X through /dev/input/mice which is still in
whidespread use. That's why evtest does not work. We could as Peter
(CCed) to implement an option to turn off grabbing so users
On 3/27/07, Chuck Ebbert [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
The driver grabs tochpad with EVIOCGRAB ioctl to prevent input events
from bveing delivered to X through /dev/input/mice which is still in
whidespread use. That's why evtest does not work. We could as Peter
(CCed) to
Dmitry Torokhov wrote:
And why did the mouse numbers all get rearranged in 2.6.20, e.g.
mouse1 became mouse2 for many people?
Input devices are not guaranteed to be stable.
So people with z-axis mice need to redo their X config for each
kernel release when the device numbers change? Or
On 3/27/07, Chuck Ebbert [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
And why did the mouse numbers all get rearranged in 2.6.20, e.g.
mouse1 became mouse2 for many people?
Input devices are not guaranteed to be stable.
So people with z-axis mice need to redo their X config for each
On Monday 26 March 2007 17:42, Pete Zaitcev wrote:
> On Mon, 26 Mar 2007 15:30:42 -0400, "Dmitry Torokhov" <[EMAIL PROTECTED]>
> wrote:
>
> > Regarding the synaptics driver and scroll problem. Yesterday I
> > scrolled twice through entire Remarque's "Spark of Life" off lib.ru
> > (once with
On Mon, 26 Mar 2007 15:30:42 -0400, "Dmitry Torokhov" <[EMAIL PROTECTED]> wrote:
> Regarding the synaptics driver and scroll problem. Yesterday I
> scrolled twice through entire Remarque's "Spark of Life" off lib.ru
> (once with 0.14.2 and once with latest git pull) and did not see any
>
On 3/26/07, Pete Zaitcev <[EMAIL PROTECTED]> wrote:
On Sun, 25 Mar 2007 23:19:38 -0400, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> I tried to reproduce warping on console but could not for some reason. Could
you
> please try the patch below and tell me if it fixes the problem for you?
> +++
On Sun, 25 Mar 2007 23:19:38 -0400, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> I tried to reproduce warping on console but could not for some reason. Could
> you
> please try the patch below and tell me if it fixes the problem for you?
> +++ work/drivers/input/mousedev.c
> @@ -124,32 +124,33
On Sun, 25 Mar 2007 23:19:38 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
I tried to reproduce warping on console but could not for some reason. Could
you
please try the patch below and tell me if it fixes the problem for you?
+++ work/drivers/input/mousedev.c
@@ -124,32 +124,33 @@
On 3/26/07, Pete Zaitcev [EMAIL PROTECTED] wrote:
On Sun, 25 Mar 2007 23:19:38 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
I tried to reproduce warping on console but could not for some reason. Could
you
please try the patch below and tell me if it fixes the problem for you?
+++
On Mon, 26 Mar 2007 15:30:42 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
Regarding the synaptics driver and scroll problem. Yesterday I
scrolled twice through entire Remarque's Spark of Life off lib.ru
(once with 0.14.2 and once with latest git pull) and did not see any
scrollbar getting
On Monday 26 March 2007 17:42, Pete Zaitcev wrote:
On Mon, 26 Mar 2007 15:30:42 -0400, Dmitry Torokhov [EMAIL PROTECTED]
wrote:
Regarding the synaptics driver and scroll problem. Yesterday I
scrolled twice through entire Remarque's Spark of Life off lib.ru
(once with 0.14.2 and once
On Sunday 25 March 2007 14:19, Pete Zaitcev wrote:
> On Sun, 25 Mar 2007 01:34:02 -0400, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
>
> > > + * Without this, a touchpad may report an unchanged
> > > position,
> > > + * then a sync. The input_event() eats the
On Sun, 25 Mar 2007 01:34:02 -0400, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> > + * Without this, a touchpad may report an unchanged
> > position,
> > + * then a sync. The input_event() eats the position report,
> > but
> > + * lets the sync
On Sun, 25 Mar 2007 01:34:02 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
+ * Without this, a touchpad may report an unchanged
position,
+ * then a sync. The input_event() eats the position report,
but
+ * lets the sync through. We
On Sunday 25 March 2007 14:19, Pete Zaitcev wrote:
On Sun, 25 Mar 2007 01:34:02 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
+ * Without this, a touchpad may report an unchanged
position,
+ * then a sync. The input_event() eats the position
report,
Here's another one of those soon-to-be-obsoleted patches to mousedev.
But if it lives just in 2.6.21, it's good, right? It's a pure bugfix.
On my laptop with Synaptics, if I lift the finger and place it elsewhere,
the pointer sometimes warps dramatically. Here's the evtest trace
which illustrates
Here's another one of those soon-to-be-obsoleted patches to mousedev.
But if it lives just in 2.6.21, it's good, right? It's a pure bugfix.
On my laptop with Synaptics, if I lift the finger and place it elsewhere,
the pointer sometimes warps dramatically. Here's the evtest trace
which illustrates
26 matches
Mail list logo
