# # UWB device configuration # menuconfig UWB tristate "Ultra Wideband devices" default n help UWB is a high-bandwidth, low-power, point-to-point radio technology using a wide spectrum (3.1-10.6GHz). It is optimized for in-room use (480Mbps at 2 meters, 110Mbps at 10m). It serves as the transport layer for other protocols, such as Wireless USB (WUSB). The topology is peer to peer; however, higher level protocols (such as WUSB) might impose a master/slave relationship. Say Y here if your computer has UWB radio controllers (USB or PCI) based. You will need to enable the radio controllers below. It is ok to select all of them, no harm done. For more help check the UWB and WUSB related files in . To compile the UWB stack as a module, choose M here. if UWB config UWB_HWA tristate "UWB Radio Control driver for WUSB-compliant USB dongles (HWA)" depends on USB help This driver enables the radio controller for HWA USB devices. HWA stands for Host Wire Adapter, and it is a UWB Radio Controller connected to your system via USB. Most of them come with a Wireless USB host controller also. To compile this driver select Y (built in) or M (module). It is safe to select any even if you do not have the hardware. config UWB_WHCI tristate "UWB Radio Control driver for WHCI-compliant cards" depends on PCI help This driver enables the radio controller for WHCI cards. WHCI is a specification developed by Intel (http://www.intel.com/technology/comms/wusb/whci.htm) much in the spirit of USB's EHCI, but for UWB and Wireless USB radio/host controllers connected via memory mapping (eg: PCI). Most of these cards come also with a Wireless USB host controller. To compile this driver select Y (built in) or M (module). It is safe to select any even if you do not have the hardware. config UWB_I1480U tristate "Support for Intel Wireless UWB Link 1480 HWA" depends on UWB_HWA select FW_LOADER help This driver enables support for the i1480 when connected via USB. It consists of a firmware uploader that will enable it to behave as an HWA device. To compile this driver select Y (built in) or M (module). It is safe to select any even if you do not have the hardware. endif # UWB
path: root/include/uapi/asm-generic/signal.h
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2017-01-17 13:46:29 +0000
committerHerbert Xu <herbert@gondor.apana.org.au>2017-01-23 22:41:33 +0800
commit11e3b725cfc282efe9d4a354153e99d86a16af08 (patch)
tree8b5b9e0e1bcae1ab98ee652ffb7b13b05c209bd6 /include/uapi/asm-generic/signal.h
parentd6040764adcb5cb6de1489422411d701c158bb69 (diff)
crypto: arm64/aes-blk - honour iv_out requirement in CBC and CTR modes
Update the ARMv8 Crypto Extensions and the plain NEON AES implementations in CBC and CTR modes to return the next IV back to the skcipher API client. This is necessary for chaining to work correctly. Note that for CTR, this is only done if the request is a round multiple of the block size, since otherwise, chaining is impossible anyway. Cc: <stable@vger.kernel.org> # v3.16+ Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'include/uapi/asm-generic/signal.h')