USB stop to identify sun keyboard

[Hans Petter Selasky]

On Wednesday 06 January 2010 11:17:33 Renato Botelho wrote:

> 
> ugen1.1: <UHCI root HUB VIA> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps)
>  pwr=ON ugen0.1: <UHCI root HUB VIA> at usbus0, cfg=0 md=HOST spd=FULL
>  (12Mbps) pwr=ON ugen2.1: <UHCI root HUB VIA> at usbus2, cfg=0 md=HOST
>  spd=FULL (12Mbps) pwr=ON ugen3.1: <UHCI root HUB VIA> at usbus3, cfg=0
>  md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: <EHCI root HUB VIA> at usbus4,
>  cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: <product 0x100e vendor
>  0x0430> at usbus0, cfg=0 md=HOST
> spd=FULL (12Mbps) pwr=SAVE
> ugen0.3: <USB Mouse vendor 0x0566> at usbus0, cfg=0 md=HOST spd=LOW
> (1.5Mbps) pwr=ON
> ugen0.4: <product 0x00a2 vendor 0x0430> at usbus0, cfg=0 md=HOST
> spd=FULL (12Mbps) pwr=ON
> 
> The both unidentified are the same ones added on rev. 190089,
> the keyboard and the USB Hub
> 

That is because these devices provide a device string, while your SUN keyboard 
does not. See:

usbconfig -u X -a Y dump_device_desc dump_curr_config_desc

Look for fields starting with iXXXX .

--HPS