Lines Matching refs:that

11    This program is distributed in the hope that it will be useful,
56 UWB is a wide-band communication protocol that is to serve also as the
91       *WUSB*: the layer that sits on top of UWB to provide Wireless USB.
99 mere terms is a USB dongle that enables your PC to have UWB and Wireless
118       controller that is connected via USB instead of PCI.
133 eye, it looks like a hub that connects upstream wirelessly.
136 code with the HWA-RC driver; there is a bunch of factorization work that
137 has been done to support that in upcoming releases.
142 This is your usual PCI device that implements WHCI. Similar in concept
162 each device that pops up in radio presence (ie: the UWB host receives a
163 beacon from it) you get a struct uwb_dev that will show up in
166 For each RC that is detected, a new struct uwb_rc and struct uwb_dev are
169 Each RC driver is implemented by a separate driver that plugs into the
170 interface that the UWB stack provides through a struct uwb_rc_ops. The
172 for HWA and WHCI RCs, so the driver is really a very thin transport that
175 [/uwb_rc_neh_grok()/]. Notifications are handled to the UWB daemon, that
196 /drivers/uwb/hwa-rc.c:hwarc_probe()/ picks it up, that will set up the
222 and beacon group (that's what the zero is for), the dongle's radio
225 the event stream that is funneled into the API with
234 [uwbd calls periodically /uwb/beacon.c:uwb_beca_purge()/ that will purge
270 HWA-HC and DWA-HC share that they are Wire-Adapters (USB or WUSB
274 HWA-HC and WHCI-HC share that they are both WUSB host controllers, so
283 ID and tell the HC to use all that. Then we start it. This means the HC
289       that define a stream in the UWB channel time allocated for sending
294       among them are the bandwidth allocations that tell each device
301 A new device pops up, it scans the radio looking for MMCs that give out
341 /DN_Disconnect/ that will prompt a disconnection from the system.
349 Each HC has a number of rpipes and buffers that can be assigned to them;
361 intensive, if any...not that the current approach is not. It just has to
367 When the xfer is executed, we receive a notification that says data is
370 descriptor that gives us the status of the transfer, its identification
374 callbacks for the URBs issued from here are the ones that will declare
406 and not yet done and when all that is done, the xfer callback will be
430 dongle that is used to deliver an stream of events and notifications to