Bug 269471

Summary: U-Blox C099-F9P eval board patch
Product: Base System Reporter: stacy
Component: usbAssignee: freebsd-usb (Nobody) <usb>
Status: New ---    
Severity: Affects Only Me    
Priority: ---    
Version: 13.1-RELEASE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
patch none

Description stacy 2023-02-10 17:56:30 UTC
Created attachment 240055 [details]
patch

The C099-F9P eval board has a USB hub and 3 USB devices, the first
device is the USB port of the ZED-F9P GNSS chip, the second is a FTDI
serial bridge connected to the UART of the ZED-F9P and the third is a
FTDI serial bridge connected to the UART of the ODIN-W2 communications
chip.

The first device is recognized by FreeBSD (by umodem), the other two
are not recognized.

dmesg output after plugging in the board:

ugen1.3: <vendor 0x0424 product 0x2514> at usbus1
uhub4 on uhub2
uhub4: <vendor 0x0424 product 0x2514, class 9/0, rev 2.00/b.b3, addr 3> on usbus1
uhub4: MTT enabled
uhub4: 3 ports with 3 removable, self powered
ugen1.4: <u-blox AG C099 ZED-F9P> at usbus1
ugen1.5: <u-blox AG C099 ODIN-W2> at usbus1
ugen1.6: <u-blox AG - www.u-blox.com u-blox GNSS receiver> at usbus1
umodem0 on uhub4
umodem0: <u-blox AG - www.u-blox.com u-blox GNSS receiver, class 2/0, rev 1.10/1.00, addr 6> on usbus1
umodem0: data interface 1, has CM over data, has no break

dmesg output after patching and compiling uftdi.ko and kldload ./uftdi.ko:

uftdi0 on uhub4
uftdi0: <C099 ZED-F9P> on usbus1
uftdi1 on uhub4
uftdi1: <C099 ODIN-W2> on usbus1