Re: [OpenWrt-Devel] More bad RPATH
Hi Etienne, please test after fresh build with these two patches applied: http://luci.subsignal.org/~jow/rpath/ My first thought was to fixup libtool to not spray rpaths all over the place but since replacing every libtool in every package seems futile the next best place to do so would be the rstrip.sh script which already prepares all executables and shared objects for packaging. The series above packages patchelf as host utility and uses it to strip rpaths which are either within $TOPDIR or exactly /lib or /usr/lib (standard library search path). We can extend this as needed to exclude other dangerous paths like /tmp, /var or /mnt... ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 0/7] Add custom TRX header option
Patchset to essentially add custom TRX header to all firmware produced. This is most useful for the Belkin routers from my experience. I'm not how other trx based firmwares modify the header for their own purposes. This is applied across the board so that the kernel, trx tools and mtd tools are all compiled with the specified header. I have modified the kernel specifically for the brcm47xx based boards to ensure the mtd parser looks for the correct magic. NOTE: This function will, for other boards, fail. Will Sheppard (7): config: Add option to specify custom TRX header mtd: Add custom trx magic option to mtd tool mtd: Fix: Use TRX_MAGIC define not hard-coded number trx: Add custom TRX option to trx firmware tool mtd: Add debug showing header magic in use kernel: bcm47xx: Add custom TRX header option to kernel mtd: Fix makefile to work with quilt as per wiki config/Config-images.in| 15 ++ package/system/mtd/Makefile| 9 +- package/system/mtd/src/trx.c | 10 +-- .../patches-3.14/162-Belkin_custom_trx_magic.patch | 35 ++ tools/firmware-utils/Makefile | 4 +++ tools/firmware-utils/src/trx.c | 10 ++- 6 files changed, 79 insertions(+), 4 deletions(-) create mode 100644 target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] raspberry pi v3.19
On Feb 9, 2015 4:25 AM, John Crispin blo...@openwrt.org wrote: Hi, i synced our rpi port with the upstream tree on github. it boots and i can see the coloured palette test pic on the hdmi, however ethernet fails to come up. i attached a uart just to find out that my rpi is either broken or i am connecting it wrong. has anyone managed to get uart working ? to my understanding i need to connect pin6 to gnd and use 8 and 10 for the 2 data lines. should i see output from the bootloader prior to board detecting/loading the sd card You will not get any UART output prior to the kernel boot, the GPU boot code does not output anything (at least not in the builds we use). Could you share the boot log to see if there is anything obvious? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 7/7] mtd: Fix makefile to work with quilt as per wiki
Signed-off-by: Will Sheppard wshepp...@embedded-bits.co.uk --- package/system/mtd/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/package/system/mtd/Makefile b/package/system/mtd/Makefile index 91c4fac..5da27d1 100644 --- a/package/system/mtd/Makefile +++ b/package/system/mtd/Makefile @@ -34,6 +34,7 @@ endef define Build/Prepare mkdir -p $(PKG_BUILD_DIR) $(CP) ./src/* $(PKG_BUILD_DIR)/ + $(call Build/Prepare/Default) endef target=$(firstword $(subst -, ,$(BOARD))) -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 4/7] trx: Add custom TRX option to trx firmware tool
Signed-off-by: Will Sheppard wshepp...@embedded-bits.co.uk --- tools/firmware-utils/Makefile | 4 tools/firmware-utils/src/trx.c | 10 +- 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/tools/firmware-utils/Makefile b/tools/firmware-utils/Makefile index 83c51d7..9c9a6a5 100644 --- a/tools/firmware-utils/Makefile +++ b/tools/firmware-utils/Makefile @@ -18,7 +18,11 @@ endef define Host/Compile mkdir -p $(HOST_BUILD_DIR)/bin $(call cc,addpattern) +ifeq ($(CONFIG_KERNEL_TRX_MAGIC_OVERRIDE),y) + $(call cc,trx,-DCONFIG_KERNEL_TRX_MAGIC_OVERRIDE -DCONFIG_KERNEL_TRX_MAGIC=$(CONFIG_KERNEL_TRX_MAGIC) ) +else $(call cc,trx) +endif $(call cc,motorola-bin) $(call cc,dgfirmware) $(call cc,mksenaofw md5) diff --git a/tools/firmware-utils/src/trx.c b/tools/firmware-utils/src/trx.c index aa1f5be..848d67b 100644 --- a/tools/firmware-utils/src/trx.c +++ b/tools/firmware-utils/src/trx.c @@ -66,7 +66,15 @@ uint32_t crc32buf(char *buf, size_t len); /**/ /* from trxhdr.h */ -#define TRX_MAGIC 0x30524448 /* HDR0 */ + +#ifndef CONFIG_KERNEL_TRX_MAGIC_OVERRIDE +#warning Using default TRX MAGIC +#define TRX_MAGIC 0x30524448 /* HDR0 */ +#else +#warning TRX firmware tool is using overridden TRX_MAGIC +#define TRX_MAGIC (CONFIG_KERNEL_TRX_MAGIC) +#endif + #define TRX_MAX_LEN0x72 #define TRX_NO_HEADER 1 /* Do not write TRX header */ -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 1/7] config: Add option to specify custom TRX header
Signed-off-by: Will Sheppard wshepp...@embedded-bits.co.uk --- config/Config-images.in | 15 +++ 1 file changed, 15 insertions(+) diff --git a/config/Config-images.in b/config/Config-images.in index 5c2e79e..e4e4804 100644 --- a/config/Config-images.in +++ b/config/Config-images.in @@ -6,6 +6,21 @@ menu Target Images + + config KERNEL_TRX_MAGIC_OVERRIDE + bool Override TRX magic number + default n + help + Select to override default TRX_MAGIC value of HDR0 + + config KERNEL_TRX_MAGIC + hex TRX_MAGIC + default 0x12345678 + depends on KERNEL_TRX_MAGIC_OVERRIDE + help + Enter magic + + menuconfig TARGET_ROOTFS_INITRAMFS bool ramdisk default y if USES_INITRAMFS -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 5/7] mtd: Add debug showing header magic in use
Signed-off-by: Will Sheppard wshepp...@embedded-bits.co.uk --- package/system/mtd/src/trx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/system/mtd/src/trx.c b/package/system/mtd/src/trx.c index 1722cf2..776cb82 100644 --- a/package/system/mtd/src/trx.c +++ b/package/system/mtd/src/trx.c @@ -160,7 +160,7 @@ mtd_fixtrx(const char *mtd, size_t offset) size_t block_offset; if (quiet 2) - fprintf(stderr, Trying to fix trx header in %s at 0x%x...\n, mtd, offset); + fprintf(stderr, Trying to fix trx header in %s at 0x%x... Magic 0x%08X\n, mtd, offset, TRX_MAGIC); fd = mtd_check_open(mtd); if(fd 0) { -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 6/7] kernel: bcm47xx: Add custom TRX header option to kernel
Signed-off-by: Will Sheppard wshepp...@embedded-bits.co.uk --- .../patches-3.14/162-Belkin_custom_trx_magic.patch | 35 ++ 1 file changed, 35 insertions(+) create mode 100644 target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch diff --git a/target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch b/target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch new file mode 100644 index 000..eea7716 --- /dev/null +++ b/target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch @@ -0,0 +1,35 @@ +--- a/drivers/mtd/bcm47xxpart.c b/drivers/mtd/bcm47xxpart.c +@@ -42,7 +42,14 @@ + #define T_METER_MAGIC 0x4D54 /* MT */ + #define ML_MAGIC1 0x39685a42 + #define ML_MAGIC2 0x26594131 ++ ++ ++#ifdef CONFIG_TRX_MAGIC_OVERRIDE ++#define TRX_MAGIC (CONFIG_TRX_MAGIC) ++#else + #define TRX_MAGIC 0x30524448 ++#endif ++ + #define SHSQ_MAGIC0x71736873 /* shsq (weird ZTE H218N endianness) */ + #define UBI_EC_MAGIC 0x23494255 /* UBI# */ + +--- a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig +@@ -14,6 +14,15 @@ if MTD + + menu OpenWrt specific MTD options + ++config TRX_MAGIC_OVERRIDE ++ bool Override trx magic ++ default n ++ ++config TRX_MAGIC ++ hex Enter the magic... ++ depends on TRX_MAGIC_OVERRIDE ++ default 0x12345678 ++ + config MTD_ROOTFS_ROOT_DEV + bool Automatically set 'rootfs' partition to be root filesystem + default y -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 3/7] mtd: Fix: Use TRX_MAGIC define not hard-coded number
Signed-off-by: Will Sheppard wshepp...@embedded-bits.co.uk --- package/system/mtd/src/trx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/system/mtd/src/trx.c b/package/system/mtd/src/trx.c index 5d0f364..1722cf2 100644 --- a/package/system/mtd/src/trx.c +++ b/package/system/mtd/src/trx.c @@ -189,7 +189,7 @@ mtd_fixtrx(const char *mtd, size_t offset) } trx = (struct trx_header *) (buf + offset); - if (trx-magic != STORE32_LE(0x30524448)) { + if (trx-magic != STORE32_LE(TRX_MAGIC)) { fprintf(stderr, No trx magic found\n); exit(1); } -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] au1xxx v3.18
On 09/02/2015 21:56, Bruno Randolf wrote: [0.00] Kernel command line: root=/dev/mtdblock/0 console=ttyS0,115200 root=/dev/mtdblock0 rootfstype=squashfs,jffs2 what does that look like on 3.14 ? on mediatek the bug was that the wrong cmdline was used, causing a bad base_baud to be set in the 8250 driver ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] @44360 scripts
Hi, the subject is wonky On 09/02/2015 15:55, . wrote: From d1f104b6fe94507a80b85943fd1d4ba895f4e0a0 Mon Sep 17 00:00:00 2001 From: Detlef Schmitt blubb...@nurfuerspam.de not sure what to think of this email addr Date: Mon, 9 Feb 2015 15:35:28 +0100 Subject: [PATCH 2/2] daemon.notice netifd: wan (4235): udhcpc: option -h NAME is deprecated, use -x hostname:NAME daemon.notice netifd: wan (4235): udhcpc (v1.22.1) started replaced the deprecated option -h HOSTNAME for udhcpc with the new one the text is at least formatted in a very messy way and it seems to have part of an error and then part of a sentence John --- package/network/config/netifd/files/lib/netifd/proto/dhcp.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh index d4c483d..bde60a2 100755 --- a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh +++ b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh @@ -52,7 +52,7 @@ proto_dhcp_setup() { -s /lib/netifd/dhcp.script \ -f -t 0 -i $iface \ ${ipaddr:+-r $ipaddr} \ - ${hostname:+-H $hostname} \ + ${hostname:+-x hostname:$hostname} \ ${vendorid:+-V $vendorid} \ $clientid $broadcast $dhcpopts } ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] au1xxx v3.18
On 09/02/2015 21:56, Bruno Randolf wrote: Hi John, Something's wrong with the serial, but I was able to login via Ethernet. I did not verify PCI yet, as I only have a PCI adapter on the cubes which are in use. Serial log below: bruno On 02/09/2015 12:26 PM, John Crispin wrote: Hi Bruno, (or anyone else that has the hw at hand) i pushed the v3.18 support. could you test it please and let me know if it is working ? you need to set 3.18 in the Makefile, it is still at 3.14. [0.00] Linux version 3.18.6 (br1@shiva) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r44360) ) #1 Mon Feb 9 20:19:34 WET 2015 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 01030202 (Au1500) [0.00] 4G Systems MTX-1 Board [0.00] Determined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x03ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [0.00] Initmem setup node 0 [mem 0x-0x03ff] [0.00] Primary instruction cache 16kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: root=/dev/mtdblock/0 console=ttyS0,115200 root=/dev/mtdblock0 rootfstype=squashfs,jffs2 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Memory: 60556K/65536K available (2412K kernel code, 95K rwdata, 476K rodata, 144K init, 195K bss, 4980K reserved) [0.00] NR_IRQS:128 [0.00] Alchemy clocksource installed [0.004000] Calibrating delay loop... 395.26 BogoMIPS (lpj=790528) [0.04] pid_max: default: 32768 minimum: 301 [0.044000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.048000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.056000] NET: Registered protocol family 16 [0.06] Alchemy clocktree installed [0.064000] Alchemy DMA initialized [0.068000] alchemy-pci alchemy-pci.0: PCI controller at 32 MHz [0.10] PCI host bridge to bus :00 [0.104000] pci_bus :00: root bus resource [mem 0x4000-0x4fff] [0.108000] pci_bus :00: root bus resource [io 0x1000-0x] [0.112000] pci_bus :00: No busn resource found for root bus, will use [bus 00-ff] [0.116000] Switched to clocksource alchemy-counter1 [0.124000] NET: Registered protocol family 2 [0.128000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.136000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.144000] TCP: Hash tables configured (established 1024 bind 1024) [0.152000] TCP: reno registered [0.156000] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.16] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.168000] NET: Registered protocol family 1 [0.176000] futex hash table entries: 256 (order: -1, 3072 bytes) [0.188000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.192000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [0.216000] msgmni has been set to 118 [0.224000] io scheduler noop registered [0.228000] io scheduler deadline registered (default) [0.232000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.24] console [ttyS0] disabled [0.244000] serial8250.8: ttyS0 at MMIO 0x1110 (irq = 8, base_baud = 18187500) is a 16550A ��� ok, bad baudrate. i fixed this on mediatek in the upstream kernel for 3.16 or 17. need to think of what the issue was. it was easy to fix though. With 14.07 the last part looks like this: [0.18] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.192000] serial8250.8: ttyS0 at MMIO 0x1110 (irq = 8) is a 16550A [0.20] console [ttyS0] enabled, bootconsole disabled [0.20] console [ttyS0] enabled, bootconsole disabled [0.216000] serial8250.8: ttyS1 at MMIO 0x1140 (irq = 11) is a 16550A ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Support for DFS 5470 - 5725MHz DFS channels in US?
On 10.02.2015 05:32, Ben West wrote: I found on a UBNT Nanostation running BB r43824 that apparently only a subset of the DFS 5.8GHz channels are enabled. This matches the channel definitions in the reg DB file: https://dev.openwrt.org/browser/trunk/package/kernel/mac80211/files/regdb.txt What is the reason for keeping channels 5470 - 5725 disabled, when that range is enabled, for example, for country DE? People are operating UBNT products with stock firmware on these bands in the US. Different countries different regulatory rules. Upstream commit that removes 5470-5725 is: 31dc1c5eca29d039ac8f26340defe44bd7e497c1 This seems to be reverted by upstream with wireless-regdb (master-2015-01-30) [1] Updating the regdb should fix this. (I find no QCA feedback why this was introduced on the ML) [2] [1] http://marc.info/?l=linux-wirelessm=142263098201163 [2] http://lists.infradead.org/pipermail/wireless-regdb/2015-January/000717.html ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v1 2/7] mtd: Add custom trx magic option to mtd tool
Signed-off-by: Will Sheppard wshepp...@embedded-bits.co.uk --- package/system/mtd/Makefile | 8 +++- package/system/mtd/src/trx.c | 6 ++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/package/system/mtd/Makefile b/package/system/mtd/Makefile index 8d7bb44..91c4fac 100644 --- a/package/system/mtd/Makefile +++ b/package/system/mtd/Makefile @@ -39,7 +39,13 @@ endef target=$(firstword $(subst -, ,$(BOARD))) MAKE_FLAGS += TARGET=$(target) -TARGET_CFLAGS := $(TARGET_CFLAGS) -Dtarget_$(target)=1 -Wall + + +TARGET_CFLAGS := $(TARGET_CFLAGS) -Dtarget_$(target)=1 -Wall + +ifdef CONFIG_KERNEL_TRX_MAGIC_OVERRIDE + TARGET_CFLAGS += -DCONFIG_KERNEL_TRX_MAGIC_OVERRIDE -DCONFIG_KERNEL_TRX_MAGIC=$(CONFIG_KERNEL_TRX_MAGIC) +endif ifdef CONFIG_MTD_REDBOOT_PARTS MAKE_FLAGS += FIS_SUPPORT=1 diff --git a/package/system/mtd/src/trx.c b/package/system/mtd/src/trx.c index 089d1ac..5d0f364 100644 --- a/package/system/mtd/src/trx.c +++ b/package/system/mtd/src/trx.c @@ -34,7 +34,13 @@ #include mtd.h #include crc32.h +#ifndef CONFIG_KERNEL_TRX_MAGIC_OVERRIDE +#warning Using default TRX MAGIC #define TRX_MAGIC 0x30524448 /* HDR0 */ +#else +#warning mtd is using overridden TRX_MAGIC +#define TRX_MAGIC (CONFIG_KERNEL_TRX_MAGIC) +#endif struct trx_header { uint32_t magic; /* HDR0 */ uint32_t len; /* Length of file including header */ -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On Mon, 2015-02-09 at 13:30 +0100, John Crispin wrote: Hi, i bumped the lantiq support to v3.18 and tested it on 6 different boards. I have not tested vdsl support due to lack of a vdsl line. could someone please do so. @antii: can you rebase/resnd the dwc2 series ? it does not apply to the v3.18 patches John Build now fails for AR9. Relevant log: scripts/kconfig/conf --silentoldconfig Kconfig net/sched/Kconfig:43: warning: menuconfig statement without prompt * * Restart config... * * * Staging drivers * Staging drivers (STAGING) [Y/n/?] y Data acquisition support (comedi) (COMEDI) [N/m/?] n RealTek RTL8192U Wireless LAN NIC driver (RTL8192U) [N/m/?] n Support for rtllib wireless devices (RTLLIB) [N/m/?] n RealTek RTL8712U (RTL8192SU) Wireless LAN NIC driver (R8712U) [N/m/y/?] n Realtek RTL8188EU Wireless LAN NIC driver (R8188EU) [N/m/y/?] n Realtek RTL8723AU Wireless LAN NIC driver (R8723AU) [N/m/?] (NEW) aborted! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] BB:ramips:Kingston MLW221 cleanup
MLW221 dts use tabs NOT spaces. Cleanup uci-defaults and diag.sh Signed-off-by: L. D. Pinney ldpin...@gmail.com --- target/linux/ramips/base-files/etc/diag.sh | 4 +- target/linux/ramips/base-files/etc/uci-defaults/01_leds| 5 +- target/linux/ramips/base-files/etc/uci-defaults/02_network | 5 +- target/linux/ramips/dts/MLW221.dts | 226 +- 4 files changed, 116 insertions(+), 124 deletions(-) diff --git a/target/linux/ramips/base-files/etc/diag.sh b/target/linux/ramips/base-files/etc/diag.sh index bd3779a..74b8867 100755 --- a/target/linux/ramips/base-files/etc/diag.sh +++ b/target/linux/ramips/base-files/etc/diag.sh @@ -73,9 +73,7 @@ get_status_led() { m4) status_led=m4:blue:status ;; - mlw221) - status_led=kingston:blue:status - ;; + mlw221|\ mlwg2) status_led=kingston:blue:system ;; diff --git a/target/linux/ramips/base-files/etc/uci-defaults/01_leds b/target/linux/ramips/base-files/etc/uci-defaults/01_leds index f5b5b01..5d6ed2b 100755 --- a/target/linux/ramips/base-files/etc/uci-defaults/01_leds +++ b/target/linux/ramips/base-files/etc/uci-defaults/01_leds @@ -113,10 +113,7 @@ case $board in hw550-3g) set_usb_led hw550-3g:green:usb ;; - mlw221) - set_wifi_led kingston:blue:wifi - ucidef_set_led_default system system kingston:blue:system 1 - ;; + mlw221|\ mlwg2) set_wifi_led kingston:blue:wifi ucidef_set_led_default system system kingston:blue:system 1 diff --git a/target/linux/ramips/base-files/etc/uci-defaults/02_network b/target/linux/ramips/base-files/etc/uci-defaults/02_network index 91bedcc..c3ea489 100755 --- a/target/linux/ramips/base-files/etc/uci-defaults/02_network +++ b/target/linux/ramips/base-files/etc/uci-defaults/02_network @@ -55,10 +55,7 @@ ramips_setup_interfaces() ucidef_set_interface_lan eth0.2 ;; - mlwg2) -ucidef_set_interface_lan eth0.1 -;; - + mlwg2 | \ wl-330n | \ wmr300) ucidef_set_interface_lan eth0.1 diff --git a/target/linux/ramips/dts/MLW221.dts b/target/linux/ramips/dts/MLW221.dts index f220e97..83467dc 100644 --- a/target/linux/ramips/dts/MLW221.dts +++ b/target/linux/ramips/dts/MLW221.dts @@ -3,117 +3,117 @@ /include/ mt7620n.dtsi / { - compatible = mlw221, ralink,mt7620n-soc; - model = Kingston MLW221; - - palmbus@1000 { - gpio0: gpio@600 { - status = okay; - }; - - gpio2: gpio@660 { - status = okay; - }; - - gpio3: gpio@688 { - status = okay; - }; - - spi@b00 { - status = okay; - - m25p80@0 { - #address-cells = 1; - #size-cells = 1; - compatible = s25fl129p1; - reg = 0 0; - linux,modalias = m25p80, s25fl129p1; - spi-max-frequency = 1000; - - partition@0 { - label = u-boot; - reg = 0x0 0x3; - read-only; - }; - - partition@3 { - label = u-boot-env; - reg = 0x3 0x1; - read-only; - }; - - factory: partition@4 { - label = factory; - reg = 0x4 0x1; - read-only; - }; - - partition@5 { - label = firmware; - reg = 0x5 0xf6; - }; - - partition@fb { - label = user-config; - reg = 0xfb 0x5; - - }; - }; - }; - }; - - ehci@101c { - status = okay; - }; - - ohci@101c1000 { - status = okay; - }; - - ethernet@1010 { - mtd-mac-address = factory 0x4; - ralink,port-map = w; - }; - - wmac@1018 { -
Re: [OpenWrt-Devel] raspberry pi v3.19
On 09/02/2015 18:12, Florian Fainelli wrote: Could you share the boot log to see if there is anything obvious? Hi, without uart i get no bootlog. i just see the coloured palette on the hdmi. but the uart stays quiet. i am starting to wonder if the uart is dead. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
there is no ar9 target. can you give me your .config file please ? On 09/02/2015 18:30, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 13:30 +0100, John Crispin wrote: Hi, i bumped the lantiq support to v3.18 and tested it on 6 different boards. I have not tested vdsl support due to lack of a vdsl line. could someone please do so. @antii: can you rebase/resnd the dwc2 series ? it does not apply to the v3.18 patches John Build now fails for AR9. Relevant log: scripts/kconfig/conf --silentoldconfig Kconfig net/sched/Kconfig:43: warning: menuconfig statement without prompt * * Restart config... * * * Staging drivers * Staging drivers (STAGING) [Y/n/?] y Data acquisition support (comedi) (COMEDI) [N/m/?] n RealTek RTL8192U Wireless LAN NIC driver (RTL8192U) [N/m/?] n Support for rtllib wireless devices (RTLLIB) [N/m/?] n RealTek RTL8712U (RTL8192SU) Wireless LAN NIC driver (R8712U) [N/m/y/?] n Realtek RTL8188EU Wireless LAN NIC driver (R8188EU) [N/m/y/?] n Realtek RTL8723AU Wireless LAN NIC driver (R8723AU) [N/m/?] (NEW) aborted! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On 09/02/2015 18:30, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 13:30 +0100, John Crispin wrote: Hi, i bumped the lantiq support to v3.18 and tested it on 6 different boards. I have not tested vdsl support due to lack of a vdsl line. could someone please do so. @antii: can you rebase/resnd the dwc2 series ? it does not apply to the v3.18 patches John Build now fails for AR9. Relevant log: scripts/kconfig/conf --silentoldconfig Kconfig net/sched/Kconfig:43: warning: menuconfig statement without prompt * * Restart config... * * * Staging drivers * Staging drivers (STAGING) [Y/n/?] y Data acquisition support (comedi) (COMEDI) [N/m/?] n RealTek RTL8192U Wireless LAN NIC driver (RTL8192U) [N/m/?] n Support for rtllib wireless devices (RTLLIB) [N/m/?] n RealTek RTL8712U (RTL8192SU) Wireless LAN NIC driver (R8712U) [N/m/y/?] n Realtek RTL8188EU Wireless LAN NIC driver (R8188EU) [N/m/y/?] n Realtek RTL8723AU Wireless LAN NIC driver (R8723AU) [N/m/?] (NEW) aborted! try r44366 or newer please ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] raspberry pi v3.19
I tried adding support for 3.18 and I have issues booting the raspberry. There must be something wrong with the new mmc driver, because it detects the SD card insertions/extractiones, but doesn't read the partitions: http://pastebin.com/GWFYrXnT My patches: http://files.noltari.es/openwrt/bcm2708/brcm2708_3-18.tgz Regards, Álvaro. El 09/02/2015 a las 18:12, Florian Fainelli escribió: On Feb 9, 2015 4:25 AM, John Crispin blo...@openwrt.org mailto:blo...@openwrt.org wrote: Hi, i synced our rpi port with the upstream tree on github. it boots and i can see the coloured palette test pic on the hdmi, however ethernet fails to come up. i attached a uart just to find out that my rpi is either broken or i am connecting it wrong. has anyone managed to get uart working ? to my understanding i need to connect pin6 to gnd and use 8 and 10 for the 2 data lines. should i see output from the bootloader prior to board detecting/loading the sd card You will not get any UART output prior to the kernel boot, the GPU boot code does not output anything (at least not in the builds we use). Could you share the boot log to see if there is anything obvious? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
bootlog please On 09/02/2015 21:25, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 19:18 +0100, John Crispin wrote: try r44366 or newer please SPI flash is not detected, bricking the device. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v1 0/7] Add custom TRX header option
On 09/02/15 08:29, Will Sheppard wrote: Patchset to essentially add custom TRX header to all firmware produced. This is most useful for the Belkin routers from my experience. I'm not how other trx based firmwares modify the header for their own purposes. This is applied across the board so that the kernel, trx tools and mtd tools are all compiled with the specified header. I have modified the kernel specifically for the brcm47xx based boards to ensure the mtd parser looks for the correct magic. NOTE: This function will, for other boards, fail. I don't think this is desirable at all to have, for many reasons: - how can an use figure out the proper TRX_MAGIC value he/she should use? - this is extremely error prone and can result, as you mention in failing to work with existing devices with well-defined TRX headers - how can we get some level of reproducibility for both the kernel and firmware tools builds? I would really encourage you to extend the existing code to take an arbitrary list of TRX magics, such that you can have maybe a single file to modify and both mtd and the kernel can use that list of magic values accordingly. Out of curiosity, how many different TRX magic values should we have to support with or without your patches? Will Sheppard (7): config: Add option to specify custom TRX header mtd: Add custom trx magic option to mtd tool mtd: Fix: Use TRX_MAGIC define not hard-coded number trx: Add custom TRX option to trx firmware tool mtd: Add debug showing header magic in use kernel: bcm47xx: Add custom TRX header option to kernel mtd: Fix makefile to work with quilt as per wiki config/Config-images.in| 15 ++ package/system/mtd/Makefile| 9 +- package/system/mtd/src/trx.c | 10 +-- .../patches-3.14/162-Belkin_custom_trx_magic.patch | 35 ++ tools/firmware-utils/Makefile | 4 +++ tools/firmware-utils/src/trx.c | 10 ++- 6 files changed, 79 insertions(+), 4 deletions(-) create mode 100644 target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Failsafe broken on Nexx WT3020
Hi, I am asking for help on https://dev.openwrt.org/ticket/18768 Failsafe mode appears to be broken on the Nexx WT3020 as of r43977. I suspect that TCP connections are not working when VLAN is disabled just like on other MediaTek/Ralink chipsets. Can someone please have a look? Thanks, probono ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] A5-V11 images are missing in snapshots
Hi, what is needed to get a certain target board into the snapshots? Specifically, A5-V11 images are missing in the ramips-rt305x snapshots on http://downloads.openwrt.org/snapshots/trunk/ramips/generic/ as described in https://dev.openwrt.org/ticket/18712 Thanks, probono ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On Mon, 2015-02-09 at 19:18 +0100, John Crispin wrote: try r44366 or newer please SPI flash is not detected, bricking the device. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
On Mon, 2015-02-09 at 21:27 +0100, John Crispin wrote: bootlog please On 09/02/2015 21:25, Daniel Gimpelevich wrote: On Mon, 2015-02-09 at 19:18 +0100, John Crispin wrote: try r44366 or newer please SPI flash is not detected, bricking the device. [0.00] Linux version 3.18.6 (danielg4@chimera) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r43982) ) #3 Mon Feb 9 115 [0.00] SoC: AR9 rev 1.2 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 0001954c (MIPS 34Kc) [0.00] MIPS: machine is DGN3500 - Netgear DGN3500 [0.00] Determined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] User-defined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x03ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [0.00] Initmem setup node 0 [mem 0x-0x03ff] [0.00] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: root=/dev/mtdblock0 ip=192.168.1.1:192.168.1.15eth0:on console=ttyS1,115200 ethaddr=30:46:90 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Writing ErrCtl register=5880 [0.00] Readback ErrCtl register=5880 [0.00] Memory: 60404K/65536K available (3312K kernel code, 147K rwdata, 664K rodata, 144K init, 194K bss, 5132K reserved) [0.00] NR_IRQS:256 [0.00] CPU Clock: 333MHz [0.00] Calibrating delay loop... 221.18 BogoMIPS (lpj=442368) [0.036000] pid_max: default: 32768 minimum: 301 [0.04] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.044000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.052000] pinctrl core: initialized pinctrl subsystem [0.056000] NET: Registered protocol family 16 [0.064000] pinctrl-xway 1e100b10.pinmux: Init done [0.068000] dma-xway 1e104100.dma: Init done - hw rev: 6, ports: 5, channels: 20 [0.076000] PCI host bridge /fpi@1000/pci@E105400 ranges: [0.08] MEM 0x1800..0x19ff [0.084000] IO 0x1ae0..0x1aff [0.088000] ath9k,eeprom ath9k_eep: failed to load eeprom address [0.10] usbcore: registered new interface driver usbfs [0.104000] usbcore: registered new interface driver hub [0.108000] usbcore: registered new device driver usb [0.112000] PCI host bridge to bus :00 [0.116000] pci_bus :00: root bus resource [mem 0x1800-0x19ff] [0.12] pci_bus :00: root bus resource [io 0x] [0.124000] pci_bus :00: No busn resource found for root bus, will use [bus 00-ff] [0.128000] pci :00:0e.0: BAR 0: assigned [mem 0x1800-0x1800] [0.132000] Switched to clocksource MIPS [0.136000] NET: Registered protocol family 2 [0.144000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.148000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.156000] TCP: Hash tables configured (established 1024 bind 1024) [0.164000] TCP: reno registered [0.164000] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.172000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.18] NET: Registered protocol family 1 [0.184000] gptu: totally 6 16-bit timers/counters [0.188000] gptu: misc_register on minor 63 [0.192000] gptu: succeeded to request irq 126 [0.196000] gptu: succeeded to request irq 127 [0.20] gptu: succeeded to request irq 128 [0.204000] gptu: succeeded to request irq 129 [0.212000] gptu: succeeded to request irq 130 [0.216000] gptu: succeeded to request irq 131 [0.22] futex hash table entries: 256 (order: -1, 3072 bytes) [0.228000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.236000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [0.248000] msgmni has been set to 117 [0.252000] io scheduler noop registered [0.256000] io scheduler deadline registered (default) [0.26] 1e100c00.serial: ttyLTQ0 at MMIO 0x1e100c00 (irq = 112, base_baud = 0) is a lantiq,asc [0.268000] console [ttyLTQ0] enabled [0.268000] console [ttyLTQ0] enabled [0.276000] bootconsole [early0] disabled [0.276000] bootconsole [early0] disabled [0.332000] Realtek RTL8366RB ethernet switch
Re: [OpenWrt-Devel] [PATCH v1 0/7] Add custom TRX header option
Hi - thanks for review; reply inline On 9 February 2015 at 20:52, Florian Fainelli flor...@openwrt.org wrote: On 09/02/15 08:29, Will Sheppard wrote: Patchset to essentially add custom TRX header to all firmware produced. This is most useful for the Belkin routers from my experience. I'm not how other trx based firmwares modify the header for their own purposes. This is applied across the board so that the kernel, trx tools and mtd tools are all compiled with the specified header. I have modified the kernel specifically for the brcm47xx based boards to ensure the mtd parser looks for the correct magic. NOTE: This function will, for other boards, fail. I don't think this is desirable at all to have, for many reasons: - how can an use figure out the proper TRX_MAGIC value he/she should use? There's simply no hard-and-fast rule for this - just looking at a factory binary might not help - it worked for me. - this is extremely error prone and can result, as you mention in failing to work with existing devices with well-defined TRX headers Error prone inasmuch as it could be the wrong value and thus brick the router? ( I guess I'm always thinking from a have a serial port perspective ) - how can we get some level of reproducibility for both the kernel and firmware tools builds? I would really encourage you to extend the existing code to take an arbitrary list of TRX magics, such that you can have maybe a single file to modify and both mtd and the kernel can use that list of magic values accordingly. I agree. As the mtd utility looks for this value though, it would have to know what router it was being used on - i'm not sure that is available as a value in user-space is it? Out of curiosity, how many different TRX magic values should we have to support with or without your patches? I know that Belkin seem to use different magics i.e. not HDR0, I'm not sure about other manufacturers. But presumably these values could be added as they become known. Will Sheppard (7): config: Add option to specify custom TRX header mtd: Add custom trx magic option to mtd tool mtd: Fix: Use TRX_MAGIC define not hard-coded number trx: Add custom TRX option to trx firmware tool mtd: Add debug showing header magic in use kernel: bcm47xx: Add custom TRX header option to kernel mtd: Fix makefile to work with quilt as per wiki config/Config-images.in| 15 ++ package/system/mtd/Makefile| 9 +- package/system/mtd/src/trx.c | 10 +-- .../patches-3.14/162-Belkin_custom_trx_magic.patch | 35 ++ tools/firmware-utils/Makefile | 4 +++ tools/firmware-utils/src/trx.c | 10 ++- 6 files changed, 79 insertions(+), 4 deletions(-) create mode 100644 target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] au1xxx v3.18
Hi John, Something's wrong with the serial, but I was able to login via Ethernet. I did not verify PCI yet, as I only have a PCI adapter on the cubes which are in use. Serial log below: bruno On 02/09/2015 12:26 PM, John Crispin wrote: Hi Bruno, (or anyone else that has the hw at hand) i pushed the v3.18 support. could you test it please and let me know if it is working ? you need to set 3.18 in the Makefile, it is still at 3.14. [0.00] Linux version 3.18.6 (br1@shiva) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r44360) ) #1 Mon Feb 9 20:19:34 WET 2015 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 01030202 (Au1500) [0.00] 4G Systems MTX-1 Board [0.00] Determined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Zone ranges: [0.00] Normal [mem 0x-0x03ff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x03ff] [0.00] Initmem setup node 0 [mem 0x-0x03ff] [0.00] Primary instruction cache 16kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [0.00] Kernel command line: root=/dev/mtdblock/0 console=ttyS0,115200 root=/dev/mtdblock0 rootfstype=squashfs,jffs2 [0.00] PID hash table entries: 256 (order: -2, 1024 bytes) [0.00] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.00] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.00] Memory: 60556K/65536K available (2412K kernel code, 95K rwdata, 476K rodata, 144K init, 195K bss, 4980K reserved) [0.00] NR_IRQS:128 [0.00] Alchemy clocksource installed [0.004000] Calibrating delay loop... 395.26 BogoMIPS (lpj=790528) [0.04] pid_max: default: 32768 minimum: 301 [0.044000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.048000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.056000] NET: Registered protocol family 16 [0.06] Alchemy clocktree installed [0.064000] Alchemy DMA initialized [0.068000] alchemy-pci alchemy-pci.0: PCI controller at 32 MHz [0.10] PCI host bridge to bus :00 [0.104000] pci_bus :00: root bus resource [mem 0x4000-0x4fff] [0.108000] pci_bus :00: root bus resource [io 0x1000-0x] [0.112000] pci_bus :00: No busn resource found for root bus, will use [bus 00-ff] [0.116000] Switched to clocksource alchemy-counter1 [0.124000] NET: Registered protocol family 2 [0.128000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [0.136000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [0.144000] TCP: Hash tables configured (established 1024 bind 1024) [0.152000] TCP: reno registered [0.156000] UDP hash table entries: 256 (order: 0, 4096 bytes) [0.16] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [0.168000] NET: Registered protocol family 1 [0.176000] futex hash table entries: 256 (order: -1, 3072 bytes) [0.188000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.192000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [0.216000] msgmni has been set to 118 [0.224000] io scheduler noop registered [0.228000] io scheduler deadline registered (default) [0.232000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.24] console [ttyS0] disabled [0.244000] serial8250.8: ttyS0 at MMIO 0x1110 (irq = 8, base_baud = 18187500) is a 16550A ��� With 14.07 the last part looks like this: [0.18] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [0.192000] serial8250.8: ttyS0 at MMIO 0x1110 (irq = 8) is a 16550A [0.20] console [ttyS0] enabled, bootconsole disabled [0.20] console [ttyS0] enabled, bootconsole disabled [0.216000] serial8250.8: ttyS1 at MMIO 0x1140 (irq = 11) is a 16550A ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ar71xx: ZyXEL NBG6716 leds improvement ( correction - second attempt )
the 3 patches sent are white space broken and patchwork failed to pick them up. i have manually applied this patch, but please use git for sending patches in future. On 06/02/2015 12:27, Marcin Mikołajczak wrote: This patch fixes LEDs in ZyXEL NBG6716 - POWER LED was missing - USB LEDs incorrect order Signed-off-by: Marcin Mikolajczak gr4ffy at gmail.com --- Sorry, but this is my first patch for OpenWrt - previous one was splitted in two half. Index: trunk/target/linux/ar71xx/base-files/etc/diag.sh === --- trunk/target/linux/ar71xx/base-files/etc/diag.sh(wersja 44288) +++ trunk/target/linux/ar71xx/base-files/etc/diag.sh(kopia robocza) @@ -130,7 +130,7 @@ status_led=nbg460n:green:power ;; nbg6716) - status_led=nbg6716:white:power + status_led=zyxel:white:power ;; om2p | \ om2pv2 | \ Index: trunk/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds === --- trunk/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (wersja 44288) +++ trunk/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds (kopia robocza) @@ -215,8 +215,8 @@ ucidef_set_led_netdev wan WAN zyxel:white:internet eth1 ucidef_set_led_wlan wlan WLAN zyxel:white:wifi2g phy1tpt ucidef_set_led_wlan wlan5 WLAN5 zyxel:white:wifi5g phy0tpt - ucidef_set_led_usbdev usb1 USB1 zyxel:white:usb0 1-1 - ucidef_set_led_usbdev usb2 USB2 zyxel:white:usb1 2-1 + ucidef_set_led_usbdev usb1 USB1 zyxel:white:usb0 2-1 + ucidef_set_led_usbdev usb2 USB2 zyxel:white:usb1 1-1 ;; om2p | \ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v1 0/7] Add custom TRX header option
On 09/02/15 13:12, Will Sheppard wrote: Hi - thanks for review; reply inline On 9 February 2015 at 20:52, Florian Fainelli flor...@openwrt.org mailto:flor...@openwrt.org wrote: On 09/02/15 08:29, Will Sheppard wrote: Patchset to essentially add custom TRX header to all firmware produced. This is most useful for the Belkin routers from my experience. I'm not how other trx based firmwares modify the header for their own purposes. This is applied across the board so that the kernel, trx tools and mtd tools are all compiled with the specified header. I have modified the kernel specifically for the brcm47xx based boards to ensure the mtd parser looks for the correct magic. NOTE: This function will, for other boards, fail. I don't think this is desirable at all to have, for many reasons: - how can an use figure out the proper TRX_MAGIC value he/she should use? There's simply no hard-and-fast rule for this - just looking at a factory binary might not help - it worked for me. That was more of a rhetorical question, since this is not easy, someone has to do it, and preferably in a way that makes the build reliable for end-users. - this is extremely error prone and can result, as you mention in failing to work with existing devices with well-defined TRX headers Error prone inasmuch as it could be the wrong value and thus brick the router? ( I guess I'm always thinking from a have a serial port perspective ) Error prone on multiple levels: what happens if I wipe-out my original config and can't remember the correct 32-bits magic value? What if the option is renamed, what I upgrade the kernel but not mtd, etc... - how can we get some level of reproducibility for both the kernel and firmware tools builds? I would really encourage you to extend the existing code to take an arbitrary list of TRX magics, such that you can have maybe a single file to modify and both mtd and the kernel can use that list of magic values accordingly. I agree. As the mtd utility looks for this value though, it would have to know what router it was being used on - i'm not sure that is available as a value in user-space is it? You can certainly extract the board you are running on, but that assumes you already have a working user-space and kernel, hence the partition parser needs to work etc... chicken and egg. The alternative, which is likely what is happening today, is that you need to flash a special image, with a special magic that only supports a particular set of boards using a defined TRX magic value, that way you can become (at least at the MTD level) board agnostic. Out of curiosity, how many different TRX magic values should we have to support with or without your patches? I know that Belkin seem to use different magics i.e. not HDR0, I'm not sure about other manufacturers. But presumably these values could be added as they become known. That is the direction I would take, just add them one by one such that you can control exactly when both user-space and kernel space can properly support a given model (or family of). Will Sheppard (7): config: Add option to specify custom TRX header mtd: Add custom trx magic option to mtd tool mtd: Fix: Use TRX_MAGIC define not hard-coded number trx: Add custom TRX option to trx firmware tool mtd: Add debug showing header magic in use kernel: bcm47xx: Add custom TRX header option to kernel mtd: Fix makefile to work with quilt as per wiki config/Config-images.in| 15 ++ package/system/mtd/Makefile| 9 +- package/system/mtd/src/trx.c | 10 +-- .../patches-3.14/162-Belkin_custom_trx_magic.patch | 35 ++ tools/firmware-utils/Makefile | 4 +++ tools/firmware-utils/src/trx.c | 10 ++- 6 files changed, 79 insertions(+), 4 deletions(-) create mode 100644 target/linux/brcm47xx/patches-3.14/162-Belkin_custom_trx_magic.patch ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel: add missing symbol
Signed-off-by: Daniel Golle dan...@makrotopia.org --- target/linux/generic/config-3.18 | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/generic/config-3.18 b/target/linux/generic/config-3.18 index b831223..52cc3b0 100644 --- a/target/linux/generic/config-3.18 +++ b/target/linux/generic/config-3.18 @@ -3948,6 +3948,7 @@ CONFIG_TMPFS_XATTR=y # CONFIG_TPS65010 is not set # CONFIG_TPS6507X is not set # CONFIG_TR is not set +# CONFIG_TRACEPOINT_BENCHMARK is not set # CONFIG_TRACER_SNAPSHOT is not set # CONFIG_TRACER_SNAPSHOT_PER_CPU_SWAP is not set # CONFIG_TRACE_BRANCH_PROFILING is not set -- 2.2.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] oxnas: switch to 3.18
Tested on stg212 and kd20. Signed-off-by: Daniel Golle dan...@makrotopia.org --- target/linux/oxnas/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/oxnas/Makefile b/target/linux/oxnas/Makefile index 05ae8cf..186222d 100644 --- a/target/linux/oxnas/Makefile +++ b/target/linux/oxnas/Makefile @@ -15,7 +15,7 @@ CPU_TYPE:=mpcore MAINTAINER:=Daniel Golle dan...@makrotopia.org -KERNEL_PATCHVER:=3.14 +KERNEL_PATCHVER:=3.18 include $(INCLUDE_DIR)/target.mk -- 2.2.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: add mc-mac1200r to do_load_ath10k_board_bin()
This patch adds the mc-mac1200r target to do_load_ath10k_board_bin() in target/linux/ar71xx/base-files/lib/preinit/81_load_ath10k_board_bin to load the ath10k radio MAC address from the EEPROM in MERCURY MAC1200R devices Signed-off-by: Roger Pueyo Centelles roger.pu...@guifi.net --- .../ar71xx/base-files/lib/preinit/81_load_ath10k_board_bin| 11 +++ 1 file changed, 11 insertions(+) diff --git a/target/linux/ar71xx/base-files/lib/preinit/81_load_ath10k_board_bin b/target/linux/ar71xx/base-files/lib/preinit/81_load_ath10k_board_bin index 7190820..9a32dfc 100644 --- a/target/linux/ar71xx/base-files/lib/preinit/81_load_ath10k_board_bin +++ b/target/linux/ar71xx/base-files/lib/preinit/81_load_ath10k_board_bin @@ -23,6 +23,17 @@ do_load_ath10k_board_bin() { dd if=/dev/mtdblock4 \ bs=1 skip=20492 count=2104 /tmp/ath10k-board.bin ;; + mc-mac1200r) + local mac + mac=$(macaddr_add $(cat /sys/class/net/eth1/address) -1) + + dd if=/dev/mtdblock4 \ + bs=1 skip=20480 count=6 \ + of=/tmp/ath10k-board.bin + macaddr_2bin $mac /tmp/ath10k-board.bin + dd if=/dev/mtdblock4 \ + bs=1 skip=20492 count=2104 /tmp/ath10k-board.bin + ;; r6100) local mac mac=$(macaddr_add $(cat /sys/class/net/eth1/address) +2) -- 2.1.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] raspberry pi v3.19
Hi, i synced our rpi port with the upstream tree on github. it boots and i can see the coloured palette test pic on the hdmi, however ethernet fails to come up. i attached a uart just to find out that my rpi is either broken or i am connecting it wrong. has anyone managed to get uart working ? to my understanding i need to connect pin6 to gnd and use 8 and 10 for the 2 data lines. should i see output from the bootloader prior to board detecting/loading the sd card ? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] More bad RPATH
On 09/02/2015 14:07, Etienne Champetier wrote: Hi 2015-02-09 14:01 GMT+01:00 John Crispin blo...@openwrt.org mailto:blo...@openwrt.org: On 09/02/2015 13:57, Etienne Champetier wrote: Hi all, To follow r44328 (https://dev.openwrt.org/browser/trunk?rev=44328) (jow fix for cmake RPATH) I've launched a full build of ar71xx to check all bin/lib for bad RPATH # cd ./staging_dir/target-mips_34kc_uClibc-0.9.33.2/root-ar71xx # find . -type f | xargs -n1 -P24 file | grep ': ELF' | awk -F':' '{print $1}' | xargs -n1 ./checksec.sh --file | grep -v 'STACK CANARY' checksec.txt # awk '{print $NF}' checksec.txt lib.txt # awk '{print $NF}' checksec.txt | xargs -n1 readelf -a | grep RPATH | awk -F'[' '{print [$2}' rpath.txt you can merge libs.txt and rpath.txt with # paste lib.txt rpath.txt I will try to fix later Also i think we should have a test that fail the build if there is builroot path in the RPATH Regards Etienne can you build a script to turns this into a list of package names that are effected ? I'll try, but not before tonight $root/var/lib/opkg/* has files that will help you map the file-ipkg/package John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq v3.18
I'll test it today. 9 lut 2015 13:30 John Crispin blo...@openwrt.org napisał(a): Hi, i bumped the lantiq support to v3.18 and tested it on 6 different boards. I have not tested vdsl support due to lack of a vdsl line. could someone please do so. @antii: can you rebase/resnd the dwc2 series ? it does not apply to the v3.18 patches John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] @44360 scripts
From d1f104b6fe94507a80b85943fd1d4ba895f4e0a0 Mon Sep 17 00:00:00 2001 From: Detlef Schmitt blubb...@nurfuerspam.de Date: Mon, 9 Feb 2015 15:35:28 +0100 Subject: [PATCH 2/2] daemon.notice netifd: wan (4235): udhcpc: option -h NAME is deprecated, use -x hostname:NAME daemon.notice netifd: wan (4235): udhcpc (v1.22.1) started replaced the deprecated option -h HOSTNAME for udhcpc with the new one --- package/network/config/netifd/files/lib/netifd/proto/dhcp.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh index d4c483d..bde60a2 100755 --- a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh +++ b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh @@ -52,7 +52,7 @@ proto_dhcp_setup() { -s /lib/netifd/dhcp.script \ -f -t 0 -i $iface \ ${ipaddr:+-r $ipaddr} \ - ${hostname:+-H $hostname} \ + ${hostname:+-x hostname:$hostname} \ ${vendorid:+-V $vendorid} \ $clientid $broadcast $dhcpopts } -- 1.9.1 Signed-off-by: Detlef Schmitt blubb...@nurfuerspam.de ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] raspberry pi v3.19
ok, so uart, how do you connect it ? On 10/02/2015 02:02, Álvaro Fernández Rojas wrote: I tried adding support for 3.18 and I have issues booting the raspberry. There must be something wrong with the new mmc driver, because it detects the SD card insertions/extractiones, but doesn't read the partitions: http://pastebin.com/GWFYrXnT My patches: http://files.noltari.es/openwrt/bcm2708/brcm2708_3-18.tgz Regards, Álvaro. El 09/02/2015 a las 18:12, Florian Fainelli escribió: On Feb 9, 2015 4:25 AM, John Crispin blo...@openwrt.org mailto:blo...@openwrt.org wrote: Hi, i synced our rpi port with the upstream tree on github. it boots and i can see the coloured palette test pic on the hdmi, however ethernet fails to come up. i attached a uart just to find out that my rpi is either broken or i am connecting it wrong. has anyone managed to get uart working ? to my understanding i need to connect pin6 to gnd and use 8 and 10 for the 2 data lines. should i see output from the bootloader prior to board detecting/loading the sd card You will not get any UART output prior to the kernel boot, the GPU boot code does not output anything (at least not in the builds we use). Could you share the boot log to see if there is anything obvious? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Support for DFS 5470 - 5725MHz DFS channels in US?
I found on a UBNT Nanostation running BB r43824 that apparently only a subset of the DFS 5.8GHz channels are enabled. Frequencies: * 5180 MHz [36] (17.0 dBm) * 5200 MHz [40] (17.0 dBm) * 5220 MHz [44] (17.0 dBm) * 5240 MHz [48] (17.0 dBm) * 5260 MHz [52] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 730 sec) * 5280 MHz [56] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 730 sec) * 5300 MHz [60] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 730 sec) * 5320 MHz [64] (23.0 dBm) (no IR, radar detection) DFS state: usable (for 730 sec) * 5500 MHz [100] (disabled) * 5520 MHz [104] (disabled) * 5540 MHz [108] (disabled) * 5560 MHz [112] (disabled) * 5580 MHz [116] (disabled) * 5600 MHz [120] (disabled) * 5620 MHz [124] (disabled) * 5640 MHz [128] (disabled) * 5660 MHz [132] (disabled) * 5680 MHz [136] (disabled) * 5700 MHz [140] (disabled) * 5745 MHz [149] (30.0 dBm) * 5765 MHz [153] (30.0 dBm) * 5785 MHz [157] (30.0 dBm) * 5805 MHz [161] (30.0 dBm) * 5825 MHz [165] (30.0 dBm) This matches the channel definitions in the reg DB file: https://dev.openwrt.org/browser/trunk/package/kernel/mac80211/files/regdb.txt What is the reason for keeping channels 5470 - 5725 disabled, when that range is enabled, for example, for country DE? People are operating UBNT products with stock firmware on these bands in the US. This table below represents my current understanding of permissible use of the DFS channels in the US: *Point-to-MultiPoint* *Band* *Lower Frequency* *Upper Frequency* *FCC Reg* *Max Power (dBm)* *Notes* 900 MHz 902.0MHz 928.0MHz Part 15.247 (b)(3) , (b)(4) 36dBm 2.4 GHz 2400.0MHz 2483.5MHz Part 15.247 (b)(3) , (b)(4) 36dBm 5.1 GHz UNII Low 5150.0MHz 5250.0MHz Part 15.407 (a)(1), (e) 36dBm 5.3 GHz UNII Mid 5250.0MHz 5350.0MHz Part 15.407 (a)(2), (h)(2) 30dBm Requires DFS radar det. 5.4 GHz UNII DFS 5470.0MHz 5725.0MHz Part 15.407 (a)(2), (h)(2) 30dBm Requires DFS radar det. 5.8 GHz UNII Upper 5725.0MHz 5875.5MHz Part 15.247 (b)(3) , (b)(4) 36dBm Part 15.407 (a)(3) -- Ben West http://gowasabi.net b...@gowasabi.net 314-246-9434 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel