USB serial port vs 6.1

[Henrik Brix Andersen]

On Wed, Jan 30, 2008 at 12:19:35AM -0800, perryh at pluto.rain.com wrote:
> Yes, the console now reports
> 
>   ucom0: FIDI usb serial converter, rev 1.10/4.00, addr 3
> 
> and /dev contains:
> 
>   crw-rw----  1 uucp  dialer    1,  23 Nov 24 21:17 /dev/cuaU0
>   crw-rw----  1 uucp  dialer    1,  24 Nov 24 21:17 /dev/cuaU0.init
>   crw-rw----  1 uucp  dialer    1,  25 Nov 24 21:17 /dev/cuaU0.lock
>   crw-------  1 root  wheel     1,  20 Nov 24 21:17 /dev/ttyU0
>   crw-------  1 root  wheel     1,  21 Nov 24 21:17 /dev/ttyU0.init
>   crw-------  1 root  wheel     1,  22 Nov 24 21:17 /dev/ttyU0.lock
> 
> so apparently the combination of uftdi and ucom picked it up.
> (I already had ucom loaded from the earlier attempt to get the
> modem recognized as a USB <==> serial device.)

Good.

> Short of guesswork, or loading everything, how would one go about
> figuring out which of the various uxxx shims is going to be needed
> to connect a given serial device to ucom?  I notice that "man uftdi"
> does not mention "FIDI" (granted "FTDI" is close).

Odd - I actually read your original mail as "FTDI" and not "FIDI",
which is why I recommended the uftdi(4) driver.

The best way of matching a USB device to an unloaded driver, is to
check for the VID (Vendor ID) and PID (Product ID) of the device and
compare them to those listed in the various drivers.

Brix
-- 
Henrik Brix Andersen <brix at FreeBSD.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 217 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-usb/attachments/20080130/76a3d958/attachment.pgp