From owner-freebsd-usb@FreeBSD.ORG Thu Dec 17 13:05:09 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E01E01065672 for ; Thu, 17 Dec 2009 13:05:09 +0000 (UTC) (envelope-from me@jackal.in) Received: from mail.doorsense.net (server.doorsense.net [89.108.95.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6A1A88FC16 for ; Thu, 17 Dec 2009 13:05:09 +0000 (UTC) Received: from [81.27.59.54] (helo=dell.jackal.in) by mail.doorsense.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1NLG2T-000M2g-Q5; Thu, 17 Dec 2009 16:05:07 +0300 From: jackal To: Hans Petter Selasky , freebsd-usb@freebsd.org Date: Thu, 17 Dec 2009 16:04:30 +0300 User-Agent: KMail/1.12.3 (FreeBSD/8.0-STABLE; KDE/4.3.3; i386; ; ) References: <200912161556.52923.me@jackal.in> <200912171432.20725.me@jackal.in> <200912171343.22970.hselasky@c2i.net> In-Reply-To: <200912171343.22970.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912171604.30794.me@jackal.in> X-Spam-Score: -4.8 (----) X-Spam-Status: No, score=-4.8 required=5.0 autolearn=no SpamAssassin 3.2.5 (2008-06-10) on mail.desalvia.com Content analysis details: (-4.8 points, 5.0 required) pts rule name description --- ---------------------- --------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.2 SUBJECT_FUZZY_TION Attempt to obfuscate words in Subject: -3.2 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Cc: Subject: Re: logitech vx nano mouse buttons X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: me@jackal.in List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 13:05:10 -0000 Hello, On Thursday 17 December 2009 15:43:21 Hans Petter Selasky wrote: > On Thursday 17 December 2009 12:32:19 jackal wrote: > > Hello, > > > > On Thursday 17 December 2009 01:38:09 Hans Petter Selasky wrote: > > > On Wednesday 16 December 2009 21:50:09 jackal wrote: > > > > Hello, > > > > > > > > On Wednesday 16 December 2009 22:44:41 Paul Schmehl wrote: > > > > > --On Wednesday, December 16, 2009 11:44:21 -0600 Hans Petter > > > > > Selasky > > > > > > > > > > wrote: > > > > > > On Wednesday 16 December 2009 13:56:52 jackal wrote: > > > > > >> Hello, > > > > > >> > > > > > >> I'm using logitech vx nano mouse at freebsd 8-stable. > > > > > >> Everything works fine, except wheel left/right buttons. > > > > > >> `cat /dev/ums0' doesn't show anything when pressing this > > > > > >> buttons. Any other buttons works fine, including navigation > > > > > >> buttons. Is there a way to get this buttons work? > > > > > > > > > > Have you googled for the answer? > > > > > > > > > > http://wiki.eeeuser.com/configure_logitech_vx_nano > > > > > > > > > > http://bbs.archlinux.org/viewtopic.php?id=41805 > > > > > > > > > > http://crunchbanglinux.org/forums/topic/504/solved-help-setting-up- > > > > >si de -w he el-buttons/ > > > > > > > > > > Section "InputDevice" > > > > > Identifier "VX Nano" > > > > > Driver "evdev" > > > > > Option "Name" "Logitech USB Receiver" > > > > > Option "Protocol" "evdev" > > > > > Option "Buttons" "9" > > > > > Option "SendCoreEvents" > > > > > Option "ZAxisMapping" "4 5" > > > > > Option "WAxisMapping" "8 9" > > > > > EndSection > > > > > > > > > > Obviously the driver will be different on FreeBSD, but the > > > > > WAxisMapping is the one that controls the side buttons. > > > > > > > > Ofcourse, I googled it, and I tried this configuration. But > > > > ..AxisMapping is just button-to-axis mapping. xev doesn't see this > > > > buttons. > > > > Any Xorg driver should work with ums0 device (as I understand), so I > > > > tried to `cat /dev/ums0' without X server and moused. > > > > > > Can you enable ums debugging: > > > > > > sysctl hw.usb.ums.debug=15 > > > > ####### left button press > > Dec 17 12:46:16 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:16 dell kernel: ums_intr_callback:228: data = 01 00 > > 00 00 00 00 00 00 Dec 17 12:46:16 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:0 t:0 w:0 buttons:0x00000004 > > > > ####### left button release > > Dec 17 12:46:16 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:16 dell kernel: ums_intr_callback:228: data = 00 00 > > 00 00 00 00 00 00 Dec 17 12:46:16 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:0 t:0 w:0 buttons:0x00000000 > > > > ####### backward button press > > Dec 17 12:46:18 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:18 dell kernel: ums_intr_callback:228: data = 08 00 > > 00 00 00 00 00 00 Dec 17 12:46:18 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:0 t:0 w:0 buttons:0x00000008 > > > > ####### backward button release > > Dec 17 12:46:18 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:18 dell kernel: ums_intr_callback:228: data = 00 00 > > 00 00 00 00 00 00 Dec 17 12:46:18 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:0 t:0 w:0 buttons:0x00000000 > > > > ####### forward button press > > Dec 17 12:46:19 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:19 dell kernel: ums_intr_callback:228: data = 10 00 > > 00 00 00 00 00 00 Dec 17 12:46:19 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:0 t:0 w:0 buttons:0x00000010 > > > > ####### forward button release > > Dec 17 12:46:19 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:19 dell kernel: ums_intr_callback:228: data = 00 00 > > 00 00 00 00 00 00 Dec 17 12:46:19 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:0 t:0 w:0 buttons:0x00000000 > > > > ####### wheel up > > Dec 17 14:21:07 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 14:21:07 dell kernel: ums_intr_callback:228: data = 00 00 > > 00 00 00 00 01 00 Dec 17 14:21:07 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:-1 t:0 w:0 buttons:0x00000000 > > > > ####### wheel down > > Dec 17 14:21:11 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 14:21:11 dell kernel: ums_intr_callback:228: data = 00 00 > > 00 00 00 00 ff 00 Dec 17 14:21:11 dell kernel: ums_intr_callback:294: x:0 > > y:0 z:1 t:0 w:0 buttons:0x00000000 > > > > ####### wheel left > > Dec 17 12:46:20 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:20 dell kernel: ums_intr_callback:228: data = 00 00 > > 00 00 00 00 00 ff > > > > ####### wheel right > > Dec 17 12:46:22 dell kernel: ums_intr_callback:210: sc=0xc61dc800 > > actlen=8 Dec 17 12:46:22 dell kernel: ums_intr_callback:228: data = 00 00 > > 00 00 00 00 00 01 > > > > Wheel left/right buttons doesn't have 'release' events. Seems like it's > > fourth axis... When holding one of this buttons, an event is generated > > continuously. > > If you do log2 of the buttons value you get the button # pressed. Looks > like the mapping is not 1:1. Try to add a button map to the X11 config > file. > Yes, backward/forward button mapping is not 1:1. These buttons works with Option "ButtonMapping" "1 2 3 6 7" as expected. But the problem is with 'wheel left/right' buttons. These buttons doesn't generate button events, so xev can't see these buttons. Dec 17 12:46:20 dell kernel: ums_intr_callback:210: sc=0xc61dc800 actlen=8 Dec 17 12:46:20 dell kernel: ums_intr_callback:228: data = 00 00 00 00 00 00 00 ff Dec 17 12:46:22 dell kernel: ums_intr_callback:210: sc=0xc61dc800 actlen=8 Dec 17 12:46:22 dell kernel: ums_intr_callback:228: data = 00 00 00 00 00 00 00 01 There's no ums_intr_callback:294 events. What you mean by phrase 'do log2 of the buttons value'? What is the 'log2'? -- Kind regards, Eugeny.