Daniel Ribeiro wrote: > > The only correct way to identify devices is using the serial number, > > as stored in a string descriptor referenced in the iSerial field in > > the device descriptor. > > On USB identifying device instances is not an issue, even without > iSerial: Bus/Device numbers are unique.
The serial number is the correct way to distinguish two identical USB devices per spec. Everything else is a workaround for broken devices. > Replicating standard usb-serial, supported by kernel mode drivers > on virtually all platforms with an userspace implementation? Right. As you may know there is no real hard spec for USB-serial and drivers are often device-specific, and since just using libusb would be simpler there could be a point to avoiding kernel drivers that expose this device as a serial port. > the code would definitely be smaller than a full usb-serial > userspace implementation. A bulk transfer with libusb is literally one line of code. Messing with the kernel driver model is not pretty, absolutely not cross platform and certainly not as easy as just using libusb. //Peter
pgpDrFyAfpKxn.pgp
Description: PGP signature
------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
