From owner-freebsd-usb@FreeBSD.ORG Thu Feb 14 04:07:11 2008 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 3989716A418 for ; Thu, 14 Feb 2008 04:07:11 +0000 (UTC) (envelope-from markus@FreeBSD.org) Received: from mail-in-12.arcor-online.net (mail-in-12.arcor-online.net [151.189.21.52]) by mx1.freebsd.org (Postfix) with ESMTP id AE74013C45A for ; Thu, 14 Feb 2008 04:07:10 +0000 (UTC) (envelope-from markus@FreeBSD.org) Received: from mail-in-09-z2.arcor-online.net (mail-in-09-z2.arcor-online.net [151.189.8.21]) by mail-in-12.arcor-online.net (Postfix) with ESMTP id 641084C96D; Thu, 14 Feb 2008 05:07:09 +0100 (CET) Received: from mail-in-06.arcor-online.net (mail-in-06.arcor-online.net [151.189.21.46]) by mail-in-09-z2.arcor-online.net (Postfix) with ESMTP id 47A2828EDBE; Thu, 14 Feb 2008 05:07:09 +0100 (CET) Received: from galaxy.homeunix.org (dslb-084-061-046-087.pools.arcor-ip.net [84.61.46.87]) by mail-in-06.arcor-online.net (Postfix) with ESMTP id 1203A35E6A5; Thu, 14 Feb 2008 05:07:09 +0100 (CET) Received: from cheops.phoenix (cheops.phoenix [192.168.1.3]) by galaxy.homeunix.org (Postfix) with ESMTP id 548E43F456; Thu, 14 Feb 2008 05:04:21 +0100 (CET) From: Markus Brueffer To: freebsd-usb@freebsd.org Date: Thu, 14 Feb 2008 05:06:48 +0100 User-Agent: KMail/1.9.7 References: <47AE28EB.7070205@chuckr.org> <20080213180132.511a7fb4.torfinn.ingolfsen@broadpark.no> <47B328A9.7080808@chuckr.org> In-Reply-To: <47B328A9.7080808@chuckr.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1913414.gXjQVzJ3N8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200802140506.52864.markus@FreeBSD.org> X-Virus-Scanned: ClamAV 0.92.1/5805/Thu Feb 14 00:29:12 2008 on mail-in-06.arcor-online.net X-Virus-Status: Clean Cc: Subject: Re: getting my new graphic tablet cooperating with gimp 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: Thu, 14 Feb 2008 04:07:11 -0000 --nextPart1913414.gXjQVzJ3N8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Mittwoch, 13. Februar 2008 18:28:09 schrieb Chuck Robey: > Torfinn Ingolfsen wrote: > > On Sun, 10 Feb 2008 18:10:52 +0100 > > > > Kai Wang wrote: > >> On Sat, Feb 09, 2008 at 05:27:55PM -0500, Chuck Robey wrote: > >>> I have a nice new UC-Logic WP8060-TAB08, sometimes called the > >>> Superpen, and I want to get it working so's I can make fine art > >>> with it (yeah, I'm a dreamer, so what else is new, hey?) The > >>> return off of dmesg is: > >>> > >>> ums0: > >>> on uhub0 ums0: X report 0x0002 not supported > >>> device_attach: ums0 attach returned 6 > >> > >> This is because your tablet use absolute coordinates (most tablets do) > >> while ums(4) currently only support relative ones. > >> > >> Could you please try to dump your pen's report descriptor and paste it > >> here, thus we can have more infomation? > > I appreciate the extra information. In fact, I am having one heck of a > time trying to figure out exactly how to parse this. I am reading with t= he > HID1_11 spec on my knee at all times, but I swear, I have never seen such= a > poorly written document! It's not _that_ bad, but it surely lacks several clarifications in some are= as=20 and some information on specific topics is scattered across the whole=20 document. Best thing to get started is IMHO to get an idea about what reports are and= to=20 get the raw report descriptor of a simple device (e.g. a mouse if it's not= =20 from a keyboard/mouse combo) and start decoding it by hand. The sources of= =20 the libusbhid parser might be of help as well, although it contains several= =20 bugs and isn't spec compliant in several cases, but it might get you an ide= a=20 of what's going on. Furthermore playing with usbhidctl might be of help. I have written a completly new fully spec compliant HID parser which is soo= n=20 ready for public consumption as part of a new libhid. It contains many=20 comments and should be easy to understand. The data representation directly= =20 takes the tree-like structure of a decoded report descriptor into account s= o=20 that it's easy to write drivers that only handle one or more specific=20 application collections. Furthermore physical descriptors are supported and= =20 the data handling functions hide the concept of report IDs so that it's les= s=20 error prone to develop HID drivers (ums(4) e.g. doesn't support reports oth= er=20 than report 0 which is the reason that many of todays mice don't work). The= =20 parser itself will hopefully replace our current in-kernel HID parser. > I am having a terrible time trying to figure out=20 > the actual scope of each statement, which refers to what. I don't run any > piece of Windows stuff here, so many of the pieces of demo software I have > found on the web do me no good. I didn't find any windows software that really made it easier to understand= =20 the spec. It's IMHO easier to directly get your hands dirty and to read the= =20 code of an HID parser. > I'm not giving up, I keep on making new discoveries, but if anyone knows = of > a description of HID that involves some real use of English, I sure would > appreciate a pointer to it. If you have any specific questions, please drop me a mail. Markus --nextPart1913414.gXjQVzJ3N8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD4DBQBHs75c1I0Qcnj4qNQRAk54AJiU6OlMsYPOlH08wbeXURpLDCikAKCrOQt1 Aj2rhRlwyNLpJLJtbThl+g== =i5uM -----END PGP SIGNATURE----- --nextPart1913414.gXjQVzJ3N8--