Re: [LEDE-DEV] [PATCHv2] ipq806x: add support for ZyXEL NBG6817

2016-10-18 Thread J Mo
(whoops, resend in plain text) On 10/17/2016 11:22 PM, John Crispin wrote: +boot_hook_add preinit_main preinit_assign_mtd2block >diff --git a/target/linux/ipq806x/base-files/lib/preinit/05_set_iface_mac_ipq806x.sh b/target/linux/ipq806x/base-files/lib/preinit/05_set_iface_mac_ipq806x.sh >new

Re: [LEDE-DEV] [PATCHv2] ipq806x: add support for ZyXEL NBG6817

2016-10-18 Thread J Mo
On 10/18/2016 12:00 AM, John Crispin wrote: On 18/10/2016 08:54, J Mo wrote: On 10/17/2016 11:22 PM, John Crispin wrote: +boot_hook_add preinit_main preinit_assign_mtd2block diff --git a/target/linux/ipq806x/base-files/lib/preinit/05_set_iface_mac_ipq806x.sh b/target/linux/ipq806x/base

Re: [LEDE-DEV] Stability & release plans -- CVE-2016-5195

2016-10-28 Thread J Mo
On 10/28/2016 11:39 AM, yanosz wrote: 1. I'm unhappy with the state of OpenWRT at the moment. I see some trouble in building and releasing. The current code base has some bugs. I'ven't seen a fix for "mad cow" yet. For me it is hard to estimate whether OpenWRT is able to include, build and relea

Re: [LEDE-DEV] [RFC] ADSL Modem Allnet All0333CJ Rev.C / Amazon-SE SoC

2016-11-03 Thread J Mo
On 11/03/2016 02:13 AM, Tino Reichardt wrote: Where should I add my pictures and descriptions of that modem. Should I make an extra project page onto my homepage, or is the lede wiki okay for that? When okay, I need some sample device page of current lede wiki. This is what a forum would be g

Re: [LEDE-DEV] replacing files in base system from a package?

2016-11-23 Thread J Mo
Please revert this patch. This obvious breaks legitimate use cases. On 10/04/2016 12:59 AM, Russell Senior wrote: Fwiw, I ran into trouble with things busybox provides by default, but where I've add packages with fuller versions. In my case it is procps-ng from the packages feed. In order t

[LEDE-DEV] [PATCH v5 3/3] uboot-envtools: Add tew827dru support

2016-11-26 Thread J Mo
Signed-off-by: Jesse Molina --- package/boot/uboot-envtools/files/ipq | 3 +++ 1 file changed, 3 insertions(+) diff --git a/package/boot/uboot-envtools/files/ipq b/package/boot/uboot-envtools/files/ipq index 369f90f..6563b42 100755 --- a/package/boot/uboot-envtools/files/ipq +++ b/package/boot/

[LEDE-DEV] [PATCH v5 2/3] ipq806x: Add support for new device: tew827dru

2016-11-26 Thread J Mo
The TRENDnet TEW-827DRU is an ipq806x wireless router. ipq8064 SoC with 2x ARMv7-ish Krait 300 CPUs at 1.4Ghz 512MB RAM, 256MB SLC NAND flash (64MB default UBI img size) 1x qca8337-al3c 1000BASE-T ethernet switch, 1-WAN, 4-LAN 2x qca9980 802.11 radios 2x USB3 type A Product page: https://www.tren

[LEDE-DEV] [PATCH v5 1/3] ipq806x: Add new script: scripts/its-maker.sh

2016-11-26 Thread J Mo
its-maker.sh creates an .its file, given a series of arguments, which is then used to create a FIT image with mkimage. Required to support the tew827dru, but intended to support the creation of nearly any .its file. Documentation thread on the OpenWRT forum: https://forum.openwrt.org/viewtopic.ph

[LEDE-DEV] [PATCH v5 0/3] Add support for the TRENDnet TEW-827DRU (tew827dru)

