Lines Matching refs:and
7 This program is free software; you can redistribute it and/or
30 and an Intel WiNET controller).
40 1. Devices and hosts: the basic structure
44 3. On the air: beacons and enumerating the radio neighborhood
58 these others are Wireless USB and TCP/IP, but seems Bluetooth and
74 many devices are present and the length of their beacons.
76 Devices have a MAC (fixed, 48 bit address) and a device (changeable, 16
77 bit address) and send periodic beacons to advertise themselves and pass
78 info on what they are and do. They advertise their capabilities and a
85 *UWB*: the Ultra-Wide-Band stack -- manages the radio and
92 The Wireless USB spec defines means to control a UWB radio and to
99 mere terms is a USB dongle that enables your PC to have UWB and Wireless
114 whose root port is the radio and the WUSB devices connect to it.
125 their type and kick into gear.
145 Radio Control interface and the WUSB Host Controller interface per se.
159 Devices and hosts: the basic structure
166 For each RC that is detected, a new struct uwb_rc and struct uwb_dev are
172 for HWA and WHCI RCs, so the driver is really a very thin transport that
174 and sends the replies and notifications back to the API
177 neighborhood looks, creating and destroying devices as they show up or
180 Command execution is very simple: a command block is sent and a event
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.
195 Now we have a real HWA device connected and
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
204 connect to them, but this is policy stuff and should be driven
212 On the air: beacons and enumerating the radio neighborhood
214 So assuming we have devices and we have agreed for a channel to connect
222 and beacon group (that's what the zero is for), the dongle's radio
226 /drivers/uwb/neh.c:uwb_rc_neh_grok()/ and delivered to the UWBD, the UWB
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
233 are received in some time, the device is considered gone and wiped out
253 The bandwidth reservation routines are in progress and are thus not
259 completion. [Note: The bandwidth reservation work is in progress and
268 world: HWA-HC, DWA-HC and WHCI-HC.
270 HWA-HC and DWA-HC share that they are Wire-Adapters (USB or WUSB
271 connected controllers), and their transfer management system is almost
274 HWA-HC and WHCI-HC share that they are both WUSB host controllers, so
275 they have to deal with WUSB device life cycle and maintenance, wireless
279 three endpoints (Notifications, Data Transfer In and Data Transfer
280 Out--known as NEP, DTI and DTO in the code).
283 ID and tell the HC to use all that. Then we start it. This means the HC
290 WUSB IEs (host to device commands/notifications) and Device
293 single cluster at the time. The IEs are Information Elements, and
309 the device. First we allocate a /fake port/ and assign an
311 0x80 | fake_port_idx). We fiddle with the fake port status and /hub_wq/
317 exchange (FIXME: not yet done) and issue a /set address 0/ to bring the
322 start enumerating and doing transfers through usb_hcd->urb_enqueue() to
323 read descriptors and move our data.
325 *Device life cycle and keep alives*
328 per-device activity timestamp. If not, every now and then we check and
333 disconnect it from the system (cleaning up internal information and
343 *Sending and receiving data*
345 Data is sent and received through /Remote Pipes/ (rpipes). An rpipe is
346 /aimed/ at an endpoint in a WUSB device. This is the same for HWAs and
349 Each HC has a number of rpipes and buffers that can be assigned to them;
350 when doing a data transfer (xfer), first the rpipe has to be aimed and
355 header (segment request) and then if there is any data, a data buffer
371 (given when we issued it) and the segment number. If it was a data read,
375 the xfer complete at some point and call its callback.
384 array of segments, tallys on segments and buffers and callback
386 and buffer transfers.
394 For IN xfers, we only issue URBs for the segments we want to read and
401 context (wa_xfer) and submit it. When the xfer is done, our callback is
402 called and we assign the status bits and release the xfer resources.
406 and not yet done and when all that is done, the xfer callback will be
419 *HWA* -- Host Wire Adapter / USB dongle for UWB and Wireless USB
430 dongle that is used to deliver an stream of events and notifications to