I'm considering upgrading my NSA310 from jessie to stretch. Is it possible to run tvheadend on ARM Kirkwood, debian stretch??by pld - Debian
Hi there, I disassembled my NSA310 and definitely it is equipped with ADT7476, but When I use unmodified kirkwood-nsa310.dts I get adt7476-i2c-0-2e Adapter: mv64xxx_i2c adapter in0: +0.00 V (min = +0.00 V, max = +3.31 V) in1: +0.00 V (min = +0.00 V, max = +2.99 V) in2: +0.00 V (min = +0.00 V, max = +4.39 V) in3: +0.00 V (min = +0.00 V,by pld - Debian
Hi there, My NSA310 is equipped with ADT7476. In the documentation I found: Fan Speed Control ----------------- The driver exposes two trip points per PWM channel. point1: Set the PWM speed at the lower temperature bound point2: Set the PWM speed at the higher temperature bound The ADT747x will scale the PWM linearly between the lower and higher PWM speed when the temperatureby pld - Debian
(still under construction, will continue later) First remark is that cross compiling is quite east. Thus, native compilation on ARM devices is a waste of time (you need ca. 2.5h on ARM to build openssl vs. 5-10min on modern desktop using single thread!). Second remark is that compilation always creates a mess. You need to install sources, compiler, libraries, devel packages and so on. Evenby pld - Debian
Hi there, Is there any way to use buzzer in NSA310?? (the "third" version, red usb led and LM85)by pld - Debian
Hi there There is a bug in the kernel. After setting MTD_NAND_ORION=m I get: [ 5.649977] ------------[ cut here ]------------ [ 5.654625] kernel BUG at drivers/mtd/nand/nand_base.c:4416! [ 5.660309] Internal error: Oops - BUG: 0 [#1] PREEMPT ARM [ 5.665821] Modules linked in: orion_nand(+) gpio_keys ledtrig_heartbeat leds_gpio led_class ext2 mbcache sd_mod sata_mv libata fixeby pld - Debian
Found it!! # diff .config* 5361c5361 < CONFIG_CRYPTO_DEV_MV_CESA=m --- > # CONFIG_CRYPTO_DEV_MV_CESA is not set mv_cesa has to be disabled (in the kernel configuration!) in order to marvell_cesa to work. Blacklisting is not enough.by pld - Debian
Somewhere here: diff .config* 5035c5035,5036 < # CONFIG_MAGIC_SYSRQ is not set --- > CONFIG_MAGIC_SYSRQ=y > CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1 5235c5236 < CONFIG_CRYPTO_AEAD=m --- > CONFIG_CRYPTO_AEAD=y 5243c5244 < CONFIG_CRYPTO_RNG_DEFAULT=m --- > CONFIG_CRYPTO_RNG_DEFAULT=y 5253,5254c5254,5255 < CONFIG_CRYPTO_GF128MUL=m < CONFIG_CRYPTO_NULL=m --by pld - Debian
Hi there, It's not about sources or patches. It's about the kernel configuration. I did compile linux-4.4.3 patched with the patch taken from linux-4.4.0-kirkwood-tld-1-bodhi.tar.bz2 and the config from: https://github.com/archlinuxarm/PKGBUILDs/tree/master/core/linux-kirkwood-dt CESA works as expected. Here are some test results: Before loaging cryptodev: typeby pld - Debian
Hi I kind of brute-force glued together some parts of ArchLinuxARM and stretch with jessie. Now I have working set-up. It's quite messy at the moment so I'll have to clean it up a bit. bodhi Wrote: > Sure, can you extract the patches? I'll take a Sure, but I need few more days. Have to work - hard life. btw: This forced me to set up jessie chroot (inside of PLD) andby pld - Debian
With linux-4.2.0-kirkwood-tld-1-bodhi.tar.bz2 still no luck. But, I did test the ArchLinux. Both, marvell_cesa and crypotodev load cleanly and marvell_cesa shows in /proc/crypto. Kernel version 4.4.1-1-ARCH. Maybe we should steal some patches from there?by pld - Debian
> While loading mv_cesa: > [ 855.515205] MV-CESA:Could not register sha1 > driver > [ 855.520135] MV-CESA:Could not register > hmac-sha1 driver > > While loading marvell_cesa (after removing > mv_cesa): > [ 1701.535309] marvell-cesa: probe of > f1030000.crypto failed with error -524 The same result with linux-4.4.0-kirkwood-tld-1-bodhi.tar.bz2. Can soby pld - Debian
Hi, If you plan to use the md RAID1 volume for the rootfs you may be interested in the second part of the following http://forum.doozan.com/read.php?2,26394,26397#msg-26397 In a week or two I'm going to set up RAID1 on my NSA310. I'll try to write some tutorial then.by pld - Debian
bodhi Wrote: > Thanks for sharing! indeed, the modern new u-boot > versions have made this possible and it is a > pretty convenient feature. I've not tried to > switch to this booting method because some users > still boot with stock u-boot and they only want a > newer kernel. I'm using: U-Boot 1.1.4 (Jun 8 2011 - 18:48:37) Marvell version: 3.4.19 U-Boot coby pld - Debian
Hi again, Some tricks and tips 1. There is no need to generate separate u-boot images for the kernel and initrd. Using following command: mkimage -A arm -O linux -T multi -C none -a 0x00008000 -e 0x00008000 -n "Linux kernel" -d zImage:initrd.img uImage I obtain single u-boot image containing both zImage and initrd. This way you do not have to bother with adjusting separate aby pld - Debian
Hi again, I'm truing to use Marvell cesa engine. Unfortunately I get the following errors: While loading mv_cesa: [ 855.515205] MV-CESA:Could not register sha1 driver [ 855.520135] MV-CESA:Could not register hmac-sha1 driver While loading marvell_cesa (after removing mv_cesa): [ 1701.535309] marvell-cesa: probe of f1030000.crypto failed with error -524 Did anyone found a fixby pld - Debian
Hi, I found 2 ways to set up all buttons on my NSA310 (probably all NSA3xx). Since I did not found to much about it on the net, I decided to share it with you all. 1. Install https://github.com/wertarbyte/magmakeys. Works perfectly. Advantages: - this is a perl script so you do not need to compile and I think that all needed libraries are present in the bodhi rootfs; - contains reaby pld - Debian