Yes, what Björnke (and Dave C) said is true - in USB termonology the
device interaction requirements are defined by the class it belongs to.
* Mass Storage class = flash drives etc. Rev lists them in "the volumes"
* Communications class = Björnke's "serial over USB" - controller
boards, modems etc that have a command set of their own. These
usually have drivers that Rev lists in "the driverNames" although
they don't always get listed. (I have a 'deviceNames()' function
somewhere (thanks to Dar Scott and Ken Ray) that returns a more
complete list - I'll see if I can dig it out and post it.) These
require that you open driver / read from driver / write to driver
/ close driver. I learned a lot from Sarah Reichelt about working
with this device type. Here is a description of her work with one
such device:
http://www.pdslabs.net/usb/rev-usb1.pdf
* HID class = keyboards, mice etc.
There are about a dozen USB device classes in all, but the ones listed
above are the ones most relevant to the current discussion.
Phil Davis
On 1/14/10 8:15 AM, Björnke von Gierke wrote:
Another boon is that usb developers are lazy (like all developers). Thus they
often use some standard lib for their device, especially if it isn't a network
adapter or other exotic device.
and the most standardised libs are:
disk space (USB memory stick or HD)
user interface (mouses, keyboard, ...)
serial over usb
so it might be worth a shot to check the drivernames when you connect your
device or before and after you install relevant drivers...
of course this is pretty much a shot into the dark...
bjoernke
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
