UBSEC(4) BSD Programmer's Manual UBSEC(4)
ubsec - Broadcom and BlueSteel uBsec 5x0x crypto accelerator
ubsec* at pci? dev ? function ?
The ubsec driver supports cards containing any of the following chips: Bluesteel 5501 The original chipset, no longer made. This ex- tremely rare unit was not very fast, lacked an RNG, and had a number of other bugs. Bluesteel 5601 A faster and fixed version of the original, with a random number unit and large number engine ad- ded. Broadcom BCM5801 A BCM5805 without public key engine or random number generator. Broadcom BCM5802 A slower version of the BCM5805. Broadcom BCM5805 Faster version of Bluesteel 5601. Broadcom BCM5820 64 bit version of the chip, and significantly more advanced. Broadcom BCM5821 Faster version of the BCM5820. This is the chip found on the Sun Crypto Accelerator 1000. Broadcom BCM5822 Faster version of the BCM5820. Broadcom BCM5823 Faster version of the BCM5822. The ubsec driver registers itself to accelerate DES, Triple-DES, MD5- HMAC, and SHA1-HMAC operations for ipsec(4) and crypto(4). On those models which contain a public key engine (almost all of the more recent ones), this feature is registered with the crypto(4) subsystem. On all models except the Bluesteel 5501 and Broadcom 5801, the driver re- gisters itself to provide random data to the random(4) subsystem.
crypt(3), crypto(4), intro(4), ipsec(4), random(4), crypto(9)
The ubsec device driver appeared in OpenBSD 2.8.
The BCM5801 and BCM5802 have not actually been tested. Also, some of the newer chips support AES but it is not supported by the driver. MirOS BSD #10-current June 10, 2000 1
Generated on 2015-04-13 10:26:13 by $MirOS: src/scripts/roff2htm,v 1.80 2015/01/02 13:54:19 tg Exp $
These manual pages and other documentation are copyrighted by their respective writers;
their source is available at our CVSweb,
AnonCVS, and other mirrors. The rest is Copyright © 2002–2015 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.
This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.