TP Link WDR4900 (was NXP p1010se device trees only correct for P1010E/P1014E, not P1010/P1014 SoCs).

2018-07-20 Thread Tim Small
On 09/07/18 23:21, Scott Wood wrote: Thanks for your email. The device in question ships an old uboot (a vendor fork of U-Boot 2010.12-svn15934). This was added by commit 6b70ffb9d1b2e, committed in July 2008... maybe there's a problem with the old U-Boot finding the crypto node on this parti

Re: NXP p1010se device trees only correct for P1010E/P1014E, not P1010/P1014 SoCs.

2018-07-09 Thread Tim Small
On 06/07/18 19:41, Scott Wood wrote: My openwrt patch just does a: /delete-node/ crypto@3; after the p1010si-post.dtsi include. U-Boot should already be removing the node on non-E chips -- see ft_cpu_setup() in arch/powerpc/cpu/mpc85xx/fdt.c Hi Scott, Thanks for your email. The devic

NXP p1010se device trees only correct for P1010E/P1014E, not P1010/P1014 SoCs.

2018-07-06 Thread Tim Small
Hello, I contributed a patch to OpenWRT a couple of days ago to fix the device tree for a device which uses an NXP p1014 without the SEC4 module. I was wondering about getting a similar fix applied upstream... The device uses the P1014 (without SEC4 functionality), and includes: fsl/p1010si