| hifn.4 (198232) | hifn.4 (208027) |
|---|---|
| 1.\" $OpenBSD: hifn.4,v 1.32 2002/09/26 07:55:40 miod Exp $ 2.\" 3.\" Copyright (c) 2000 Theo de Raadt 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 10 unchanged lines hidden (view full) --- 19.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 20.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 21.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 23.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 24.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 25.\" POSSIBILITY OF SUCH DAMAGE. 26.\" | 1.\" $OpenBSD: hifn.4,v 1.32 2002/09/26 07:55:40 miod Exp $ 2.\" 3.\" Copyright (c) 2000 Theo de Raadt 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: --- 10 unchanged lines hidden (view full) --- 19.\" INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 20.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 21.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 22.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 23.\" STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN 24.\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 25.\" POSSIBILITY OF SUCH DAMAGE. 26.\" |
| 27.\" $FreeBSD: head/share/man/man4/hifn.4 198232 2009-10-19 14:36:12Z brueffer $ | 27.\" $FreeBSD: head/share/man/man4/hifn.4 208027 2010-05-13 12:07:55Z uqs $ |
| 28.\" 29.Dd October 19, 2009 30.Dt HIFN 4 31.Os 32.Sh NAME 33.Nm hifn 34.Nd Hifn 7751/7951/7811/7955/7956 crypto accelerator 35.Sh SYNOPSIS --- 66 unchanged lines hidden (view full) --- 102.El 103.Sh SEE ALSO 104.Xr crypt 3 , 105.Xr crypto 4 , 106.Xr intro 4 , 107.Xr ipsec 4 , 108.Xr random 4 , 109.Xr crypto 9 | 28.\" 29.Dd October 19, 2009 30.Dt HIFN 4 31.Os 32.Sh NAME 33.Nm hifn 34.Nd Hifn 7751/7951/7811/7955/7956 crypto accelerator 35.Sh SYNOPSIS --- 66 unchanged lines hidden (view full) --- 102.El 103.Sh SEE ALSO 104.Xr crypt 3 , 105.Xr crypto 4 , 106.Xr intro 4 , 107.Xr ipsec 4 , 108.Xr random 4 , 109.Xr crypto 9 |
| 110.Sh CAVEATS 111The Hifn 9751 shares the same PCI ID. 112This chip is basically a 7751, but with the cryptographic functions missing. 113Instead, the 9751 is only capable of doing compression. 114Since we do not currently attempt to use any of these chips to do 115compression, the 9751-based cards are not useful. 116.Pp 117Support for the 7955 and 7956 is incomplete; the asymmetric crypto 118facilities are to be added and the performance is suboptimal. | |
| 119.Sh HISTORY 120The 121.Nm 122device driver appeared in 123.Ox 2.7 . 124The 125.Nm 126device driver was imported to 127.Fx 5.0 . | 110.Sh HISTORY 111The 112.Nm 113device driver appeared in 114.Ox 2.7 . 115The 116.Nm 117device driver was imported to 118.Fx 5.0 . |
| 119.Sh CAVEATS 120The Hifn 9751 shares the same PCI ID. 121This chip is basically a 7751, but with the cryptographic functions missing. 122Instead, the 9751 is only capable of doing compression. 123Since we do not currently attempt to use any of these chips to do 124compression, the 9751-based cards are not useful. 125.Pp 126Support for the 7955 and 7956 is incomplete; the asymmetric crypto 127facilities are to be added and the performance is suboptimal. |
|
| 128.Sh BUGS 129The 7751 chip starts out at initialization by only supporting compression. 130A proprietary algorithm, which has been reverse engineered, is required to 131unlock the cryptographic functionality of the chip. 132It is possible for vendors to make boards which have a lock ID not known 133to the driver, but all vendors currently just use the obvious ID which is 13413 bytes of 0. | 128.Sh BUGS 129The 7751 chip starts out at initialization by only supporting compression. 130A proprietary algorithm, which has been reverse engineered, is required to 131unlock the cryptographic functionality of the chip. 132It is possible for vendors to make boards which have a lock ID not known 133to the driver, but all vendors currently just use the obvious ID which is 13413 bytes of 0. |