glxsb(4) [debian man page]

GLXSB(4)						 BSD/i386 Kernel Interfaces Manual						  GLXSB(4)

NAME

     glxsb -- Geode LX Security Block crypto accelerator

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device crypto
	   device glxsb

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   glxsb_load="YES"

DESCRIPTION

     The glxsb driver supports the security block of the Geode LX series processors.  The Geode LX is a member of the AMD Geode family of inte-
     grated x86 system chips.

     Driven by periodic checks for available data from the generator, glxsb supplies entropy to the random(4) driver for common usage.

     glxsb also supports acceleration of AES-128-CBC operations for crypto(4).	It also registers itself to accelerate other HMAC algorithms,
     although there is no hardware acceleration for those algorithms.  This is only needed so glxsb can work with ipsec(4).

CAVEAT

     The crypto(9) framework will fail to open the crypto session on the device if the AES key's length is != 128 bits.  This prevents the use of
     the glxsb device driver with AES keys of length != 128 bits.

SEE ALSO

     crypto(4), intro(4), pci(4), ipsec(4), random(4), crypto(9)

HISTORY

     The glxsb device driver first appeared in OpenBSD 4.1.  The glxsb device driver was imported into FreeBSD 7.1.

AUTHORS

     The glxsb device driver was written for OpenBSD by Tom Cosgrove.  It was ported to FreeBSD by Patrick Lamaiziere <patfbsd@davenulle.org>

BSD
								   June 8, 2008 							       BSD

UBSEC(4)						   BSD Kernel Interfaces Manual 						  UBSEC(4)

NAME

     ubsec -- Broadcom and BlueSteel uBsec 5x0x crypto accelerator

SYNOPSIS

     To compile this driver into the kernel, place the following lines in your kernel configuration file:

	   device crypto
	   device cryptodev
	   device ubsec

     Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

	   ubsec_load="YES"

DESCRIPTION

     The ubsec driver supports cards containing Broadcom and BlueSteel uBsec 5x0x crypto accelerator chips.

     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) subsys-
     tem.

     On all models except the Bluesteel 5501 and Broadcom 5801, the driver registers itself to provide random data to the random(4) subsystem.

HARDWARE

     The ubsec driver supports cards containing any of the following chips:

	   Bluesteel 5501    The original chipset, no longer made.  This extremely 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 added.

	   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  A BCM5822 with AES capability.

	   Broadcom BCM5825  Faster version of the BCM5823.

SEE ALSO

     crypt(3), crypto(4), intro(4), ipsec(4), random(4), crypto(9)

HISTORY

     The ubsec device driver appeared in OpenBSD 2.8.  The ubsec device driver was imported to FreeBSD 5.0.

BUGS

     The BCM5801 and BCM5802 have not actually been tested.  The AES capability of the BCM5823 is not yet supported; it is awaiting public disclo-
     sure of programming information from Broadcom.

BSD
								   May 16, 2009 							       BSD