2016-11-26 Thread J Mo
Rebase on head commit 97eff5cba52076da476f028b02bae34fd1f3a9f6 No change from v4 except to accommodate changes from 97eff5cba52076da476f028b02bae34fd1f3a9f6 Known issues, history, et-cetera documented on this forum thread: https://forum.openwrt.org/viewtopic.php?id=65956 J Mo (3): ipq806x

Re: [LEDE-DEV] [PATCH v5 2/3] ipq806x: Add support for new device: tew827dru

2016-12-01 Thread J Mo
On 11/27/2016 02:29 AM, Mathias Kresin wrote: I asked you three (!) times to _explain_ what this code should do [0][1][2]. Now I see the very same code again without having ever seen the requested explanation. This still looks like the hackish image code that was required with the old ima

Re: [LEDE-DEV] [PATCH v5 2/3] ipq806x: Add support for new device: tew827dru

2016-12-04 Thread J Mo
On 12/01/2016 11:18 PM, Mathias Kresin wrote: 02.12.2016 06:28, J Mo: On 11/27/2016 02:29 AM, Mathias Kresin wrote: I asked you three (!) times to _explain_ what this code should do [0][1][2]. Now I see the very same code again without having ever seen the requested explanation. This

[LEDE-DEV] mkimage producing FIT images without data files

2016-08-06 Thread J Mo
Hello I am trying to get LEDE to build for a new device, and my device needs a FIT image. However, mkimage appears to be putting out a FIT file without the actual data files being included. All the rest of the FIT file formatting looks right on cursory inspection, but the data files which we

Re: [LEDE-DEV] mkimage producing FIT images without data files

2016-08-06 Thread J Mo
= 0.16 kB = 0.00 MB Architecture: ARM Load Address: unavailable Hash algo:crc32 Hash value: 374daf15 Note the "Data Size: " fields being wrong. The real Image 0 file is 200KB and Image 1 is 5.7MB. On 08/06/2016 03:59 PM, J Mo wrote: Hello I am trying to get LEDE to b

Re: [LEDE-DEV] mkimage producing FIT images without data files

2016-08-06 Thread J Mo
e relative to that path. Why that format is needed is unexplained. I don't have anything good to say about u-boot/denx documentation. On 08/06/2016 04:05 PM, J Mo wrote: Sorry, I forgot to include this stdout from running mkimage manually: FIT description: LEDE FIT image for

[LEDE-DEV] TRENDnet TEW-827DRU (QCA IPQ8064), stuck at "Starting kernel ..."

2016-08-09 Thread J Mo
Hello everyone I am trying to build LEDE for the TRENDnet TEW-827DRU and I'm stuck on a problem where the kernel won't boot. This device is based off the IPQ8064 and QCA9980+QCA9980 chips. Very similar to the TP-Link Archer C2600, Linksys EA8500, and Netgear D7500. I have the factory format

Re: [LEDE-DEV] TRENDnet TEW-827DRU (QCA IPQ8064), stuck at "Starting kernel ..."

2016-08-10 Thread J Mo
I'm not sure what this was but I rebased my branch and it's fixed now. On 08/09/2016 05:33 AM, J Mo wrote: Hello everyone I am trying to build LEDE for the TRENDnet TEW-827DRU and I'm stuck on a problem where the kernel won't boot. This device is based off the IPQ8064

[LEDE-DEV] Older u-boot mangles UBI from ubinize 1.5.2

