Em Qui, 2011-01-06 às 22:54 +0100, Peter Stuge escreveu:
> > 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.

Sure, but the point here is to distinguish two _connected_ USB devices,
i don't really need to distinguish two _physical_ 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.

> 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.

I can see the portability benefit of using a libusb-only approach, but
it would also make it a lot harder to reuse the plugin/driver code for
real-serial connected devices using the same serial protocol.

Anyway, I will not implement userspace libusb logic for cm210x's
usbserial hardware specifics, its not that small and easy... Its already
implemented on kernelspace for most platforms and rewriting it for
libusb seems a waste of resources.

If you know an open source project that has such 'cm210x libusb'
implementation that i can easily copynpaste, please tell me! ;)

-- 
Daniel Ribeiro

Attachment: signature.asc
Description: Esta é uma parte de mensagem assinada digitalmente

------------------------------------------------------------------------------
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

Reply via email to