On Thu, Oct 23, 2008 at 02:28:32PM +0200, Christian Hohnstaedt wrote:
>
> atomic_set(&ctx->configuring, 0);
> + switch ((image_id>>16) & 0xff) {
> + case 3:
> + if (cipher_cfg_enc(tfm) & MOD_AES) {
> + printk(KERN_ERR "Firmware o
upport AES, or even
> > no crypto at all.
>
> What happens when two tfms are constructed at the same time?
>
Subject: [PATCH] ixp4xx_crypto: avoid firmware loading during module
initialisation
By moving the firmware-loading to the transform initialisation,
the driver may be com
Christian Hohnstaedt <[EMAIL PROTECTED]> wrote:
> By moving the firmware-loading to the transform initialisation,
> the driver may be compiled in.
>
> Notify the user if the firmware does not support AES, or even
> no crypto at all.
What happens when two tfms are constructed at the same time?
Ch
By moving the firmware-loading to the transform initialisation,
the driver may be compiled in.
Notify the user if the firmware does not support AES, or even
no crypto at all.
Signed-off-by: Christian Hohnstaedt <[EMAIL PROTECTED]>
---
drivers/crypto/ixp4xx_crypto.c | 44 +++
