On 29/01/16 15:02, Jan Kandziora wrote: > Am 29.01.2016 um 08:28 schrieb Johan Ström: >> On 28/01/16 23:58, Jan Kandziora wrote: >>> Am 28.01.2016 um 23:38 schrieb Johan Ström: >>>> What do you think? >>>> >>> Sounds reasonable. But if you name it owusbprobe, it should be able to >>> detect DS9490 and DS9481, too. >>> >> Actually, I think DS9490 is based on the DS2490 chip, so that is >> implicitly supported (but output can be more explicit)? >> > In a multi-DS9490 setup, you may want to identify the adaptor by port. > We don't have a tool for that yet, so it would be nice if your tool > covers this, too. In the end, we can come up with a better scheme that > -u -u2 and so on. Would that be the one based on the device iteration order? Can someone elaborate on how that digit is computed? From my quick look, it seems to be a number incrementing for every single USB device seen, regardless if it matched or not (might be wrong, just glanced).
Does the DS9490/DS2490 has a serial number that could be used for proper identification? > >> As for the DS9481, it seems to be based on the Prolific PL-2303HXD chip, >> a generic adapter chip similar to the FTDI. Behind that, it emulates a >> DS2480B (owfs source code doesn't even mention this adapter actually). >> I don't see any specific VID/PID info in the Maxim datasheet, >> > That information seems outdated. The adaptor board which came with my > DS28E17 eval kit says DS9481P-300 and it is based on a MAXQ1010 µC. Not > much else in there, the schematics from their datasheet don't match the > circuit at all. Oh, ok. Both https://www.maximintegrated.com/en/products/interface/controllers-expanders/DS9481R-200.html and https://www.maximintegrated.com/en/products/comms/ibutton/DS9481R-3C7.html mentions Prolific. Didn't even find DS9481P-300 until explicitly searching for it. > > So, don't check for a PL2303 in there but for 0b6a:5a03. The driver is > cdc_acm rather that pl2303. It works with owfs as a DS2480 on /dev/ttyACMx. > Great, then we can uniquely identify it at least. And ask user to use /dev/ttyACM*something* at least, even if we cannot identify the port. A note on identifying the port, I found this old thread: http://owfs-developers.1086194.n5.nabble.com/tty2usb-td10852.html Seems it was never finished, or fully resolved.. Given that, I'd like to skip any port-mapping attempts for the moment and just merge the current ftdi support (with some improvements to the tool). Johan ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
