The USB CDC support under windows is plain stupid. That's the only time I've ever seen a mac kernel dump. A few years ago the Prolific drivers actually managed to crash the operating system on my mac. I have found the drivers for FTDI to be superior (although it's too bad the linux driver makes me write udev rules to uniquely identify the device special file name). Every other device/driver I've ever used fails this basic usability test. When I use multiple devices (which is more often than not), I do not want to guess which one is which, or guess what the device special file name (or com port number) is if I happen to plug it in to a different USB port. FTDI is the only one I've found with this feature KeySpan, Prolific, SI Labs, and generic USB CDC devices and drivers all fail this test. Can you tell us what the differences are and what matters?Īs someone already mentioned, the FTDI has a unique serial number that allows use of multiple devices without ambiguity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |