Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 09 Feb 2008 14:21:16 -0500
From:      Chuck Robey <chuckr@chuckr.org>
To:        FreeBSD-Hackers <freebsd-hackers@freebsd.org>
Subject:   USB Graphic Tablets
Message-ID:  <47ADFD2C.80009@chuckr.org>

next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just laid hands on a UC-Logic WP8060-TAB08 Graphic tablet, so as to make
my work in gimp easier  I got this one instead of a Wacom unit for the
single obvious reason: $$.  It seems to have all the features of the big
boys, it's 8" by 6", 1024 intensity levels, chrome bumpers, dual carbs, etc.

Anyhow, the probing returns, on my FreeBSD-current system:

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

and in /dev, there isn;'t any ums0 device to be found, and that error #6 is
 (appropriately enough) Device Not Configured.

Well, my first question is, does there exist a tool for USB that let's you
view the raw return from the usb probing?  I want to see what this device
is actually identifying itself as.  Actual numeric vendor IDs and product
IDs are the sort of thing I'm after.  Something a whole lot more detailed
that usbdevs, please.  Even the dmesg listing (as I show above) hasn't got
the numbers and tails I need.

Secondly, if I find out (I've contacted a friendly fellow at the
manufacturer) that this device works very much like, say, a Wacom device,
is there any way to fake out the kernel and force it to think that the
device I'm showing it is actually something else, some alias?  If there
isn't some fairly direct method of doing this, then could someone give me
some sort of description of how I might go about sticking in a fake entry
that works exactly as a present entry?  I figure at least part of it is
find out out that object file holds the intended alias target, and also
mucking about with the usbdevs file,  what else might be required?

If it turns out that a completely new driver is required, then I need no
immediate answer, because (like I said) I wrote the manufacturer, and I
figure they'll take a few years to reply with technical details, and
probably tell me how great their Windows driver is.

Thanks for whatever I can get.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHrf0sz62J6PPcoOkRAn1dAJ4moCo3iBp4WlNF3/sVH14zKR23fgCePt7B
xyKtj04Z/O7oCZKS5fxr2wY=
=TE+n
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47ADFD2C.80009>