On Fri, Feb 5, 2016 at 5:12 AM, Martin Michlmayr <[email protected]> wrote: > * JM <[email protected]> [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 been enabled in Debian as >> a module in 4.4~rc4-1~exp1 (debian bug #807634), coexisting with the >> old driver (mv_cesa). > > I think it would be best if you directly repoted this to > [email protected] > and copied: > Boris BREZILLON <[email protected]> > Arnaud Ebalard <[email protected]> > Thomas Petazzoni <[email protected]> > Russell King <[email protected]> > > -- > Martin Michlmayr > http://www.cyrius.com/
Update: I reported the issue to upstream [1] but they cannot replicate it on their hardware. I've built a vanilla 4.4.1 kernel using Debian's .config as explained in [2] and the module still fails in the same fashion. For an independent confirmation, I'd appreciate if someone with a Kirkwood device (preferably a QNAP) could test the 4.4 kernel from experimental and try the following: rmmod mv_cesa modprobe marvell_cesa allhwsupport=1 dmesg | tail -n 1 I've been asked to build a vanilla kernel again using .config provided by Arnaud Ebalard for ReadyNAS Duo [3], but it ends up being too large to fit in QNAP's 2MB mtd kernel partition, and I am also not sure if it will work with the Debian userland, or which drivers I need to enable for the QNAP to work properly (flash, rtc?), any hints would be appreciated. Best regards, Jan 1 http://lists.infradead.org/pipermail/linux-arm-kernel/2016-February/thread.html#405279 2 http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package 3 http://lists.infradead.org/pipermail/linux-arm-kernel/2016-February/405530.html
