Lines Matching refs:it

7    This program is free software; you can redistribute it and/or
8    modify it under the terms of the GNU General Public License version
11    This program is distributed in the hope that it will be useful,
86       associated spectrum to allow for devices sharing it. Allows to
114       whose root port is the radio and the WUSB devices connect to it.
115       To the system it looks like a separate USB host. The driver (will)
117       for which the root hub is the radio...To reiterate: it is a USB
123       package provides a driver for it (it looks like a network
131 wired devices, but it is connected to your PC connected via Wireless
132 USB. To the system it looks like yet another USB host. To the untrained
133 eye, it looks like a hub that connects upstream wirelessly.
135 We still offer no support for this; however, it should share a lot of
143 to EHCI, it allows your wireless USB devices (including DWAs) to connect
144 to your host via a PCI interface. As in the case of the HWA, it has a
154 are in radio proximity to allow drivers to connect to them. As well, it
163 beacon from it) you get a struct uwb_dev that will show up in
192 So let's say we connect a dongle to the system: it is detected and
194 /drivers/uwb/ptc/usb.c:ptc_usb_probe()/] and then it is reenumerated.
196 /drivers/uwb/hwa-rc.c:hwarc_probe()/ picks it up, that will set up the
197 Wire-Adaptor environment and then suck it into the UWB stack's vision of
203       [/uwb_rc_scan()/] so it finds what's available around and tries to
205       from user space. As of now, the operator is expected to do it
221 Now it is visible. If there were other devices in the same radio channel
229 UWBD wakes up and scans the event list; finds a beacon and adds it to
231 the same device, he considers it to be 'onair' and creates a new device
283 ID and tell the HC to use all that. Then we start it. This means the HC
297 Now it all depends on external stimuli.
301 A new device pops up, it scans the radio looking for MMCs that give out
329 if the activity timestamp gets old, we ping the device by sending it a
330 Keep Alive IE; it responds with a /DN_Alive/ pong during the DNTS (this
333 disconnect it from the system (cleaning up internal information and
340 If the device wants to disconnect, it will either die (ugly) or send a
371 (given when we issued it) and the segment number. If it was a data read,
401 context (wa_xfer) and submit it. When the xfer is done, our callback is