diff options
| author | Daniel González Cabanelas <dgcbueu@gmail.com> | 2021-04-04 23:06:46 +0200 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2021-04-17 21:56:05 +0200 |
| commit | 2e1ebe96c61424d0829bb1c8b5ec44aaa8bea8af (patch) | |
| tree | 737f327376307ce023f39e4d707f08349cd25e1f /target/linux/mvebu/cortexa53 | |
| parent | fa6f57f66c1286c7b649de01de0b994e4e27626e (diff) | |
| download | upstream-2e1ebe96c61424d0829bb1c8b5ec44aaa8bea8af.tar.gz upstream-2e1ebe96c61424d0829bb1c8b5ec44aaa8bea8af.tar.bz2 upstream-2e1ebe96c61424d0829bb1c8b5ec44aaa8bea8af.zip | |
mvebu: armada 370: dts: fix the crypto engine
The crypto engine in Armada 370 SoCs is currently broken. It can be
checked installing the required packages for testing openssl with hw
acceleration:
opkg install openssl-util
opkg install kmod-cryptodev
opkg install libopenssl-devcrypto
After configuring /etc/ssl/openssl.cnf to let openssl use the crypto
engine for digest operations, and performing some checksums..
md5sum 10M-file.bin
openssl md5 10M-file.bin
...we can see they don't match.
There might be an alignment or size constraint issue caused by the
idle-sram area.
Use the whole crypto sram and disable the idle-sram area to fix it. Also
disable the idle support by adding the broken-idle property to prevent
accessing the disabled idle-sram.
We don't care about disabling the idle support since it is already broken
in Armada 370 causing a huge performance loss because it disables
permanently the L2 cache. This was reported in the Openwrt forum and
elsewhere by Debian users with different board models.
Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
Diffstat (limited to 'target/linux/mvebu/cortexa53')
0 files changed, 0 insertions, 0 deletions