- 11 9月, 2006 1 次提交
-
-
由 Helge Deller 提交于
Signed-off-by: NHelge Deller <deller@gmx.de> Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
-
- 02 4月, 2006 1 次提交
-
-
由 Richard Thrippleton 提交于
Toshiba Protege M300 also requires the same workaround as Satellites and Dynabooks - Synaptics report rate should be lowered to 40pps (from 80), otherwise KBC starts losing keypresses. Signed-off-by: NRichard Thrippleton <ret28@cam.ac.uk> Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
-
- 14 3月, 2006 1 次提交
-
-
由 Eric Sesterhenn 提交于
Signed-off-by: NEric Sesterhenn <snakebyte@gmx.de> Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
-
- 14 1月, 2006 1 次提交
-
-
由 Dmitry Torokhov 提交于
This should help driver to deal vith KVMs that reset mice when switching between boxes. Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
-
- 29 10月, 2005 1 次提交
-
-
由 Dmitry Torokhov 提交于
Input: convert drivers/input/mouse to dynamic input_dev allocation This is required for input_dev sysfs integration Signed-off-by: NDmitry Torokhov <dtor@mail.ru> Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
-
- 24 7月, 2005 1 次提交
-
-
由 Sergey Vlasov 提交于
Synaptics driver used child->type to select either 3-byte or 4-byte packet size for the pass-through port; this gives wrong results for the newer protocols. Change the check to use child->pktsize instead. Signed-off-by: NSergey Vlasov <vsu@altlinux.ru> Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
-
- 11 7月, 2005 1 次提交
-
-
由 Simon Horman 提交于
Toshiba Dynabooks require the same workaround as Satellites - Synaptics report rate should be lowered to 40pps (from 80), otherwise KBC starts losing keypresses. Signed-off-by: NSimon Horman <horms@valinux.co.jp> Signed-off-by: NVojtech Pavlik <vojtech@suse.cz> Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
-
- 28 5月, 2005 1 次提交
-
-
由 Dmitry Torokhov 提交于
is no reason one driver should take 10 lines in dmesg. Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
-
- 17 4月, 2005 1 次提交
-
-
由 Linus Torvalds 提交于
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
-