From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 21 17:56:46 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F39DC16A41F for ; Fri, 21 Oct 2005 17:56:45 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D37843D46 for ; Fri, 21 Oct 2005 17:56:45 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from fw.home (pcp05405355pcs.norstn01.pa.comcast.net[68.81.66.212]) by comcast.net (rwcrmhc11) with SMTP id <2005102117564401300fspthe>; Fri, 21 Oct 2005 17:56:44 +0000 Received: (qmail 84094 invoked from network); 21 Oct 2005 17:56:43 -0000 Received: from kris.home (2d30ffc1ee241b6ab4b50c9e48679bcd@192.168.0.251) by fw.home with SMTP; 21 Oct 2005 17:56:43 -0000 Received: (qmail 75339 invoked by uid 1000); 21 Oct 2005 17:56:43 -0000 Date: Fri, 21 Oct 2005 13:56:42 -0400 From: Kris Maglione To: freebsd-hackers@freebsd.org Message-ID: <20051021175642.GA74774@kris.home> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: USB mouse, wheel doesn't work X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2005 17:56:46 -0000 I have a gyration mouse. At first, it didn't work, but I got it working by setting sc->sc_iid to 0 in USB_ATTACH in ums.c. The only problem that I have now is that the wheel doesn't work. The wheel is supposed to be reported in the 4th byte of sc_ibuf. The problem is that nothing after the third byte is touched. In fact, I had to zero the entire buffer after the malloc, so some junk value didn't cause a persistent Z axis value. When I turn the wheel, I get a bunch of events, but with no data... the first three bytes are set to 0, and the rest are either junk (if I haven't zerod after the malloc), or null (if I have). I don't know enough about the USB subsystem to go chasing after this myself, but I would assume that the problem is outside of the ums driver. Can someone point me in the right direction here? If it helps, the device is a combination keyboard/mouse reciever. Thanks -- Kris Maglione No matter what happens, there is always somebody who knew that it would.