Date: Thu, 14 Feb 2008 05:06:48 +0100 From: Markus Brueffer <markus@FreeBSD.org> To: freebsd-usb@freebsd.org Subject: Re: getting my new graphic tablet cooperating with gimp Message-ID: <200802140506.52864.markus@FreeBSD.org> In-Reply-To: <47B328A9.7080808@chuckr.org> References: <47AE28EB.7070205@chuckr.org> <20080213180132.511a7fb4.torfinn.ingolfsen@broadpark.no> <47B328A9.7080808@chuckr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <kaiwang27@gmail.com> 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: <UC-LOGIC Tablet WP8060U, class 0/0, rev 1.10/0.00, addr 2> > >>> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200802140506.52864.markus>