Lines Matching full:such

14 development project. This is the first such API released on Linux to
24 -  Flexible enough to expose more complex USB device capabilities such
43 distinguish drivers running inside such hardware from the more familiar
84     Examples of such controller hardware include the PCI-based NetChip
90     functions, using calls to the controller driver. Because such
109     -  handling life cycle events, such as managing bindings to
115     Such drivers may be modules of proprietary code, although that
144     Other layers may exist. These could include kernel layers, such as
146     on standard POSIX system call APIs such as ``open()``, ``close()``,
148     be an option. Such user mode code will not necessarily be subject to
169 be remotely debugged. Most such USB protocol code doesn't need to be
171 NFS are. Such gadget-side interface drivers should eventually be
191     are reading. One example of such information is endpoint
193     example source code (such as that for "Gadget Zero"), to fully
206 such as device-to-device DMA (without temporary storage in a memory
213 such differences only matter for "endpoint zero" logic that handles
243    hardware, such as the net2280 on PCI (USB 2.0), sa11x0 or pxa25x as
262    configurations, unless the hardware prevents such operation. For OTG
291 USB specifications. Such issues are in the domain of gadget drivers,
344 instances. Each such configuration includes at least one struct
345 :c:type:`usb_function`, which packages a user visible role such as "network
347 such as "Device Firmware Upgrade".
387 the assistance of tools such as GDB running with User Mode Linux. At
389 hooking it up to a simulator for a microcontroller. Such simulators can
431 solution for interoperability with systems such as MS-Windows and MacOS.
465 Such drivers need at most minor changes, and most of the calls added to
473    exposed in new gadget attributes such as ``b_hnp_enable`` flag. HNP