Mailinglist Archive: opensuse-bugs (9716 mails)
| < Previous | Next > |
[Bug 337822] Different mouse name for the same Vendor/Prodcut ID
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Thu, 1 Nov 2007 08:32:37 -0600 (MDT)
- Message-id: <20071101143237.9FD00245269@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=337822#c8
Stefan Dirsch <sndirsch@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|
|ms@xxxxxxxxxx
--- Comment #8 from Stefan Dirsch <sndirsch@xxxxxxxxxx> 2007-11-01 08:32:36
MST ---
Besides Name, Vendor and InputFashion - all these are meta informations, from
which Name/Vendor have a special meaning for the evdev driver :-( - SaX2 uses
the following options for the evdev driver.
- Buttons
- Protocol
- SendCoreEvents
- ZAxisMapping
But all these options are only available for the mouse driver and not the evdev
driver. Therefore I suggest to simply use the generic evdev mouse driver
configuration after fixing the Name/Vendor issue.
# And the following for all mice
Section "InputDevice"
Identifier "mouse"
Driver "evdev"
Option "evBits" "+1-2"
Option "keyBits" "~272-287"
Option "relBits" "~0-2 ~6 ~8"
Option "Pass" "3"
EndSection
Marcus, what do you think about my proposal to rename the meta SaX2 options
Name and Vendor to SaXName and SaXVendor in comment #1?
Otherwise we need to rename them in the evdev driver, which would make
our evdev driver incompatible to the upstream one. :-(
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Stefan Dirsch <sndirsch@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|
|ms@xxxxxxxxxx
--- Comment #8 from Stefan Dirsch <sndirsch@xxxxxxxxxx> 2007-11-01 08:32:36
MST ---
Besides Name, Vendor and InputFashion - all these are meta informations, from
which Name/Vendor have a special meaning for the evdev driver :-( - SaX2 uses
the following options for the evdev driver.
- Buttons
- Protocol
- SendCoreEvents
- ZAxisMapping
But all these options are only available for the mouse driver and not the evdev
driver. Therefore I suggest to simply use the generic evdev mouse driver
configuration after fixing the Name/Vendor issue.
# And the following for all mice
Section "InputDevice"
Identifier "mouse"
Driver "evdev"
Option "evBits" "+1-2"
Option "keyBits" "~272-287"
Option "relBits" "~0-2 ~6 ~8"
Option "Pass" "3"
EndSection
Marcus, what do you think about my proposal to rename the meta SaX2 options
Name and Vendor to SaXName and SaXVendor in comment #1?
Otherwise we need to rename them in the evdev driver, which would make
our evdev driver incompatible to the upstream one. :-(
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |