Re: [BUG] New Kernel Bugs
On 11/13/2007 04:12 PM, Alan Cox wrote: Bug fixing is not about finding someone to blame, it's about getting the bug fixed. Partly - its also about understanding why the bug occurred and making it not happen again. Very few people think about that part.
Re: Fix sudden warps in mousedev
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 who don't use mousedev multiplexor can use evtest and other commands. What should people be using instead of /dev/input/mice ? And why did the mouse numbers all get rearranged in 2.6.20, e.g. mouse1 became mouse2 for many people?
Re: Fix sudden warps in mousedev
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 should they be using some other configuration? People using this now have X crashes on kernel upgrade because event1 became event2: Driver evdev Option Device /dev/input/event1
