12 Feb
2015
12 Feb
'15
12:22 p.m.
On Thu, Feb 12, 2015 at 12:08 PM, Aubrey Turner aubrey.c.turner@gmail.com wrote:
I finally found the driver installer and unpack it (using WINE on Ubuntu so as not to mess up my Windows laptop).
What I found is that the Windows driver is just a repackaged version of the FTDI drivers using the vendor and device IDs that RATOC has assigned to the cable.
So, you might be able to try using modprobe to load the the FTDI driver (ftdi_sio) and the RATOC IDs. It's not guaranteed to work, but it may be worth a try.
You should be able to automate this with a udev rule, too. There's more information here: http://chirp.danplanet.com/projects/chirp/wiki/CableGuide_FTDI_OEM_Cables
Who was that complaining about the Chirp website?
Tom KD7LXL