On 7/5/05, Frank Hofmann - Solaris Sustaining <[EMAIL PROTECTED]> wrote:
> The whitepaper you quote essentially contains instructions about how
> to use the "ugen" driver. This is not a "USB scanbus" facility, but
> instead an all-purpose generic USB I/O transfer driver that can be
> MADE to attach to a large variety of USB devices. I say "MADE" because
> the admin is supposed to tell it which specific device to bind to, via
> the shown "add_drv -i ....." command (give it the bus/vendor/devid to
> which it shall attach).

I thought that might be the case, but I was missing how exactly what
was posted there would help me create the devstat nodes. Thanks for
clearing up the confusion.

> ugen allows to write userspace USB drivers. This is what the example
> whitepaper is talking about. It's a bit like uscsi, in the sense that
> is allows you to talk raw SCSI/USB protocol to a specific device. But
> it doesn't do a "bus inquiry". prtconf (resp. libdevinfo under the hood)
> does that.
> 
> Btw, ugen, prtconf, libdevinfo, uscsi all have manpages.
> 
> What exactly are you attempting to do ?

I'm trying to get the USB HID report descriptor to find out certain
characteristics about USB hid devices attached to the system, such as
it's exact name, reported coordinate size, etc. Probably something
very similar to what usbms does. I just realised that the source to
usbms is available on opensolaris.org, but is there a more "userland"
friendly way to get the information than what usbms does to get it?
The way I see it being done in the usbms driver appears to imply that
I might only be able to do this through a kernel device driver or
through a program run as root. If I can only do it as root, that's
alright, but I was trying to avoid writing something that required
writing a kernel module.

-- 
Shawn Walker, Software and Systems Analyst
[EMAIL PROTECTED] - http://binarycrusader.blogspot.com/
_______________________________________________
opensolaris-code mailing list
[email protected]
https://opensolaris.org:444/mailman/listinfo/opensolaris-code

Reply via email to