All of lore.kernel.org
 help / color / mirror / Atom feed
From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: marvell_cesa fails to register on kirkwood (88F6282)
Date: Fri, 05 Feb 2016 22:04:44 +0100	[thread overview]
Message-ID: <87twlmdg2b.fsf@natisbad.org> (raw)
In-Reply-To: <8760y2vqje.fsf@natisbad.org> (Arnaud Ebalard's message of "Fri, 05 Feb 2016 21:41:09 +0100")

Hi,

> I'll try and do the same now w/ CESA support compiled as module to see
> what I get. I'll keep you posted.

root at mood:~# insmod /tmp/marvell-cesa.ko 
[  573.897977] marvell-cesa f1030000.crypto: CESA device successfully registered

root at mood:~# uname -a
Linux mood 4.4.0.duov2 #2 Fri Feb 5 21:42:49 CET 2016 armv5tel GNU/Linux

root at mood:~# zcat /proc/config.gz | grep -i CESA
# CONFIG_CRYPTO_DEV_MV_CESA is not set
CONFIG_CRYPTO_DEV_MARVELL_CESA=m

Cheers,

a+

ps: my config is temporarily at http://natisbad.org/config-duov2-cesa

  reply	other threads:[~2016-02-05 21:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05  5:01 marvell_cesa fails to register on kirkwood (88F6282) JM
2016-02-05  9:02 ` Andrew Lunn
2016-02-05 10:29   ` Boris Brezillon
2016-02-05 15:00     ` JM
2016-02-05 15:45       ` Gregory CLEMENT
2016-02-05 16:01         ` JM
2016-02-05 16:09           ` Gregory CLEMENT
2016-02-05 16:28             ` Gregory CLEMENT
2016-02-05 20:41               ` Arnaud Ebalard
2016-02-05 21:04                 ` Arnaud Ebalard [this message]
2016-02-06 15:14                   ` JM
2016-02-06 21:57                     ` Arnaud Ebalard
2016-02-08 17:23                     ` Russell King - ARM Linux
2016-02-14  0:09                       ` JM
2016-04-05 20:30                         ` JM
2016-02-05 22:57                 ` JM
2016-02-05 16:28           ` Boris Brezillon
2016-02-05 17:21             ` JM
2016-02-05 15:58 ` Fabio Estevam
2016-02-05 16:02   ` Boris Brezillon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87twlmdg2b.fsf@natisbad.org \
    --to=arno@natisbad.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.