How about imbedding a list of known good vid/pid numbers and including a
command-line switch of "--forceftdi" to let people test others.
Or actually probe for the latency and buffer sizes you mentioned.
I'm not a big fan of command-line switches. They raise the barrier for new
users. I'd rather things "just work" perfectly. But since this would only
be an optional test it might be a good solution.
On Mon, Jun 23, 2014 at 1:54 AM, Johan Ström <jo...@stromnet.se> wrote:
> Thank you! Looking forward to feedback from more experienced owfs-eyes..
> :)
>
> Scanning the USB bus for vid/pid should be no problem. However, the
> DS9490R seems to use a special vid/pid, where the LinkUSB uses a generic
> "any-kind-of-ftdi-based-adapter"-vid/pid. Unfortunately the dumped strings
> doesn't seem to help much either:
>
> My LinkUSB:
>
> ugen4.2: <FT232R USB UART FTDI> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps)
> pwr=ON (90mA)
> bLength = 0x0012
> bDescriptorType = 0x0001
> bcdUSB = 0x0200
> bDeviceClass = 0x0000
> bDeviceSubClass = 0x0000
> bDeviceProtocol = 0x0000
> bMaxPacketSize0 = 0x0008
> idVendor = 0x0403
> idProduct = 0x6001
> bcdDevice = 0x0600
> iManufacturer = 0x0001 <FTDI>
> iProduct = 0x0002 <FT232R USB UART>
> iSerialNumber = 0x0003 <A900fx3D>
> bNumConfigurations = 0x0001
>
> Compared to another RS232-dongle (identical fields omited):
> ugen3.3: <USB FAST SERIAL ADAPTER FTDI> at usbus3, cfg=0 md=HOST spd=FULL
> (12Mbps) pwr=ON (44mA)
> bcdUSB = 0x0110
> iProduct = 0x0002 <USB FAST SERIAL ADAPTER>
> iSerialNumber = 0x0003 <FTCDDBSX>
>
> Not so much to go on.. the iProduct string is different, but I bet the
> chip is not exactly the same, and that any FT232R based design identifies
> itself as "FT232R USB UART"..
>
> Johan
>
>
> On 23/06/14 00:44, Paul Alfille wrote:
>
> This is incredible work. Definitely will add to the master branch once the
> final touches and test are done.
>
> It's easy, using libusb, to read the vendor/product code. We do it for
> DS9490R adapters now. Beyond vendor/product codes, there are many other USB
> strings. One of them might be characteristic of all the relevant FTDI
> adapters, even custom runs.
>
> Paul
>
>
> On Sun, Jun 22, 2014 at 5:20 PM, Johan Ström <jo...@stromnet.se> wrote:
>
>> ....
>
> > I do have one thing on the todo list, and that is auto-detection.
>>
> > Currently you have to explicitly specify a LinkUSB FTDI serial
>> number
>> > (Linux: lsusb, FreeBSD: usbconfig). This is not very optimal. However,
>> > at least my device uses the standard FTDI Vendor/product ID. This means
>> > I cannot distinguish a random FTDI-based RS232-adapter and a LinkUSB,
>> > without actually talking to the device. This can of course be done, but
>> > I'm not sure it's "acceptable" to start writing to every FTDI adapter
>> > found..
>> >
>> > How is this solved with other auto-detected devices?
>> >
>> >
>> > Looking forward to any and all feedback! :)
>> > Johan
>> >
>> >
>> > [1]
>> >
>> https://sourceforge.net/p/owfs/mailman/owfs-developers/thread/53905A08.40906%40stromnet.se/#msg32422357
>> > [2] https://sourceforge.net/p/owfs/code/merge-requests/1/
>>
>>
>>
>> ------------------------------------------------------------------------------
>> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
>> Find What Matters Most in Your Big Data with HPCC Systems
>> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
>> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
>> http://p.sf.net/sfu/hpccsystems
>> _______________________________________________
>> Owfs-developers mailing list
>> Owfs-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>
>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data
> Explorationhttp://p.sf.net/sfu/hpccsystems
>
>
>
> _______________________________________________
> Owfs-developers mailing
> listOwfs-developers@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing & Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
