The Chelsio crypto driver is an Upper Layer Driver (ULD), making use
of the Chelsio Lower Layer Driver (LLD - cxgb4). The LLD facilitates
the basic infrastructure services of the ULD. These services include
queue allocation, deallocation and registration with LLD. The queues
are used for sending
Adds the config entry for the Chelsio Crypto Driver, Makefile changes
for the same.
Signed-off-by: Yeshaswi M R Gowda
---
drivers/crypto/Kconfig |2 ++
drivers/crypto/Makefile |1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/crypto/Kconfig
The Chelsio's Crypto Hardware can perform the following operations:
SHA1, SHA224, SHA256, SHA384 and SHA512, HMAC(SHA1), HMAC(SHA224),
HMAC(SHA256), HMAC(SHA384), HAMC(SHA512), AES-128-CBC, AES-192-CBC,
AES-256-CBC, AES-128-XTS, AES-256-XTS
This patch implements the driver for above mentioned
Hi Herbert,
This patch series contains 3 patches that add support for Chelsio's
Crypto Hardware.
The patch series has been created against Herbert Xu's tree (crypto-2.6).
It includes patches for Chelsio Low Level Driver(cxgb4) and adds the new
crypto Upper Layer Driver(chcr) under a new
From: Alastair D'Silva
This patch provides the necessary infrastructure to allow drivers
to be automatically loaded via UDEV. It implements the minimum
required to be able to use module_cpu_feature_match to trigger
the GENERIC_CPU_AUTOPROBE mechanisms.
The features exposed
From: Alastair D'Silva
This series allows the vmx_crypto module to be detected and automatically
loaded via UDEV if the CPU supports the vector crypto feature.
Alastair D'Silva (2):
powerpc: Add module autoloading based on CPU features
crypto: vmx - Convert to CPU
From: Alastair D'Silva
This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure
to automatically load the vmx_crypto module if the CPU supports
it.
Signed-off-by: Alastair D'Silva
---
drivers/crypto/vmx/Kconfig | 2 +-
drivers/crypto/vmx/vmx.c
On Tue, Jul 19, 2016 at 11:01:55AM +1000, Michael Ellerman wrote:
>
> Can you please ask for an ack before merging arch patches?
>
> That's a 70 line powerpc patch and a 6 line crypto patch. It has no
> reviews and no acks. I would have preferred it if we could take it via
> the powerpc tree.
On Mon, 2016-07-18 at 10:59 +0200, Pavel Machek wrote:
> On Fri 2016-07-08 10:19:26, Linus Torvalds wrote:
> >
> > [ rare comment rant. I think I'll do this once, and then ignore the
> > discussion ]
> >
> > On Fri, Jul 8, 2016 at 9:45 AM, Herbert Xu
> > wrote:
>
On Mon, Jul 18, 2016 at 08:25:17PM +0800, kbuild test robot wrote:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
> master
> head: c6335cbb0486f09b4c2ae86e84bf87efd667afa6
> commit: 4e6c3df4d729f85997cbf276bfa8ffd8579b8e77 [147/175] crypto: skcipher -
>
Am Montag, 18. Juli 2016, 11:23:26 schrieb Sandy Harris:
Hi Sandy,
> On Mon, Jul 18, 2016 at 3:14 AM, Herbert Xu
wrote:
> > Stephan Mueller wrote:
> >> This patch adds the ability to register templates for RNGs. RNGs are
> >> "meta" mechanisms
From: "Leonidas S. Barbosa"
This patch add XTS support using VMX-crypto driver.
Signed-off-by: Leonidas S. Barbosa
Signed-off-by: Paulo Flabiano Smorigo
---
drivers/crypto/vmx/Makefile | 2 +-
This patch add XTS subroutines using VMX-crypto driver.
It gives a boost of 20 times using XTS.
These code has been adopted from OpenSSL project in collaboration
with the original author (Andy Polyakov ).
Signed-off-by: Leonidas S. Barbosa
On Mon, Jul 18, 2016 at 3:14 AM, Herbert Xu wrote:
> Stephan Mueller wrote:
>> This patch adds the ability to register templates for RNGs. RNGs are
>> "meta" mechanisms using raw cipher primitives. Thus, RNGs can now be
>> implemented as
tree:
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
head: c6335cbb0486f09b4c2ae86e84bf87efd667afa6
commit: 3a01d0ee2b991c8c267620e63a4ab47cd8c30cc4 [163/175] crypto: skcipher -
Remove top-level givcipher interface
reproduce: make htmldocs
All warnings (new
On Fri, Jul 15, 2016 at 02:09:13PM +0300, Dan Carpenter wrote:
> The props->ap[] array is defined like this:
>
> struct alg_props ap[NX_MAX_FC][NX_MAX_MODE][3];
>
> So we can see that if msc->fc and msc->mode are == to NX_MAX_FC or
> NX_MAX_MODE then we're off by one.
>
> Fixes:
On Thu, Jul 14, 2016 at 08:39:18PM -0700, Tadeusz Struk wrote:
> Hi Salvatore,
> On 07/14/2016 03:25 AM, Salvatore Benedetto wrote:
> > Embedding the akcipher_request in pkcs1pad_request don't take
> > into account the context space required by the akcipher object.
>
> I think we do take into
On Wed, Jul 13, 2016 at 03:47:16PM +1000, alast...@au1.ibm.com wrote:
> From: Alastair D'Silva
>
> This series allows the vmx_crypto module to be detected and automatically
> loaded via UDEV if the CPU supports the vector crypto feature.
>
> Alastair D'Silva (2):
>
When an akcipher test fails, we don't know which algorithm failed
because the name is not printed. This patch fixes this.
Signed-off-by: Herbert Xu
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index 769cc2a..5c9d5a5 100644
--- a/crypto/testmgr.c
+++
Use the parameter 'gfp_flags' instead of 'flag' as second argument of
dma_pool_alloc(). The parameter 'flag' is for the TDMA descriptor, its
content has no sense for the allocator.
Signed-off-by: Romain Perier
---
drivers/crypto/marvell/tdma.c | 2 +-
1 file
On Fri 2016-07-08 10:19:26, Linus Torvalds wrote:
> [ rare comment rant. I think I'll do this once, and then ignore the
> discussion ]
>
> On Fri, Jul 8, 2016 at 9:45 AM, Herbert Xu
> wrote:
> >
> > Nack. As I said the commenting style in the crypto API is the
> >
Am Montag, 18. Juli 2016, 15:14:17 schrieb Herbert Xu:
Hi Herbert,
> >
> > diff --git a/crypto/rng.c b/crypto/rng.c
> > index b81cffb..92cc02a 100644
> > --- a/crypto/rng.c
> > +++ b/crypto/rng.c
> > @@ -232,5 +232,36 @@ void crypto_unregister_rngs(struct rng_alg *algs, int
> > count) }
> >
Stephan Mueller wrote:
> This patch adds the ability to register templates for RNGs. RNGs are
> "meta" mechanisms using raw cipher primitives. Thus, RNGs can now be
> implemented as templates to allow the complete flexibility the kernel
> crypto API provides.
>
>
On Wed, Jul 13, 2016 at 03:01:38PM +0100, Will Thomas wrote:
>
> I don't see any other drivers explicitly requesting a fallback
> driver by name. Anyways, should this be done using "sha1-generic"
The problem is that you're relying on the fallback to implement
import/export. So if the fallback
24 matches
Mail list logo