2016-08-10 Thread J Mo
Greetings I am attempting to port LEDE/OpenWRT to a new device; the TRENDnet TEW-827DRU, which is a IPQ806X-based (AP148) system. It has a NAND flash for storage with a UBI (kernel + squashfs + ubifs). When my system attempts to attach the UBI, I see the following error from linux: [

Re: [LEDE-DEV] Older u-boot mangles UBI from ubinize 1.5.2

2016-08-11 Thread J Mo
I got that good old feeling... like I just jumped onto a bag of flaming poo. Ha ha On 08/11/2016 03:40 AM, Daniel Golle wrote: Understandable. However, we also need to experiment and figure out the mess left behind by $vendor which often doesn't leave a lot of reasonable options for 3rd-p

Re: [LEDE-DEV] Older u-boot mangles UBI from ubinize 1.5.2

2016-08-11 Thread J Mo
On 08/11/2016 05:31 AM, Daniel Golle wrote: That's what I told you in the previous mail, removing the rootfs= parameter from the dts should do the trick, because you just cannot mount a ubi device (which is a character device in Linux) with a block-based filesystem (like squashfs). This cannot

Re: [LEDE-DEV] Older u-boot mangles UBI from ubinize 1.5.2

2016-08-11 Thread J Mo
On 08/11/2016 04:28 AM, J Mo wrote: Hm, I just found another example. I don't know why this didn't turn up in my searches yesterday since it's a perfect match with the EXACT error. This too was on a QSDK AP148: https://patchwork.ozlabs.org/patch/509468/ I think I'll g

Re: [LEDE-DEV] [U-Boot] Older u-boot mangles UBI from ubinize 1.5.2

2016-08-11 Thread J Mo
It's all moot now! I accidentally wrecked my u-boot today. I typoed "nand write ${fileaddr} ${BOOTCONFIG_nand_addr} ${0x800}" When I meant "0x800" instead of the undefined "${0x800}", which u-boot translated to 0xacc. I guess I'm going to find out if that JTAG header works. ___

Re: [LEDE-DEV] wds link problem

2016-08-25 Thread J Mo
Hi I am mentioned in that ticket you linked. I've seen similar problems, but I'm not positive that my situation wasn't just a hardware failure. I will get in contact with that tribut person and work with him. Thanks for bringing this to my attention. Anyway, your problem is different. TP-Li

[LEDE-DEV] ubi-auto-create-ubiblock-device-for-rootfs and mtd-qcom-smem-rename-rootfs-ubi patches not working for me

2016-08-31 Thread J Mo
Hi everyone I know there was recently some traffic on the list here about UBI and mounting rootfs. I caught some of it, but not all of it. Please pardon me if these are already known issues or this doesn't add anything useful to the conversation. I am working on getting the TRENDnet TEW-8

Re: [LEDE-DEV] ubi-auto-create-ubiblock-device-for-rootfs and mtd-qcom-smem-rename-rootfs-ubi patches not working for me

2016-09-01 Thread J Mo
On 09/01/2016 03:05 AM, Daniel Golle wrote: > >Should I bug these? Already known issues? Comments? The current approach to mount the rootfs is based on a naming convention. The mtd partition to be auto-attached has to be named 'ubi', the UBI volume used as rootfs has to be named 'rootfs'. Then

[LEDE-DEV] New device: Two USB ports, only one USB activity LED

2016-09-02 Thread J Mo
Greetings I have a new device I am working on and it has two USB ports but only one USB activity LED. Right now the LED works the way I like with one of the USB ports, but not the other port. I would like for the LED to go active and/or blink when there is activity from either port. Anyon

[LEDE-DEV] LEDE use of WoSign TLS certificates

2016-09-02 Thread J Mo
LEDE uses WoSign. The admin staff might want to look into that. http://www.percya.com/2016/08/chinese-ca-wosign-faces-revocation.html ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Documentation for router support means the famous Table of Hardware

2016-09-07 Thread J Mo
On 09/07/2016 11:43 AM, Jan-Tarek Butt wrote: If anyone have some better ideas for documenting device specific informations pls write it here. Also some feature ideas or potential problems will be very helpful. Maybe you should involve these people in the conversation: https://forum.openwrt.o

[LEDE-DEV] [PATCH 3/4] DTS file for the tew827dru

2016-09-07 Thread J Mo
Signed-off-by: jmomo --- .../arch/arm/boot/dts/qcom-ipq8064-tew827dru.dts | 357 + 1 file changed, 357 insertions(+) create mode 100644 target/linux/ipq806x/files/arch/arm/boot/dts/qcom-ipq8064-tew827dru.dts diff --git a/target/linux/ipq806x/files/arch/arm/boot/dts/qcom-

[LEDE-DEV] [PATCH 0/4] Add support for the TRENDnet TEW-827DRU (tew827dru)

2016-09-07 Thread J Mo
This is an initial patch set proposal to add support for the TRENDnet TEW-827DRU. Especially notice the FIT builder block I put in image-commands.mk. It should probably not go there, but I don't know of an alternative because it can't go into the device makefile. Finally note that patch 494-mt

[LEDE-DEV] [PATCH 2/4] Add support for new device: tew827dru

2016-09-07 Thread J Mo
The TRENDnet TEW-827DRU is an ipq806x wireless router. ipq8064 SoC with 2x ARMv7-ish Krait 300 CPUs at 1.4Ghz 512MB RAM, 256MB SLC NAND flash (64MB default UBI img size) 1x qca8337-al3c 1000BASE-T ethernet switch, 1-WAN, 4-LAN 2x qca9980 802.11 radios 2x USB3 type A Product page: https://www.tre

[LEDE-DEV] [PATCH 1/4] Add new script: scripts/its-maker.sh

2016-09-07 Thread J Mo
its-maker.sh creates an .its file, given a series of arguments, which is then used to create a FIT image. Required to support the tew827dru, but intended to support the creation of any valid .its file. Signed-off-by: jmomo --- scripts/its-maker.sh | 598 +++

[LEDE-DEV] [PATCH 4/4] Add bootconfig and flash script for the tew827dru

2016-09-07 Thread J Mo
The tew827dru requires a u-boot hush shell script to install it's factory image. Additionally, a "bootconfig" partition blob is needed to direct the OEM's "Fail Safe" system to boot from the proper UBI partition. Signed-off-by: jmomo --- .../linux/ipq806x/image/tew827dru-bootconfig.bin | Bin

Re: [LEDE-DEV] [PATCH 1/4] Add new script: scripts/its-maker.sh

2016-09-08 Thread J Mo
On 09/08/2016 12:09 AM, John Crispin wrote: On 08/09/2016 07:04, J Mo wrote: its-maker.sh creates an .its file, given a series of arguments, which is then used to create a FIT image. Required to support the tew827dru, but intended to support the creation of any valid .its file. Signed-off

Re: [LEDE-DEV] [PATCH 4/4] Add bootconfig and flash script for the tew827dru

2016-09-08 Thread J Mo
On 09/08/2016 12:16 AM, John Crispin wrote: On 08/09/2016 07:04, J Mo wrote: The tew827dru requires a u-boot hush shell script to install it's factory image. Additionally, a "bootconfig" partition blob is needed to direct the OEM's "Fail Safe" system to boot

Re: [LEDE-DEV] [PATCH 2/4] Add support for new device: tew827dru

2016-09-08 Thread J Mo
diff --git a/include/image-commands.mk b/include/image-commands.mk index 40a9619..209caf4 100644 --- a/include/image-commands.mk +++ b/include/image-commands.mk @@ -167,3 +167,48 @@ define Build/sysupgrade-tar --rootfs $(call param_get_default,rootfs,$(1),$(IMAGE_ROOTFS)) \

[LEDE-DEV] How to merge/combine more than one mtd partition for storage?

2016-09-08 Thread J Mo
Hello! I have a device which has a 256MB SLC NAND flash for storage. It uses a redundant pair of 64MB UBI partitions. Then it has 108MB of completely unused non-partitioned space at the end of the NAND. I would like to combine these partitions so that I can use the combined 236MB of NAND sp

Re: [LEDE-DEV] A Wiki for LEDE Documentation

2016-09-09 Thread J Mo
On 09/09/2016 05:17 PM, nobody in particular wrote: we should Less "We oughta" More "I will" ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH v2 3/3] uboot-envtools: Add tew827dru support

