Lines Matching refs:t
21 peripheral). Also, the host software doesn't need to deal with
33 don't do the same things as the ones running inside hosts, so they've
99 Different controllers don't
101 faults (including software-induced ones like unlinking an URB) isn't yet
104 controller driver, to make sure drivers don't have bugs of their own as
105 well as to make sure they aren't relying on some HCD-specific behavior.
156 they don't necessarily need to provide the DMA mapping themselves. There
185 it doesn't do much in hardware. OHCI was designed later, to have the
252 always leave the devices plugged in to the same hub port. *Don't even
257 second server. Pleast note that it doesn't (yet) expose those IDs.
279 an endpoint from one thread, you won't be able to write to a different
287 you can't rely on them for stable access to devices. For example,
332 If your code can't handle more than one device at a time, at least
338 requests; some devices don't need more complex interactions than those.
389 A number of usbfs requests don't deal very directly with device I/O.
399 Note that if your driver doesn't claim an interface before trying to
418 *You can't tell whether a "not slow" device is connected at high
471 filesystem operations even when they don't create a character or
575 At this writing, you can't transfer more than 4 KBytes of data to or
742 P = Product ID info. (from Device descriptor, but they won't fit
861 | can't be shared with any other device.