summaryrefslogtreecommitdiffstats
path: root/drivers/usb/README
diff options
context:
space:
mode:
authorDavid Brownell <david-b@pacbell.net>2005-05-31 10:21:11 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2005-06-27 14:44:01 -0700
commit5da0106f0b9b13afa4a902c01d4c98b002df55ff (patch)
tree3ef5267a83c70ac37b2ce8c4421b839bb228ff41 /drivers/usb/README
parent77078570abe0848c3076b4f7d42f79b1407f3e8f (diff)
downloadop-kernel-dev-5da0106f0b9b13afa4a902c01d4c98b002df55ff.zip
op-kernel-dev-5da0106f0b9b13afa4a902c01d4c98b002df55ff.tar.gz
[PATCH] USB: wireless usb <linux/usb_ch9.h> declarations
This provides declarations for new requests, descriptors, and bitfields as defined in the Wireless USB 1.0 spec. Device support will involve a new "Wire Adapter" device class, connecting a USB Host to a cluster of wireless USB devices. There will be two adapter types: * Host Wireless Adapter (HWA): the downstream link is wireless, which connects a wireless USB host to wireless USB devices (not unlike like a hub) including to the second type of adapter. * Device Wireless Adapter (DWA): the upstream link is wireless, for connecting existing USB devices through wired links into the cluser. All wireless USB devices will need persistent (and secure!) key storage, and it's probable that Linux -- or device firmware -- will need to be involved with that to bootstrap the initial secure key exchange. Some user interface is required in that initial key exchange, and since the most "hands-off" one is a wired USB link, I suspect wireless operation will usually not be the only mode for wireless USB devices. (Plus, devices can recharge batteries using wired USB...) All other key exchange protocols need error prone user interactions, like copying and/or verifying keys. It'll likely be a while before we have commercial Wireless USB hardware, much less Linux implementations that know how to use it. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/usb/README')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud