Jump to content

USBD.SYS: Difference between revisions

From EDM2
No edit summary
Ak120 (talk | contribs)
Line 10: Line 10:
;/REQ
;/REQ
:Parameter controls USBD driver initialization: driver at initialization time checks for listed host controller drivers and fails to install if none of listed drivers is loaded. Current version of USB stack supports the following parameter codings:
:Parameter controls USBD driver initialization: driver at initialization time checks for listed host controller drivers and fails to install if none of listed drivers is loaded. Current version of USB stack supports the following parameter codings:
*: '''/REQ:USBUHCD$''' USBD driver is loaded only if UHCI compliant host driver is loaded
:* '''/REQ:USBUHCD$''' USBD driver is loaded only if UHCI compliant host driver is loaded
*: '''/REQ:USBOHCD$''' USBD driver is loaded only if OHCI compliant host driver is loaded
:* '''/REQ:USBOHCD$''' USBD driver is loaded only if OHCI compliant host driver is loaded
*: '''/REQ:USBEHCD$''' USBD driver is loaded only if EHCI compliant host driver is loaded
:* '''/REQ:USBEHCD$''' USBD driver is loaded only if EHCI compliant host driver is loaded
*: '''/REQ:USBUHCD$,USBOHCD$,USBEHCD$''' USBD driver is loaded only if one of OHCI/UHCI/EHCI compliant host drivers are loaded. This most general form of parameter and must be used in most cases. If you are using /REQ parameter all statements "BASEDEV=USBUHCD.SYS", "BASEDEV=USBOHCD.SYS" and "BASEDEV=USBEHCD.SYS" must be first in the sequence of USB statements.
:* '''/REQ:USBUHCD$,USBOHCD$,USBEHCD$''' USBD driver is loaded only if one of OHCI/UHCI/EHCI compliant host drivers are loaded. This most general form of parameter and must be used in most cases. If you are using /REQ parameter all statements "BASEDEV=USBUHCD.SYS", "BASEDEV=USBOHCD.SYS" and "BASEDEV=USBEHCD.SYS" must be first in the sequence of USB statements.
 


[[Category:BASEDEV Statements]]
[[Category:BASEDEV Statements]]

Revision as of 23:31, 8 June 2021

Product Support
OS/2 1.3
OS/2 2.0
OS/2 2.1
OS/2 2.11 SMP
OS/2 Warp 3 S
OS/2 Warp Connect S
OS/2 Warp 4 S
OS/2 Warp Server for e-Business S

The USB driver (USBD.SYS) supports EHCI, OHCI and UHCI compatible USB controllers.

BASEDEV=USBD.SYS <parameters>

Parameters

/V
Verbose Mode, displays driver information during OS/2 initialization.
/I13
Could be used to delay USB host overtaking by USB driver stack until other device driver finishes required initialization operations and then send request to USBD driver to start USB service. It could be used to boot from USB floppy drive.
/REQ
Parameter controls USBD driver initialization: driver at initialization time checks for listed host controller drivers and fails to install if none of listed drivers is loaded. Current version of USB stack supports the following parameter codings:
  • /REQ:USBUHCD$ USBD driver is loaded only if UHCI compliant host driver is loaded
  • /REQ:USBOHCD$ USBD driver is loaded only if OHCI compliant host driver is loaded
  • /REQ:USBEHCD$ USBD driver is loaded only if EHCI compliant host driver is loaded
  • /REQ:USBUHCD$,USBOHCD$,USBEHCD$ USBD driver is loaded only if one of OHCI/UHCI/EHCI compliant host drivers are loaded. This most general form of parameter and must be used in most cases. If you are using /REQ parameter all statements "BASEDEV=USBUHCD.SYS", "BASEDEV=USBOHCD.SYS" and "BASEDEV=USBEHCD.SYS" must be first in the sequence of USB statements.