Correction: benchmark parameters was wrong(didn't set the "elapsed" parameters). Old data is deleted and below is correct data. Software type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes md4 2722.18k 9854.38k 28290.99k 53199.87k 71554.39k 72204.29k md5 2624.53k 9288.04k 25463.21kby yuko1225 - Debian
!!WARNING!! !!EXPERIMENTAL!! This is not a drill. Using these codes/binaries/instructions may result DATA LOSS/DATA CORRUPTION/BRICK DEVICE/SECURITY VULNERABLE etc. USE AT YOUR OWN RISK This article is not for beginner. You must understand what you are doing. Skip to the the bottom if you just want the pre-compiled cryptodev binaries for bodhi's 5.2.9 Kirkwood kernel/debian bustby yuko1225 - Debian
Sorry for that. Pogoplug V4 Mobile. Debian buster. 5.2.9-kirkwood-tld-1. The debootstrap system was also debian buster, build on debian jessie kernel. The kernel source tree was 5.2.9 applied with the patch in your kernel package. I tried both way to compile it. Out of the tree and within the tree. Both succeed. The in-tree Makefiles configuration was: obj-$(CONFIG_CRYPTO_OCF_CRYPTODEV)by yuko1225 - Debian
bodhi Wrote: ------------------------------------------------------- > > The cryptodev module has just released v1.10 > this > > year. It doesn't looks like an abandoned > project. > > > https://github.com/cryptodev-linux/cryptodev-linux > > The install instruction is also pretty straight > > forward. make > make install > > > Inby yuko1225 - Debian
bodhi Wrote: ------------------------------------------------------- > yuko1225, > > I would look at the makefile or the build script > of the module source being built. It might be too > old. To see more details, I would need actually > build it myself. > > This is a basic Debian rootfs. So anything more > than Debian build-essential, you might need a >by yuko1225 - Debian
Hi, Thanks for the great tutorial. It's indeed the basic setup for building a module. However in many cases. It's seems we missed something more than just a soft link. https://forum.doozan.com/read.php?2,76709,87984 https://forum.doozan.com/read.php?2,18152,51209#msg-51209 Somehow these two different modules are all missed #include <sys/socket.h> And as racic saby yuko1225 - Debian
Hello bodhi, Could you please look at this issue? https://forum.doozan.com/read.php?2,18152,51209#msg-51209 It still produce exact same error on building the kernel module, even with the latest rootfs and latest kernel&header files. I'm not sure if that's the module's issue or headers issue. The module that pre-build by TheFeaR is for 5.1 which is not the latest kerneby yuko1225 - Debian
bodhi Wrote: ------------------------------------------------------- > yuko1225, > > That reminded me, do you have cpufrequtils > package install? that would be much more accurate > to see the CPU clock. Thanks for the reply. cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0:by yuko1225 - Debian
On the u-boot with uEnv.txt support you can simply add initramfs.runsize=23M To the boot parameter. Since I'm using the bodhi's u-boot this will work for me custom_params=initramfs.runsize=23Mby yuko1225 - Debian
Thanks for the great work you have done. I just successfully turn my long bricked pogoplug v4 back to life. But I do notice one thing. Unlike the old kernel, on these new kernel the BogoMIPS seems always be 333.33. Is that normal? The frequency info from sysfs looks alright though.by yuko1225 - Debian