2016-09-09 Thread J Mo
Signed-off-by: Jesse Molina --- package/boot/uboot-envtools/files/ipq | 3 +++ 1 file changed, 3 insertions(+) diff --git a/package/boot/uboot-envtools/files/ipq b/package/boot/uboot-envtools/files/ipq index 8cf0ddb..f66aabc 100755 --- a/package/boot/uboot-envtools/files/ipq +++ b/package/boot/

[LEDE-DEV] [PATCH v2 0/3] Add support for the TRENDnet TEW-827DRU (tew827dru)

2016-09-09 Thread J Mo
Second round patch set proposal to add support for the TRENDnet TEW-827DRU. I think I fixed all of the issues previously noted. its-maker.sh got a lot of fixes after testing and now supports configurations. It's nearly feature complete. I'm wrote a post over on the OpenWRT forum as documentatio

[LEDE-DEV] [PATCH v2 1/3] ipq806x: Add new script: scripts/its-maker.sh

2016-09-09 Thread J Mo
its-maker.sh creates an .its file, given a series of arguments, which is then used to create a FIT image with mkimage. Required to support the tew827dru, but intended to support the creation of nearly any .its file. Documentation thread on the OpenWRT forum: https://forum.openwrt.org/viewtopic.

[LEDE-DEV] [PATCH v2 2/3] ipq806x: Add support for new device: tew827dru

