Lines Matching full:hardware

22    they're easy to port to new hardware.
36 -  Minimalist, so it's easier to support new device controller hardware.
41 USB ``host`` hardware in a PC, workstation, or server. Linux users with
42 embedded systems are more likely to have USB peripheral hardware. To
43 distinguish drivers running inside such hardware from the more familiar
58 necessarily different (one side is a hardware-neutral master, the other
59 is a hardware-aware slave), the endpoint I/0 API used here should also
69 hardware).
75     to hardware, through registers, fifos, dma, irqs, and the like. The
77     endpoint hardware. That hardware is exposed through endpoint
84     Examples of such controller hardware include the PCI-based NetChip
89     The lower boundary of this driver implements hardware-neutral USB
91     hardware varies widely in capabilities and restrictions, and is used
97     involved in supporting new hardware, by *autoconfiguring* endpoints
110        hardware, USB suspend/resume, remote wakeup, and disconnection
131        test and measurement hardware.
165 to choose hardware endpoints and initialize their descriptors. A
168 developers are interested in KDB or KGDB hooks, to let target hardware
170 hardware-specific, any more than network protocols like X11, HTTP, or
204 The core API does not expose every possible hardware feature, only the
205 most widely available ones. There are significant hardware features,
207 buffer) that would be added using hardware-specific APIs.
210 endpoint capabilities of different hardware, but doesn't require that.
211 Hardware tends to have arbitrary restrictions, relating to transfer
218 autoconfiguration logic that scans the hardware's list of endpoints to
238 Gadget drivers make endpoint I/O requests to hardware without needing to
239 know many details of the hardware, but driver setup/configuration code
243    hardware, such as the net2280 on PCI (USB 2.0), sa11x0 or pxa25x as
254 3. The hardware driver can now start enumerating. The steps it handles
260    on what the bus interface hardware provides and on the functionality
262    configurations, unless the hardware prevents such operation. For OTG
268    That involves using a list of the hardware's endpoints, enabling each
365 The first hardware supporting this API was the NetChip 2280 controller,
371 Other hardware working in the ``gadget`` framework includes: Intel's PXA
386 driver on a normal PC, without any special hardware, and perhaps with
390 help debug subsystems where the runtime hardware is unfriendly to
400 with drivers for usb controller hardware), other gadget drivers exist.
409 hardware can't fully implement the CDC Ethernet requirements, this
416 on more slightly USB hardware (but less than the CDC subset). However,
439 a USB modem, and so on most hardware it can interoperate easily with
453 hardware level details could be very different.
455 Systems need specialized hardware support to implement OTG, notably
463 existing pool of hardware-neutral drivers, layered on top of the
500 Additional changes are needed below those hardware-neutral :c:type:`usb_bus`
502 detail. Those affect the hardware-specific code for each USB Host or