how to force ucom driver to create /dev/cuaU? for some device?

[Micah]

Vasil Dimov wrote:
> Hi all,
> 
> I have a device (GPS) that connects to the PC via the USB interface
> and I have a software (comms/garmin-utils) that wishes to talk to the
> device.
> 
> The problem is that the software expects a serial port device, not a USB
> one.
> 
> The question is how can I make the ucom(4) create a cuaU? entry for my
> device?
> 
> When I plug the device I get:
> 
> ehci_pcd: change=0x20
> uhub_explore: status change hub=1 port=5
> ehci after reset, status=0x00001801
> ehci_disown: index=5 lowspeed=0
> uhub_explore: status change hub=1 port=1
> ehci_pcd: change=0x20
> uhub_explore: status change hub=1 port=5
> usbd_new_device bus=0xffffffff80ad7000 port=1 depth=1 speed=2
> usbd_new_device: adding unit addr=2, rev=110, class=255, subclass=255, protocol=255, maxpacket=8, len=18, speed=2
> usbd_new_device: new dev (addr 2), dev=0xffffff0000b06b00, parent=0xffffff0000aff400
> usbd_probe_and_attach: trying device specific drivers
> usbd_probe_and_attach: no device specific driver found
> usbd_probe_and_attach: looping over 1 configurations
> usbd_set_config_index: status=0x0001, error=NORMAL_COMPLETION
> usbd_set_config_index: (addr 1) cno=2 attr=0xc0, selfpowered=1, power=0
> usbd_set_config_index: set config 1
> usbd_probe_and_attach: no interface drivers found
> ugen0: vendor 0x091e product 0x0003, rev 1.10/0.01, addr 2
> usbd_set_config_index: free old config
> usbd_set_config_index: status=0x0001, error=NORMAL_COMPLETION
> usbd_set_config_index: (addr 1) cno=2 attr=0xc0, selfpowered=1, power=0
> usbd_set_config_index: set config 1
> 
> This (ofcourse) does not work:
> # gardump -p /dev/ugen0
> gardump: TIOCGETA: Invalid argument
> 
> ucom is loaded:
> # kldstat -v |grep ucom
>                 85 ucom
> 

I don't suppose you tried symlinking ucom to ugen? If that works it's 
just a matter of setting up devfs.rules.

HTH
Micah