Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

On Fri, Apr 22, 2016 at 9:45 PM, Martin Michlmayr wrote: > * JM [2016-02-05 04:20]: >> To quickly bring you up to speed, the driver for Marvell's hardware >> crypto accelerator embedded in their Armada/Kirkwood SoCs has been >> rewritten as marvell_cesa and

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

* JM [2016-02-05 04:20]: > To quickly bring you up to speed, the driver for Marvell's hardware > crypto accelerator embedded in their Armada/Kirkwood SoCs has been > rewritten as marvell_cesa and merged in kernel 4.2. The new driver > received a number of patches since and has

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

Thanks again, it's the same problem as I have. I built a vanilla 4.4.1 kernel with a simple config based on http://natisbad.org/config-duov2-cesa and the marvell_cesa module works correctly there. A vanilla 4.4.1 kernel built with Debian's .config fails. I will try to find out which combination

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

On Feb 15, 2016, at 2:29 AM, JM wrote: > Actually, I just remembered that 4.4 kernel will try to load both the > old and the new module (but without allhwsupport), so please try the > following: > > rmmod mv_cesa > rmmod marvell_cesa > modprobe marvell_cesa allhwsupport=1 >

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

Actually, I just remembered that 4.4 kernel will try to load both the old and the new module (but without allhwsupport), so please try the following: rmmod mv_cesa rmmod marvell_cesa modprobe marvell_cesa allhwsupport=1 dmesg | grep -i cesa Sorry for the confusion Jan On Mon, Feb 15, 2016 at

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

Thanks for the reply. Can you paste your /proc/crypto as well? Thanks, Jan On Mon, Feb 15, 2016 at 11:25 AM, Rick Thomas wrote: >> Here you go... >> >>> root@sheeva:~# rmmod mv_cesa >>> root@sheeva:~# modprobe marvell_cesa allhwsupport=1 >>> root@sheeva:~# dmesg | tail -n 20

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

> Here you go... > >> root@sheeva:~# rmmod mv_cesa >> root@sheeva:~# modprobe marvell_cesa allhwsupport=1 >> root@sheeva:~# dmesg | tail -n 20 >> [ 16.730426] systemd[1]: Mounted Debug File System. >> [ 16.756783] systemd[1]: Started Load Kernel Modules. >> [ 16.776948] systemd[1]: Started

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

On Tue, Feb 9, 2016 at 8:27 PM, Rick Thomas wrote: > > On Feb 9, 2016, at 4:12 AM, JM wrote: > >> On Fri, Feb 5, 2016 at 5:12 AM, Martin Michlmayr wrote: >>> * JM [2016-02-05 04:20]: To quickly bring you up to

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

On Fri, Feb 5, 2016 at 5:12 AM, Martin Michlmayr wrote: > * JM [2016-02-05 04:20]: >> To quickly bring you up to speed, the driver for Marvell's hardware >> crypto accelerator embedded in their Armada/Kirkwood SoCs has been >> rewritten as marvell_cesa and

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

On Feb 9, 2016, at 4:12 AM, JM wrote: > On Fri, Feb 5, 2016 at 5:12 AM, Martin Michlmayr wrote: >> * JM [2016-02-05 04:20]: >>> To quickly bring you up to speed, the driver for Marvell's hardware >>> crypto accelerator embedded in their

marvell_cesa continues to fail on kirkwood with kernel 4.4

Hi, To quickly bring you up to speed, the driver for Marvell's hardware crypto accelerator embedded in their Armada/Kirkwood SoCs has been rewritten as marvell_cesa and merged in kernel 4.2. The new driver received a number of patches since and has been enabled in Debian as a module in

Re: marvell_cesa continues to fail on kirkwood with kernel 4.4

* JM [2016-02-05 04:20]: > To quickly bring you up to speed, the driver for Marvell's hardware > crypto accelerator embedded in their Armada/Kirkwood SoCs has been > rewritten as marvell_cesa and merged in kernel 4.2. The new driver > received a number of patches since and has