Output from dmesg: usbd_match usb0: <Intel 82371AB/EB (PIIX4) USB Host Controller> usbd_attach usbd_new_device bus=0xc09b9000 depth=0 lowspeed=0 usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=0, protocol=0, maxpacket=64, ls=0 usbd_new_device: new dev (addr 1), dev=0xc09b7b00, parent=0xc09b5040 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 usbd_set_config_index: (addr 1) attr=0x40, selfpowered=1, power=0, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 uhub0: 2 ports with 2 removable, self powered usbd_init_port: adding hub port=1 status=0x0101 change=0x0001 usbd_init_port: adding hub port=2 status=0x0100 change=0x0000 uhub_explore: status change hub=1 port=1 usbd_new_device bus=0xc09b9000 depth=1 lowspeed=0 usbd_new_device: adding unit addr=2, rev=100, class=0, subclass=0, protocol=0, maxpacket=8, ls=0 usbd_new_device: new dev (addr 2), dev=0xc09b7800, parent=0xc09b4d00 usbd_probe_and_attach: no device specific driver found usbd_set_config_index: (addr 2) attr=0x40, selfpowered=1, power=0, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 usbd_probe_and_attach: no interface drivers found ugen0 ugen0: Microsoft Microsoft Digital Sound System 80, rev 1.00/1.00, addr 2
If I cat /dev/ugen0, I get ugenread: no edesc splatted across the console (if I enable DIAGNOSTIC), otherwise I get a panic. Personally, I'd prefer that the tests in ugen.c that are currently behind DIAGNOSTIC (i.e. checking for null pointers basically) are made the default. How does a device end up with no edesc? Do you have to set the config first? Is there any docs on our USB stuff apart from the src code? Thanks, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
