Print this page
10229 Some man pages have incorrect cross-references
@@ -226,14 +226,14 @@
.Xr usba_hcdi_register 9F
will be called at this point.
.Ss Binding the Root Hub
Once this is set up, the hcdi driver must initialize its root hub by
calling
-Xr usba_hcdi_bind_root_hub 9F .
+.Xr usba_hubdi_bind_root_hub 9F .
To bind the root hub, the device driver is responsible for providing a
device descriptor that represents the hardware.
- Depending on the hardware, this descriptor may be either static or dynamic.
+Depending on the hardware, this descriptor may be either static or dynamic.
.Pp
This device descriptor should be a packed descriptor that is the same
that would be read off of the device.
The device descriptor should match a hub of a USB generation equivalent to the
maximum speed of the device.
@@ -274,11 +274,11 @@
driver to be attached and associated with the root controller.
As such, driver writers need to ensure that all initialization is done prior to
loading the root hub.
Once successfully loaded, driver writers should assume that they'll get other
calls into the driver's operation vector before the call to
-.Xr usba_hubdi_bind_root_hub 9F.
+.Xr usba_hubdi_bind_root_hub 9F .
.Pp
If the call to
.Xr usba_hubdi_bind_root_hub 9F
failed for whatever reason, the driver should unregister from USBA (see
the next section), unwind all of the resources it has allocated, and