summaryrefslogtreecommitdiffstats
path: root/sys/dev/usb/if_axereg.h
Commit message (Collapse)AuthorAgeFilesLines
* In the device attach routine, don't depend on uaa->iface beingwpaul2003-06-151-0/+1
| | | | | | | | | | | | | | populated. Apparently, if you use an ehci controller, it's not. Use usbd_device2interface_handle() to retrieve the interface handle. NOTE: uaa->iface is populated in the probe routine, so I suspect the fact that it's NULL in the attach routine is a bug in the ehci driver. Also, don't depend on the PHY addresses returned by the AXE_CMD_READ_PHYID command. The address is correct for my LinkSys NIC, but a user has reported that with a D-Link NIC, the PHYID command returns address 4 while the attached Broadcom PHY is in fact strapped for address 0. Instead, latch onto the first PHY address that returns valid data during a readreg operation.
* Add device driver support for the ASIX Electronics AX88172 USB 2.0wpaul2003-04-201-0/+178
ethernet controller. The driver has been tested with the LinkSys USB200M adapter. I know for a fact that there are other devices out there with this chip but don't have all the USB vendor/device IDs. Note: I'm not sure if this will force the driver to end up in the install kernel image or not. Special magic needs to be done to exclude it to keep the boot floppies from bloating again, someone please advise.
OpenPOWER on IntegriCloud