<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Indeed, so why are we indirectly promoting the use of counterfeit
devices then?</p>
<p>If the chip is "Genuine", the currently available "Official"
driver, <i>will</i> work.</p>
<p>Yes, I too have accumulated some dodgy chip driven adapters, just
as everyone I suspect has. I am slowly replacing them as I find
them, not because they don't work (they work just fine under
Linux, for now.) But because they all have the same identity and
no serial number, making the use of multiple devices and nailing
their feet to the numeric floor with Udev rules, rather
troublesome.</p>
<p>I prefer FTDI parts, as by default they all have a unique serial
number, making Udev rules easy and reliable.
</p>
<p>SiLabs parts are a close second choice*, with Prolific only if
there is absolutely no other alternative. Even the genuine
Prolific chips don't seem to have a "unique" identity. (Unless
I've not yet seen a "Genuine" chip!)</p>
<p>General Linux trick: What I've found is that if you build a Udev
table for regularly connected devices, starting from /dev/ttyUSB1
(or higher) then anything else that is randomly connected later,
will always show up as ttyUSB0 or 2 etc, as they is still vacant.<br>
</p>
<p>End.</p>
<p>73.</p>
<p>Dave G0WBX.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 23/09/18 20:00,
<a class="moz-txt-link-abbreviated" href="mailto:chirp_users-request@intrepid.danplanet.com">chirp_users-request@intrepid.danplanet.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:mailman.1.1537729203.6624.chirp_users@intrepid.danplanet.com">
<pre wrap="">I don't think you will find the older v3.2.0.0 driver available for
download on the Prolific site.</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Created on and sent from a Unix like PC running and using free and open source software.
::
</pre>
</body>
</html>