All that stuff below is completely foreign to me, but I wanted you to know that on my MAC, my (working perfectly) port is /dev/cu.PL2303-0000203A I have no idea if that helps at all...
Jeff
On Feb 6, 2013, at 3:24 PM, Phaeton wrote:
Thanks for the info, I still have a Windows 7 netbook, 15.4" Asus laptop, a Toshiba 15" laptop, and a quad core hombrew AMD on Asus main board running 4 ghz per core.
But my main computer is the 2011 MacBook 15.4" quad. I love the unix OS. Spent a decade supporting SCO and BSD and Novell 3xx and 4xx. Started out when networks were Thomas Conrad 100 mbps coax on DOS and business software from IBM and Macola.
Fun stuff but I was not involved in any coding other than being an official beta for NT4. So I love learning and asking questions as you might have guessed by now.
Will I Am.
Sent from my 15.4" MacBook Pro, i7 quad core
On Feb 6, 2013, at 5:01 PM, Tom Hayward esarfl@gmail.com wrote:
On Wed, Feb 6, 2013 at 12:57 PM, Phaeton phaeton@neo.rr.com wrote:
I assumed it was a name the system issued a USB to serial port device and not reflected of the driver name.
On Linux, udev usually chooses the device name. On OS X, the driver tells the OS what name it wants.
FTDI usually shows up as /dev/cu.usbserial-xxxxxxxx, where xxxxxxxx is either the device's serial number or, for unserialized devices, a location string that depends on which USB port your device is connected to.
The Prolific PL2303 driver enumerates devices at /dev/cu.usbserial.
I think /dev/cu.PL2303-XXXXXXXX is associated with the open source PL2303 project.
Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users