2016-09-09 Thread J Mo
The TRENDnet TEW-827DRU is an ipq806x wireless router. ipq8064 SoC with 2x ARMv7-ish Krait 300 CPUs at 1.4Ghz 512MB RAM, 256MB SLC NAND flash (64MB default UBI img size) 1x qca8337-al3c 1000BASE-T ethernet switch, 1-WAN, 4-LAN 2x qca9980 802.11 radios 2x USB3 type A Product page: https://www.tre

Re: [LEDE-DEV] [PATCH v2 2/3] ipq806x: Add support for new device: tew827dru

2016-09-10 Thread J Mo
On 09/10/2016 10:27 AM, Mathias Kresin wrote: 10.09.2016 03:35, J Mo: --- a/include/image-commands.mk +++ b/include/image-commands.mk @@ -168,3 +168,19 @@ define Build/sysupgrade-tar --rootfs $(call param_get_default,rootfs,$(1),$(IMAGE_ROOTFS)) \ $@ endef + +define Build

Re: [LEDE-DEV] [PATCH v2 2/3] ipq806x: Add support for new device: tew827dru

2016-09-10 Thread J Mo
On 09/10/2016 06:36 PM, J Mo wrote: diff --git a/target/linux/ipq806x/base-files/lib/preinit/06_set_iface_mac b/target/linux/ipq806x/base-files/lib/preinit/06_set_iface_mac new file mode 100644 index 000..b4ed225 --- /dev/null +++ b/target/linux/ipq806x/base-files/lib/preinit

Re: [LEDE-DEV] [PATCH v2 2/3] ipq806x: Add support for new device: tew827dru

2016-09-14 Thread J Mo
On 09/11/2016 01:39 AM, Mathias Kresin wrote: 11.09.2016 03:36, J Mo: On 09/10/2016 10:27 AM, Mathias Kresin wrote: 10.09.2016 03:35, J Mo: --- a/include/image-commands.mk +++ b/include/image-commands.mk @@ -168,3 +168,19 @@ define Build/sysupgrade-tar --rootfs $(call

[LEDE-DEV] How do I run a script once after factory installation?

2016-09-16 Thread J Mo
The router device that I'm currently working on has some goofy failover system where it has two roofs filesystems (UBI) on it's NAND flash. A special partition has a "upgrade-in-progress" bit that gets set and I need to flip it back to 0x0 after a successful system bootup. If I don't, the bo