Forgot to cc the list. On Tue, Jan 27, 2009 at 1:19 PM, Dan Streetman <[email protected]> wrote: > javax.usb keeps track of the usb topology, and last time I checked > read-write access is unfortunately needed to call the > usbdevfs_connectinfo ioctl to get the topology information. This is > why read-write access is needed. > > If someone helps with the libusb implementation, it should not require > the same write access since libusb (again, last time I checked) > doesn't provide any topology information, it's a flat listing of > devices so that call is not needed and anyone can see the devices. > > Alternately, the Linux implemenation could be changed to use only read > access (if write isn't available) and therefore show all devices only > by using read access. If you want to help make the change feel free. > > On Mon, Jan 26, 2009 at 5:25 AM, Manuel Stahl <[email protected]> wrote: >> I switched to javax.usb from libusbJava recently and now I wonder why >> this lib needs write permissions to the usb hubs. For libusbJava it was >> only necessary to modify the permissions of the device I actually want >> to access but for enumeration it was enough to have read permissions. >> >> Would it be possible to change that behaviour in future? >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> javax-usb-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/javax-usb-devel >> >
------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ javax-usb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
