From owner-freebsd-usb@FreeBSD.ORG Sun Oct 23 15:34:14 2005 Return-Path: X-Original-To: freebsd-usb@freebsd.org Delivered-To: freebsd-usb@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 304D316A41F for ; Sun, 23 Oct 2005 15:34:14 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.198.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6B4F43D45 for ; Sun, 23 Oct 2005 15:34:13 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from fw.home (pcp05405355pcs.norstn01.pa.comcast.net[68.81.66.212]) by comcast.net (rwcrmhc12) with SMTP id <20051023153412014006o9c5e>; Sun, 23 Oct 2005 15:34:12 +0000 Received: (qmail 22700 invoked from network); 23 Oct 2005 15:34:11 -0000 Received: from kris.home (e7a8a86c99019924e5f404ddea135e7c@192.168.0.251) by fw.home with SMTP; 23 Oct 2005 15:34:11 -0000 Received: (qmail 74447 invoked by uid 1000); 23 Oct 2005 15:34:10 -0000 Date: Sun, 23 Oct 2005 11:34:10 -0400 From: Kris Maglione To: "Loren M. Lang" Message-ID: <20051023153314.GA54912@kris.home> Mail-Followup-To: "Loren M. Lang" , freebsd-usb@freebsd.org References: <20051021230147.GA40893@kris.home> <20051023053600.GA18930@alzatex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20051023053600.GA18930@alzatex.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-usb@freebsd.org Subject: Re: USB mouse, wheel doesn't work X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2005 15:34:14 -0000 On Sat, Oct 22, 2005 at 10:36:00PM -0700, Loren M. Lang wrote: >Can you post the HID report descriptor for that device? All the >information about the wheel should be described in there. I have a >crude program to do that if you need. This is the debug info that attach spits out. It's based on the HID descriptor: ums_attach: sc=0xc1ca8400 ums_attach: X 8/8 ums_attach: Y 16/8 ums_attach: Z 24/8 ums_attach: B1 0/1 ums_attach: B2 1/1 ums_attach: B3 2/1 ums_attach: B4 3/1 ums_attach: B5 4/1 ums_attach: B6 32/1 ums_attach: B7 33/1 ums_attach: size=15, id=0 Read as / Here's what usbhidctl shows: # usbhidctl -f /dev/uhid0 -r Report descriptor: Total input size 0 bytes Total output size 5 bytes Total feature size 2 bytes I also tried another experiment; a basic perl script with /dev/uhid0 as STDIN: for (1..150) { my $data; sysread STDIN, $data, 150; # The max length it will read is 15 my @data = split //, $data; @data = map { ord } @data; printf "%02x %02x %02x %02x %02x -- " splice @data, 0, 5 for (1..3); print "\n"; } I got the same results as before: only the first three bytes ever changed, the rest were filled with the same junk from the malloc. -- Kris Maglione You may know where the market is going, but you can't possibly know where it's going after that.