[OpenWrt-Devel] kirkwood not booting / goflex net / goflex home
while investigating the hanging boot/kernel on goflex home i see commit r38279 / d8eb02a921fa2c06118347231f3fd69285b8a5c7 kirkwood: prepare for 3.10 which removed target/linux/kirkwood/files-3.3/arch/arm/mach-kirkwood/goflexhome-setup.c is'nt it need for 3.10+ or what was the reason for removing that? see also: https://dev.openwrt.org/ticket/14938 bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] dnsmasq 2.71 dies silently (hangs) / how to debug
On another note: I just backported an upstream fix for a race condition. Might be related to this issue or might not. Please try to test with latest trunk or bb-branch. Cheers, Steven ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] kirkwood / missing kernel-module?
during boot i see in a long loop these messages, which kernel module is missing or which symbol must be active? (kernel 3.14.17) [ 86.817858] act_ipt: Unknown symbol tcf_hash_check (err 0) [ 86.823424] act_ipt: Unknown symbol tcf_hash_create (err 0) [ 86.829162] act_ipt: Unknown symbol tcf_unregister_action (err 0) [ 86.835324] act_ipt: Unknown symbol tcf_hash_insert (err 0) [ 86.840990] act_ipt: Unknown symbol tcf_register_action (err 0) [ 86.847036] act_ipt: Unknown symbol tcf_hash_destroy (err 0) [ 86.853024] act_mirred: Unknown symbol tcf_hash_check (err 0) [ 86.858873] act_mirred: Unknown symbol tcf_hash_create (err 0) [ 86.864792] act_mirred: Unknown symbol tcf_unregister_action (err 0) [ 86.871234] act_mirred: Unknown symbol tcf_hash_insert (err 0) [ 86.877161] act_mirred: Unknown symbol tcf_register_action (err 0) [ 86.883417] act_mirred: Unknown symbol tcf_hash_destroy (err 0) [ 86.890207] act_police: Unknown symbol tcf_unregister_action (err 0) [ 86.896657] act_police: Unknown symbol tcf_hash_new_index (err 0) [ 86.902828] act_police: Unknown symbol tcf_hash_release (err 0) [ 86.908839] act_police: Unknown symbol tcf_hash_search (err 0) [ 86.914743] act_police: Unknown symbol tcf_register_action (err 0) [ 86.921009] act_police: Unknown symbol tcf_action_dump_1 (err 0) [ 86.927342] act_skbedit: Unknown symbol tcf_hash_check (err 0) [ 86.933250] act_skbedit: Unknown symbol tcf_hash_create (err 0) [ 86.939271] act_skbedit: Unknown symbol tcf_unregister_action (err 0) [ 86.945789] act_skbedit: Unknown symbol tcf_hash_insert (err 0) [ 86.951793] act_skbedit: Unknown symbol tcf_hash_release (err 0) [ 86.957895] act_skbedit: Unknown symbol tcf_register_action (err 0) [ 86.965025] cls_basic: Unknown symbol tcf_action_exec (err 0) [ 86.970864] cls_basic: Unknown symbol unregister_tcf_proto_ops (err 0) [ 86.977500] cls_basic: Unknown symbol __tcf_em_tree_match (err 0) [ 86.983670] cls_basic: Unknown symbol tcf_exts_destroy (err 0) [ 86.989584] cls_basic: Unknown symbol tcf_em_tree_dump (err 0) [ 86.995482] cls_basic: Unknown symbol tcf_exts_change (err 0) [ 87.001311] cls_basic: Unknown symbol tcf_exts_dump (err 0) [ 87.006972] cls_basic: Unknown symbol tcf_exts_dump_stats (err 0) [ 87.013133] cls_basic: Unknown symbol tcf_em_tree_validate (err 0) [ 87.019400] cls_basic: Unknown symbol register_tcf_proto_ops (err 0) [ 87.025827] cls_basic: Unknown symbol tcf_em_tree_destroy (err 0) [ 87.032006] cls_basic: Unknown symbol tcf_exts_validate (err 0) [ 87.038685] cls_flow: Unknown symbol tcf_action_exec (err 0) [ 87.044412] cls_flow: Unknown symbol unregister_tcf_proto_ops (err 0) [ 87.050973] cls_flow: Unknown symbol __tcf_em_tree_match (err 0) [ 87.057064] cls_flow: Unknown symbol tcf_exts_destroy (err 0) [ 87.062882] cls_flow: Unknown symbol tcf_em_tree_dump (err 0) [ 87.068709] cls_flow: Unknown symbol tcf_exts_change (err 0) [ 87.074436] cls_flow: Unknown symbol tcf_exts_dump (err 0) [ 87.080010] cls_flow: Unknown symbol tcf_exts_dump_stats (err 0) [ 87.086087] cls_flow: Unknown symbol tcf_em_tree_validate (err 0) [ 87.092264] cls_flow: Unknown symbol register_tcf_proto_ops (err 0) [ 87.098628] cls_flow: Unknown symbol tcf_em_tree_destroy (err 0) [ 87.104710] cls_flow: Unknown symbol tcf_exts_validate (err 0) [ 87.111362] cls_fw: Unknown symbol tcf_action_exec (err 0) [ 87.116945] cls_fw: Unknown symbol unregister_tcf_proto_ops (err 0) [ 87.123304] cls_fw: Unknown symbol tcf_exts_destroy (err 0) [ 87.128957] cls_fw: Unknown symbol tcf_exts_change (err 0) [ 87.134513] cls_fw: Unknown symbol tcf_exts_dump (err 0) [ 87.139914] cls_fw: Unknown symbol tcf_exts_dump_stats (err 0) [ 87.145819] cls_fw: Unknown symbol register_tcf_proto_ops (err 0) [ 87.151997] cls_fw: Unknown symbol tcf_exts_validate (err 0) [ 87.158014] cls_route: Unknown symbol tcf_action_exec (err 0) [ 87.163832] cls_route: Unknown symbol unregister_tcf_proto_ops (err 0) [ 87.170467] cls_route: Unknown symbol tcf_exts_destroy (err 0) [ 87.176370] cls_route: Unknown symbol tcf_exts_change (err 0) [ 87.182201] cls_route: Unknown symbol tcf_exts_dump (err 0) [ 87.187857] cls_route: Unknown symbol tcf_exts_dump_stats (err 0) [ 87.194026] cls_route: Unknown symbol register_tcf_proto_ops (err 0) [ 87.200460] cls_route: Unknown symbol tcf_exts_validate (err 0) [ 87.207049] cls_tcindex: Unknown symbol tcf_action_exec (err 0) [ 87.213038] cls_tcindex: Unknown symbol unregister_tcf_proto_ops (err 0) [ 87.219849] cls_tcindex: Unknown symbol tcf_exts_destroy (err 0) [ 87.225926] cls_tcindex: Unknown symbol tcf_exts_change (err 0) [ 87.231930] cls_tcindex: Unknown symbol tcf_exts_dump (err 0) [ 87.237762] cls_tcindex: Unknown symbol tcf_exts_dump_stats (err 0) [ 87.244105] cls_tcindex: Unknown symbol register_tcf_proto_ops (err 0) [ 87.250715] cls_tcindex: Unknown symbol tcf_exts_validate (err 0) [ 87.257177]
[OpenWrt-Devel] [PATCH] ar71xx Fix the sys LEDs on the EasyLink M150 and mini
From: L. D. Pinney ldpin...@gmail.com
This Patch sets the system LED on the EasyLink M150 and mini to EasyLink
Signed-off-by: L. D. Pinney ldpin...@gmail.com
---
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
index 72a396d..6701d3e 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
@@ -44,7 +44,7 @@ static struct flash_platform_data EL_M150_flash_data = {
static struct gpio_led EL_M150_leds_gpio[] __initdata = {
{
- .name = ELINK:green:system,
+ .name = EasyLink:green:system,
.gpio = EL_M150_GPIO_LED_SYSTEM,
.active_low = 1,
},
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
index aaccb0d..4af9abd 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
@@ -40,7 +40,7 @@ static struct flash_platform_data mini_flash_data = {
static struct gpio_led mini_leds_gpio[] __initdata = {
{
- .name = ELINK:green:system,
+ .name = EasyLink:green:system,
.gpio = MINI_GPIO_LED_SYSTEM,
.active_low = 1,
},diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
index 72a396d..6701d3e 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-m150.c
@@ -44,7 +44,7 @@ static struct flash_platform_data EL_M150_flash_data = {
static struct gpio_led EL_M150_leds_gpio[] __initdata = {
{
- .name = ELINK:green:system,
+ .name = EasyLink:green:system,
.gpio = EL_M150_GPIO_LED_SYSTEM,
.active_low = 1,
},
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
index aaccb0d..4af9abd 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-el-mini.c
@@ -40,7 +40,7 @@ static struct flash_platform_data mini_flash_data = {
static struct gpio_led mini_leds_gpio[] __initdata = {
{
- .name = ELINK:green:system,
+ .name = EasyLink:green:system,
.gpio = MINI_GPIO_LED_SYSTEM,
.active_low = 1,
},
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Lots of missing packages!
* Steven Barth cy...@openwrt.org [13.08.2014 10:48]: The current status of oldpackages is this: If you are using trunk and want to use the possibly outdated packages you have to enable the oldpackages feed and build them manually. how is this done? till some weeks it was: make package/symlinks and now? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Lots of missing packages!
Please see https://forum.openwrt.org/viewtopic.php?id=52219 Am 20.08.2014 um 15:03 schrieb Bastian Bittorf: * Steven Barth cy...@openwrt.org [13.08.2014 10:48]: The current status of oldpackages is this: If you are using trunk and want to use the possibly outdated packages you have to enable the oldpackages feed and build them manually. how is this done? till some weeks it was: make package/symlinks and now? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] bcm53xx: backport more spi-nor patches
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
target/linux/bcm53xx/config-3.14 | 1 +
.../002-mtd-spi-nor-queued-for-3.18.patch | 39 +++
...pport-for-struct-flash_platform_data-into.patch | 52 +++
...-add-Kconfig-option-to-disable-4K-sectors.patch | 44 +++
...-allow-NULL-as-spi_device_id-in-spi_nor_s.patch | 46 +++
.../403-mtd-spi-nor-refactor-wait-till-ready.patch | 374 +
6 files changed, 556 insertions(+)
create mode 100644
target/linux/bcm53xx/patches-3.14/002-mtd-spi-nor-queued-for-3.18.patch
create mode 100644
target/linux/bcm53xx/patches-3.14/400-mtd-move-support-for-struct-flash_platform_data-into.patch
create mode 100644
target/linux/bcm53xx/patches-3.14/401-mtd-spi-nor-add-Kconfig-option-to-disable-4K-sectors.patch
create mode 100644
target/linux/bcm53xx/patches-3.14/402-mtd-spi-nor-allow-NULL-as-spi_device_id-in-spi_nor_s.patch
create mode 100644
target/linux/bcm53xx/patches-3.14/403-mtd-spi-nor-refactor-wait-till-ready.patch
diff --git a/target/linux/bcm53xx/config-3.14 b/target/linux/bcm53xx/config-3.14
index f703522..e0fd0fd 100644
--- a/target/linux/bcm53xx/config-3.14
+++ b/target/linux/bcm53xx/config-3.14
@@ -168,6 +168,7 @@ CONFIG_MODULES_USE_ELF_REL=y
CONFIG_MTD_BCM47XX_PARTS=y
# CONFIG_MTD_PHYSMAP_OF is not set
CONFIG_MTD_SPI_NOR=y
+# CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not set
CONFIG_MULTI_IRQ_HANDLER=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_NEED_DMA_MAP_STATE=y
diff --git
a/target/linux/bcm53xx/patches-3.14/002-mtd-spi-nor-queued-for-3.18.patch
b/target/linux/bcm53xx/patches-3.14/002-mtd-spi-nor-queued-for-3.18.patch
new file mode 100644
index 000..7505a17
--- /dev/null
+++ b/target/linux/bcm53xx/patches-3.14/002-mtd-spi-nor-queued-for-3.18.patch
@@ -0,0 +1,39 @@
+--- a/drivers/mtd/spi-nor/spi-nor.c
b/drivers/mtd/spi-nor/spi-nor.c
+@@ -611,6 +611,7 @@ const struct spi_device_id spi_nor_ids[]
+ { m25px32-s0, INFO(0x207316, 0, 64 * 1024, 64, SECT_4K) },
+ { m25px32-s1, INFO(0x206316, 0, 64 * 1024, 64, SECT_4K) },
+ { m25px64,INFO(0x207117, 0, 64 * 1024, 128, 0) },
++ { m25px80,INFO(0x207114, 0, 64 * 1024, 16, 0) },
+
+ /* Winbond -- w25x blocks are 64K, sectors are 4KiB */
+ { w25x10, INFO(0xef3011, 0, 64 * 1024, 2, SECT_4K) },
+@@ -623,7 +624,6 @@ const struct spi_device_id spi_nor_ids[]
+ { w25q32dw, INFO(0xef6016, 0, 64 * 1024, 64, SECT_4K) },
+ { w25x64, INFO(0xef3017, 0, 64 * 1024, 128, SECT_4K) },
+ { w25q64, INFO(0xef4017, 0, 64 * 1024, 128, SECT_4K) },
+- { w25q128, INFO(0xef4018, 0, 64 * 1024, 256, SECT_4K) },
+ { w25q80, INFO(0xef5014, 0, 64 * 1024, 16, SECT_4K) },
+ { w25q80bl, INFO(0xef4014, 0, 64 * 1024, 16, SECT_4K) },
+ { w25q128, INFO(0xef4018, 0, 64 * 1024, 256, SECT_4K) },
+@@ -671,11 +671,6 @@ static const struct spi_device_id *spi_n
+ return ERR_PTR(-ENODEV);
+ }
+
+-static const struct spi_device_id *jedec_probe(struct spi_nor *nor)
+-{
+- return nor-read_id(nor);
+-}
+-
+ static int spi_nor_read(struct mtd_info *mtd, loff_t from, size_t len,
+ size_t *retlen, u_char *buf)
+ {
+@@ -958,7 +953,7 @@ int spi_nor_scan(struct spi_nor *nor, co
+ if (info-jedec_id) {
+ const struct spi_device_id *jid;
+
+- jid = jedec_probe(nor);
++ jid = nor-read_id(nor);
+ if (IS_ERR(jid)) {
+ return PTR_ERR(jid);
+ } else if (jid != id) {
diff --git
a/target/linux/bcm53xx/patches-3.14/400-mtd-move-support-for-struct-flash_platform_data-into.patch
b/target/linux/bcm53xx/patches-3.14/400-mtd-move-support-for-struct-flash_platform_data-into.patch
new file mode 100644
index 000..8076f55
--- /dev/null
+++
b/target/linux/bcm53xx/patches-3.14/400-mtd-move-support-for-struct-flash_platform_data-into.patch
@@ -0,0 +1,52 @@
+--- a/drivers/mtd/spi-nor/spi-nor.c
b/drivers/mtd/spi-nor/spi-nor.c
+@@ -915,7 +915,6 @@ int spi_nor_scan(struct spi_nor *nor, co
+ enum read_mode mode)
+ {
+ struct flash_info *info;
+- struct flash_platform_data *data;
+ struct device *dev = nor-dev;
+ struct mtd_info *mtd = nor-mtd;
+ struct device_node *np = dev-of_node;
+@@ -926,28 +925,6 @@ int spi_nor_scan(struct spi_nor *nor, co
+ if (ret)
+ return ret;
+
+- /* Platform data helps sort out which chip type we have, as
+- * well as how this board partitions it. If we don't have
+- * a chip ID, try the JEDEC id commands; they'll work for most
+- * newer chips, even if we don't recognize the particular chip.
+- */
+- data = dev_get_platdata(dev);
+- if (data data-type) {
+- const struct spi_device_id *plat_id;
+-
+- for (i = 0; i ARRAY_SIZE(spi_nor_ids) - 1; i++) {
+- plat_id = spi_nor_ids[i];
+- if
[OpenWrt-Devel] [PATCH 2/2] bcm53xx: add bcm53xxspiflash driver for SPI flashes
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
target/linux/bcm53xx/config-3.14 | 1 +
...spiflash-new-driver-for-SPI-flahes-on-Bro.patch | 261 +
2 files changed, 262 insertions(+)
create mode 100644
target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
diff --git a/target/linux/bcm53xx/config-3.14 b/target/linux/bcm53xx/config-3.14
index e0fd0fd..2192b83 100644
--- a/target/linux/bcm53xx/config-3.14
+++ b/target/linux/bcm53xx/config-3.14
@@ -167,6 +167,7 @@ CONFIG_MIGHT_HAVE_PCI=y
CONFIG_MODULES_USE_ELF_REL=y
CONFIG_MTD_BCM47XX_PARTS=y
# CONFIG_MTD_PHYSMAP_OF is not set
+CONFIG_MTD_SPI_BCM53XXSPIFLASH=y
CONFIG_MTD_SPI_NOR=y
# CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not set
CONFIG_MULTI_IRQ_HANDLER=y
diff --git
a/target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
b/target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
new file mode 100644
index 000..a74e423
--- /dev/null
+++
b/target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
@@ -0,0 +1,261 @@
+--- a/drivers/mtd/spi-nor/Kconfig
b/drivers/mtd/spi-nor/Kconfig
+@@ -28,4 +28,10 @@ config SPI_FSL_QUADSPI
+ This enables support for the Quad SPI controller in master mode.
+ We only connect the NOR to this controller now.
+
++config MTD_SPI_BCM53XXSPIFLASH
++ tristate SPI-NOR flashes connected to the Broadcom ARM SoC
++ depends on MTD_SPI_NOR
++ help
++SPI driver for flashes used on Broadcom ARM SoCs.
++
+ endif # MTD_SPI_NOR
+--- a/drivers/mtd/spi-nor/Makefile
b/drivers/mtd/spi-nor/Makefile
+@@ -1,2 +1,3 @@
+ obj-$(CONFIG_MTD_SPI_NOR) += spi-nor.o
+ obj-$(CONFIG_SPI_FSL_QUADSPI) += fsl-quadspi.o
++obj-$(CONFIG_MTD_SPI_BCM53XXSPIFLASH) += bcm53xxspiflash.o
+--- /dev/null
b/drivers/mtd/spi-nor/bcm53xxspiflash.c
+@@ -0,0 +1,239 @@
++#include linux/module.h
++#include linux/delay.h
++#include linux/spi/spi.h
++#include linux/mtd/spi-nor.h
++#include linux/mtd/mtd.h
++#include linux/mtd/cfi.h
++
++static const char * const probes[] = { bcm47xxpart, NULL };
++
++struct bcm53xxsf {
++ struct spi_device *spi;
++ struct mtd_info mtd;
++ struct spi_nor nor;
++};
++
++/**
++ * spi-nor API
++ **/
++
++static int bcm53xxspiflash_read_reg(struct spi_nor *nor, u8 opcode, u8 *buf,
++ int len)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++
++ return spi_write_then_read(b53sf-spi, opcode, 1, buf, len);
++}
++
++static int bcm53xxspiflash_write_reg(struct spi_nor *nor, u8 opcode, u8 *buf,
++ int len, int write_enable)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++ u8 *cmd = kzalloc(len + 1, GFP_KERNEL);
++ int err;
++
++ if (!cmd)
++ return -ENOMEM;
++
++ cmd[0] = opcode;
++ memcpy(cmd[1], buf, len);
++ err = spi_write(b53sf-spi, cmd, len + 1);
++
++ kfree(cmd);
++
++ return err;
++}
++
++static int bcm53xxspiflash_read(struct spi_nor *nor, loff_t from, size_t len,
++ size_t *retlen, u_char *buf)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++ struct spi_message m;
++ struct spi_transfer t[2] = { { 0 }, { 0 } };
++ unsigned char cmd[5];
++ int cmd_len = 0;
++ int err;
++
++ spi_message_init(m);
++
++ cmd[cmd_len++] = SPINOR_OP_READ;
++ if (b53sf-mtd.size 0x100)
++ cmd[cmd_len++] = (from 0xFF00) 24;
++ cmd[cmd_len++] = (from 0x00FF) 16;
++ cmd[cmd_len++] = (from 0xFF00) 8;
++ cmd[cmd_len++] = (from 0x00FF) 0;
++
++ t[0].tx_buf = cmd;
++ t[0].len = cmd_len;
++ spi_message_add_tail(t[0], m);
++
++ t[1].rx_buf = buf;
++ t[1].len = len;
++ spi_message_add_tail(t[1], m);
++
++ err = spi_sync(b53sf-spi, m);
++ if (err)
++ return err;
++
++ if (retlen m.actual_length cmd_len)
++ *retlen = m.actual_length - cmd_len;
++
++ return 0;
++}
++
++static void bcm53xxspiflash_write(struct spi_nor *nor, loff_t to, size_t len,
++size_t *retlen, const u_char *buf)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++ struct spi_message m;
++ struct spi_transfer t = { 0 };
++ u8 *cmd = kzalloc(len + 5, GFP_KERNEL);
++ int cmd_len = 0;
++ int err;
++
++ if (!cmd)
++ return;
++
++ spi_message_init(m);
++
++ cmd[cmd_len++] = nor-program_opcode;
++ if (b53sf-mtd.size 0x100)
++ cmd[cmd_len++] = (to 0xFF00) 24;
++ cmd[cmd_len++] = (to 0x00FF) 16;
++ cmd[cmd_len++] = (to 0xFF00) 8;
++ cmd[cmd_len++] = (to 0x00FF) 0;
++
[OpenWrt-Devel] Firmware without SquashFS (initramfs + overlay)
I found this explanation: http://wiki.openwrt.org/doc/techref/filesystems#can.we.switch.the.filesystem.to.be.entirely.jffs2 but I'm looking for more details. I wanted to run OpenWrt on bcm53xx using initramfs and flash with overlay data partition. So I've improved/hacked partitioner driver to create partitions like this: [2.385715] 5 bcm47xxpart partitions found on MTD device spi32766.0 [2.391982] Creating 5 MTD partitions on spi32766.0: [2.397117] 0x-0x0004 : boot [2.403742] 0x0004-0x00ff : firmware [2.410631] 0x0004001c-0x0027 : linux [2.429738] 0x0027-0x00ff : rootfs_data [2.436903] 0x00ff-0x0100 : nvram I hoped OpenWrt will use initramfs and then will overlay with with rootfs_data. Unfortunately it didn't happen, I think rootfs_data was ignored by OpenWrt. I've then tried to use rootfs. It was a bit better: [2.386053] 5 bcm47xxpart partitions found on MTD device spi32766.0 [2.392326] Creating 5 MTD partitions on spi32766.0: [2.397457] 0x-0x0004 : boot [2.404071] 0x0004-0x00ff : firmware [2.410976] 0x0004001c-0x0027 : linux [2.430065] 0x0027-0x00ff : rootfs [2.436823] mtd: device 3 (rootfs) set to be root filesystem [2.442752] mtdsplit: no squashfs found in spi32766.0 [2.447975] 0x00ff-0x0100 : nvram # mount rootfs on / type rootfs (rw) proc on /proc type proc (rw,noatime) sysfs on /sys type sysfs (rw,noatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime) tmpfs on /dev type tmpfs (rw,relatime,size=512k,mode=755) devpts on /dev/pts type devpts (rw,relatime,mode=600) debugfs on /sys/kernel/debug type debugfs (rw,noatime) But none of my changes in / survived the reboot. Any tips how to fix this? -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [base-files] remove useless explicit set of function returncode
[base-files] remove useless explicit set of function returncode
somebody started to set a function returncode in the validation
stuff and everybody copies it, e.g.
myfunction()
{
fire_command
return $?
}
a function automatically returns with the last returncode,
so we can safely remove the command 'return $?'. reference:
http://tldp.org/LDP/abs/html/exit-status.html
The last command executed in the function or script determines the exit
status.
Signed-off-by: Bastian Bittorf bitt...@bluebottle.com
---
package/base-files/files/etc/init.d/system |2 --
package/network/config/firewall/files/firewall.init|4
package/network/config/netifd/files/etc/init.d/network | 14 --
package/network/services/dropbear/files/dropbear.init |1 -
package/network/services/relayd/files/relay.init |2 --
package/system/ubox/files/log.init |2 --
package/utils/busybox/files/sysntpd|1 -
8 files changed, 1 insertion(+), 26 deletions(-)
create mode 16 kalua
@@ -0,0 +1 @@
+Subproject commit 2fbbcb4c21178e8b4991727994d2036e768dd3eb
diff --git a/package/base-files/files/etc/init.d/system
b/package/base-files/files/etc/init.d/system
index 24a9fde..6388d62 100755
--- a/package/base-files/files/etc/init.d/system
+++ b/package/base-files/files/etc/init.d/system
@@ -12,8 +12,6 @@ validate_system_section()
'buffersize:uinteger' \
'timezone:string:UTC' \
'zonename:string'
-
- return $?
}
system_config() {
diff --git a/package/network/config/firewall/files/firewall.init
b/package/network/config/firewall/files/firewall.init
index 1147b83..9664e39 100755
--- a/package/network/config/firewall/files/firewall.init
+++ b/package/network/config/firewall/files/firewall.init
@@ -15,8 +15,6 @@ validate_firewall_redirect()
'dest_ip:cidr' \
'dest_port:or(port, portrange)' \
'target:or(SNAT, DNAT)'
-
- return $?
}
validate_firewall_rule()
@@ -28,8 +26,6 @@ validate_firewall_rule()
'src_port:or(port, portrange)' \
'dest_port:or(port, portrange)' \
'target:string'
-
- return $?
}
service_triggers() {
diff --git a/package/network/config/netifd/files/etc/init.d/network
b/package/network/config/netifd/files/etc/init.d/network
index 8a7427b..1d8a5b3 100755
--- a/package/network/config/netifd/files/etc/init.d/network
+++ b/package/network/config/netifd/files/etc/init.d/network
@@ -50,8 +50,6 @@ validate_atm_bridge_section()
'atmdev:uinteger:0' \
'encaps:or(llc, vc):llc' \
'payload:or(bridged, routed):bridged'
-
- return $?
}
validate_route_section()
@@ -64,8 +62,6 @@ validate_route_section()
'metric:uinteger' \
'mtu:uinteger' \
'table:or(range(0,65535),string)'
-
- return $?
}
validate_route6_section()
@@ -77,8 +73,6 @@ validate_route6_section()
'metric:uinteger' \
'mtu:uinteger' \
'table:or(range(0,65535),string)'
-
- return $?
}
validate_rule_section()
@@ -94,8 +88,6 @@ validate_rule_section()
'lookup:or(range(0,65535),string)' \
'goto:range(0,65535)' \
'action:or(prohibit, unreachable, blackhole, throw)'
-
- return $?
}
validate_rule6_section()
@@ -111,8 +103,6 @@ validate_rule6_section()
'lookup:or(range(0,65535),string)' \
'goto:range(0,65535)' \
'action:or(prohibit, unreachable, blackhole, throw)'
-
- return $?
}
validate_switch_section()
@@ -122,8 +112,6 @@ validate_switch_section()
'enable:bool' \
'enable_vlan:bool' \
'reset:bool'
-
- return $?
}
validate_switch_vlan()
@@ -132,8 +120,6 @@ validate_switch_vlan()
'device:string' \
'vlan:uinteger' \
'ports:list(ports)'
-
- return $?
}
service_triggers()
diff --git a/package/network/services/dropbear/files/dropbear.init
b/package/network/services/dropbear/files/dropbear.init
index 5206426..c6f3d9b 100755
--- a/package/network/services/dropbear/files/dropbear.init
+++ b/package/network/services/dropbear/files/dropbear.init
@@ -47,7 +47,6 @@ validate_section_dropbear()
'Port:list(port):22' \
'SSHKeepAlive:uinteger:300' \
'IdleTimeout:uinteger:0'
- return $?
}
dropbear_instance()
diff --git a/package/network/services/relayd/files/relay.init
b/package/network/services/relayd/files/relay.init
index e193312..e38143f 100644
--- a/package/network/services/relayd/files/relay.init
+++ b/package/network/services/relayd/files/relay.init
@@ -15,8 +15,6 @@ validate_proto_relayd()
'table:range(0, 65535):16800' \
[OpenWrt-Devel] [PATCH] New package: mailsend. A tool that allows to send emails without the need to install an smtp server. Supports ssl.
From: Giovanni Di Stasi giovanni.dist...@unina.it --- net/mailsend/Makefile | 48 ++ net/mailsend/patches/000-configure | 11 + 2 files changed, 59 insertions(+) create mode 100644 net/mailsend/Makefile create mode 100644 net/mailsend/patches/000-configure diff --git a/net/mailsend/Makefile b/net/mailsend/Makefile new file mode 100644 index 000..34e6a2f --- /dev/null +++ b/net/mailsend/Makefile @@ -0,0 +1,48 @@ +# +# Copyright (C) 2006-2012 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +include $(TOPDIR)/rules.mk + +PKG_NAME:=mailsend +PKG_VERSION:=1.17b14 +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=https://github.com/muquit/mailsend/releases/download/1.17b14/ +PKG_MD5SUM:=a147cf32ee3e6562e49b4fec1dd0ea64 + +PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk + +define Package/mailsend + SECTION:=utils + CATEGORY:=Utilities + TITLE:=mailsend + DEPENDS:=+libopenssl + URL:=https://github.com/muquit/mailsend +endef + +define Build/Configure + $(call Build/Configure/Default, --with-openssl=/home/giovanni/openwrt/openwrt/build_dir/target-mips_r2_uClibc-0.9.33.2/openssl-1.0.1h) +endef + +define Package/mailsend/description + Mailsend is an utility that allows to send email without the need of a stmp server. It supports ssl emails (as gmail). +endef + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) +endef + +define Package/mailsend/install + $(INSTALL_DIR) $(1)/usr/bin + $(INSTALL_BIN) $(PKG_BUILD_DIR)/mailsend $(1)/usr/bin/ +endef + +$(eval $(call BuildPackage,mailsend)) + diff --git a/net/mailsend/patches/000-configure b/net/mailsend/patches/000-configure new file mode 100644 index 000..b393f23 --- /dev/null +++ b/net/mailsend/patches/000-configure @@ -0,0 +1,11 @@ +--- a/configure2013-10-14 17:37:39.0 +0200 b/configure2014-08-19 23:33:58.494405062 +0200 +@@ -5685,7 +5685,7 @@ + fi + fi + if test -z $openssl_cv_libraries; then +-openssl_cv_libraries=$openssl_cv_dir/lib ++openssl_cv_libraries=$openssl_cv_dir + if test -d $openssl_cv_libraries; then + OPENSSL_LIBS=-L$openssl_cv_libraries -lssl -lcrypto + fi -- 2.0.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH V2 2/2] bcm53xx: add bcm53xxspiflash driver for SPI flashes
Signed-off-by: Rafał Miłecki zaj...@gmail.com
---
V2: Fix crash
Add JEDEC
---
target/linux/bcm53xx/config-3.14 | 1 +
...spiflash-new-driver-for-SPI-flahes-on-Bro.patch | 263 +
...spiflash-try-using-JEDEC-as-one-of-method.patch | 42
3 files changed, 306 insertions(+)
create mode 100644
target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
create mode 100644
target/linux/bcm53xx/patches-3.14/405-mtd-bcm53xxspiflash-try-using-JEDEC-as-one-of-method.patch
diff --git a/target/linux/bcm53xx/config-3.14 b/target/linux/bcm53xx/config-3.14
index e0fd0fd..2192b83 100644
--- a/target/linux/bcm53xx/config-3.14
+++ b/target/linux/bcm53xx/config-3.14
@@ -167,6 +167,7 @@ CONFIG_MIGHT_HAVE_PCI=y
CONFIG_MODULES_USE_ELF_REL=y
CONFIG_MTD_BCM47XX_PARTS=y
# CONFIG_MTD_PHYSMAP_OF is not set
+CONFIG_MTD_SPI_BCM53XXSPIFLASH=y
CONFIG_MTD_SPI_NOR=y
# CONFIG_MTD_SPI_NOR_USE_4K_SECTORS is not set
CONFIG_MULTI_IRQ_HANDLER=y
diff --git
a/target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
b/target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
new file mode 100644
index 000..9a9d903
--- /dev/null
+++
b/target/linux/bcm53xx/patches-3.14/404-mtd-bcm53xxspiflash-new-driver-for-SPI-flahes-on-Bro.patch
@@ -0,0 +1,263 @@
+--- a/drivers/mtd/spi-nor/Kconfig
b/drivers/mtd/spi-nor/Kconfig
+@@ -28,4 +28,10 @@ config SPI_FSL_QUADSPI
+ This enables support for the Quad SPI controller in master mode.
+ We only connect the NOR to this controller now.
+
++config MTD_SPI_BCM53XXSPIFLASH
++ tristate SPI-NOR flashes connected to the Broadcom ARM SoC
++ depends on MTD_SPI_NOR
++ help
++SPI driver for flashes used on Broadcom ARM SoCs.
++
+ endif # MTD_SPI_NOR
+--- a/drivers/mtd/spi-nor/Makefile
b/drivers/mtd/spi-nor/Makefile
+@@ -1,2 +1,3 @@
+ obj-$(CONFIG_MTD_SPI_NOR) += spi-nor.o
+ obj-$(CONFIG_SPI_FSL_QUADSPI) += fsl-quadspi.o
++obj-$(CONFIG_MTD_SPI_BCM53XXSPIFLASH) += bcm53xxspiflash.o
+--- /dev/null
b/drivers/mtd/spi-nor/bcm53xxspiflash.c
+@@ -0,0 +1,241 @@
++#include linux/module.h
++#include linux/delay.h
++#include linux/spi/spi.h
++#include linux/mtd/spi-nor.h
++#include linux/mtd/mtd.h
++#include linux/mtd/cfi.h
++
++static const char * const probes[] = { bcm47xxpart, NULL };
++
++struct bcm53xxsf {
++ struct spi_device *spi;
++ struct mtd_info mtd;
++ struct spi_nor nor;
++};
++
++/**
++ * spi-nor API
++ **/
++
++static int bcm53xxspiflash_read_reg(struct spi_nor *nor, u8 opcode, u8 *buf,
++ int len)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++
++ return spi_write_then_read(b53sf-spi, opcode, 1, buf, len);
++}
++
++static int bcm53xxspiflash_write_reg(struct spi_nor *nor, u8 opcode, u8 *buf,
++ int len, int write_enable)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++ u8 *cmd = kzalloc(len + 1, GFP_KERNEL);
++ int err;
++
++ if (!cmd)
++ return -ENOMEM;
++
++ cmd[0] = opcode;
++ memcpy(cmd[1], buf, len);
++ err = spi_write(b53sf-spi, cmd, len + 1);
++
++ kfree(cmd);
++
++ return err;
++}
++
++static int bcm53xxspiflash_read(struct spi_nor *nor, loff_t from, size_t len,
++ size_t *retlen, u_char *buf)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++ struct spi_message m;
++ struct spi_transfer t[2] = { { 0 }, { 0 } };
++ unsigned char cmd[5];
++ int cmd_len = 0;
++ int err;
++
++ spi_message_init(m);
++
++ cmd[cmd_len++] = SPINOR_OP_READ;
++ if (b53sf-mtd.size 0x100)
++ cmd[cmd_len++] = (from 0xFF00) 24;
++ cmd[cmd_len++] = (from 0x00FF) 16;
++ cmd[cmd_len++] = (from 0xFF00) 8;
++ cmd[cmd_len++] = (from 0x00FF) 0;
++
++ t[0].tx_buf = cmd;
++ t[0].len = cmd_len;
++ spi_message_add_tail(t[0], m);
++
++ t[1].rx_buf = buf;
++ t[1].len = len;
++ spi_message_add_tail(t[1], m);
++
++ err = spi_sync(b53sf-spi, m);
++ if (err)
++ return err;
++
++ if (retlen m.actual_length cmd_len)
++ *retlen = m.actual_length - cmd_len;
++
++ return 0;
++}
++
++static void bcm53xxspiflash_write(struct spi_nor *nor, loff_t to, size_t len,
++size_t *retlen, const u_char *buf)
++{
++ struct bcm53xxsf *b53sf = nor-priv;
++ struct spi_message m;
++ struct spi_transfer t = { 0 };
++ u8 *cmd = kzalloc(len + 5, GFP_KERNEL);
++ int cmd_len = 0;
++ int err;
++
++ if (!cmd)
++ return;
++
++ spi_message_init(m);
++
++ cmd[cmd_len++] = nor-program_opcode;
++ if (b53sf-mtd.size 0x100)
Re: [OpenWrt-Devel] Firmware without SquashFS (initramfs + overlay)
On 08/20/2014 07:24 PM, Rafał Miłecki wrote: I found this explanation: http://wiki.openwrt.org/doc/techref/filesystems#can.we.switch.the.filesystem.to.be.entirely.jffs2 but I'm looking for more details. I wanted to run OpenWrt on bcm53xx using initramfs and flash with overlay data partition. So I've improved/hacked partitioner driver to create partitions like this: [2.385715] 5 bcm47xxpart partitions found on MTD device spi32766.0 [2.391982] Creating 5 MTD partitions on spi32766.0: [2.397117] 0x-0x0004 : boot [2.403742] 0x0004-0x00ff : firmware [2.410631] 0x0004001c-0x0027 : linux [2.429738] 0x0027-0x00ff : rootfs_data [2.436903] 0x00ff-0x0100 : nvram I hoped OpenWrt will use initramfs and then will overlay with with rootfs_data. Unfortunately it didn't happen, I think rootfs_data was ignored by OpenWrt. I've then tried to use rootfs. It was a bit better: [2.386053] 5 bcm47xxpart partitions found on MTD device spi32766.0 [2.392326] Creating 5 MTD partitions on spi32766.0: [2.397457] 0x-0x0004 : boot [2.404071] 0x0004-0x00ff : firmware [2.410976] 0x0004001c-0x0027 : linux [2.430065] 0x0027-0x00ff : rootfs [2.436823] mtd: device 3 (rootfs) set to be root filesystem [2.442752] mtdsplit: no squashfs found in spi32766.0 [2.447975] 0x00ff-0x0100 : nvram # mount rootfs on / type rootfs (rw) proc on /proc type proc (rw,noatime) sysfs on /sys type sysfs (rw,noatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime) tmpfs on /dev type tmpfs (rw,relatime,size=512k,mode=755) devpts on /dev/pts type devpts (rw,relatime,mode=600) debugfs on /sys/kernel/debug type debugfs (rw,noatime) But none of my changes in / survived the reboot. Any tips how to fix this? You want to use initramfs because the SquashFS image is booting very unreliable or are there any other reasons? This boot problems seams to be in the boot loader. The boot loader should not see a difference between an initramfs and a SquashFS image, could it be that the boot loader does not like small images or not aligned images? Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: enable sysupgrade for the EnGenius ESR900
Signed-off-by: Forest Crossman cyro...@gmail.com
---
target/linux/ar71xx/base-files/lib/upgrade/platform.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index b5b2873..846954c 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -176,6 +176,7 @@ platform_check_image() {
dir-835-a1 | \
dragino2 | \
esr1750 | \
+ esr900 | \
ew-dorin | \
ew-dorin-router | \
hiwifi-hc6361 | \
--
1.9.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: use ETH_ALEN for consistency
Signed-off-by: Forest Crossman cyro...@gmail.com
---
target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
index ca36e36..aa2e7f7 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
@@ -145,9 +145,9 @@ static void __init esr900_setup(void)
{
const char *config = (char *) KSEG1ADDR(ESR900_CONFIG_ADDR);
u8 *art = (u8 *) KSEG1ADDR(ESR900_CALDATA_ADDR);
- u8 lan_mac[6];
- u8 wlan0_mac[6];
- u8 wlan1_mac[6];
+ u8 lan_mac[ETH_ALEN];
+ u8 wlan0_mac[ETH_ALEN];
+ u8 wlan1_mac[ETH_ALEN];
if (ath79_nvram_parse_mac_addr(config, ESR900_CONFIG_SIZE,
ethaddr=, lan_mac) == 0) {
--
1.9.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: make LED names for EnGenius routers follow convention
Signed-off-by: Forest Crossman cyro...@gmail.com
---
target/linux/ar71xx/base-files/etc/diag.sh| 4 ++--
target/linux/ar71xx/base-files/etc/uci-defaults/01_leds | 8
target/linux/ar71xx/files/arch/mips/ath79/mach-eap300v2.c | 6 +++---
target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c | 10 +-
4 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index 1864b11..0401b93 100755
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -63,7 +63,7 @@ get_status_led() {
status_led=d-link:amber:power
;;
eap300v2)
- status_led=engenius:blue:power
+ status_led=eap300v2:blue:power
;;
eap7660d)
status_led=eap7660d:green:ds4
@@ -79,7 +79,7 @@ get_status_led() {
status_led=esr1750:amber:power
;;
esr900)
- status_led=engenius:amber:power
+ status_led=esr900:amber:power
;;
hiwifi-hc6361)
status_led=hiwifi:blue:system
diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
index d104f40..4d0992d 100755
--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -66,8 +66,8 @@ db120)
;;
eap300v2)
- ucidef_set_led_netdev lan LAN engenius:blue:lan eth0
- ucidef_set_led_wlan wlan WLAN engenius:blue:wlan phy0tpt
+ ucidef_set_led_netdev lan LAN eap300v2:blue:lan eth0
+ ucidef_set_led_wlan wlan WLAN eap300v2:blue:wlan phy0tpt
;;
rb-750)
@@ -119,8 +119,8 @@ gl-inet)
;;
esr900)
- ucidef_set_led_wlan wlan2g WLAN 2.4 GHz engenius:blue:wlan-2g
phy0tpt
- ucidef_set_led_wlan wlan5g WLAN 5 GHz engenius:blue:wlan-5g
phy1tpt
+ ucidef_set_led_wlan wlan2g WLAN 2.4 GHz esr900:blue:wlan-2g
phy0tpt
+ ucidef_set_led_wlan wlan5g WLAN 5 GHz esr900:blue:wlan-5g
phy1tpt
;;
hiwifi-hc6361)
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-eap300v2.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-eap300v2.c
index ba577e2..0aaf8e9 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-eap300v2.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-eap300v2.c
@@ -35,15 +35,15 @@
static struct gpio_led eap300v2_leds_gpio[] __initdata = {
{
- .name = engenius:blue:power,
+ .name = eap300v2:blue:power,
.gpio = EAP300V2_GPIO_LED_POWER,
.active_low = 1,
}, {
- .name = engenius:blue:lan,
+ .name = eap300v2:blue:lan,
.gpio = EAP300V2_GPIO_LED_LAN,
.active_low = 1,
}, {
- .name = engenius:blue:wlan,
+ .name = eap300v2:blue:wlan,
.gpio = EAP300V2_GPIO_LED_WLAN,
.active_low = 1,
}
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
index ca36e36..88a80f9 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c
@@ -53,27 +53,27 @@
static struct gpio_led esr900_leds_gpio[] __initdata = {
{
- .name = engenius:amber:power,
+ .name = esr900:amber:power,
.gpio = ESR900_GPIO_LED_POWER,
.active_low = 1,
},
{
- .name = engenius:blue:wlan-2g,
+ .name = esr900:blue:wlan-2g,
.gpio = ESR900_GPIO_LED_WLAN_2G,
.active_low = 1,
},
{
- .name = engenius:blue:wps,
+ .name = esr900:blue:wps,
.gpio = ESR900_GPIO_LED_WPS_BLUE,
.active_low = 1,
},
{
- .name = engenius:amber:wps,
+ .name = esr900:amber:wps,
.gpio = ESR900_GPIO_LED_WPS_AMBER,
.active_low = 1,
},
{
- .name = engenius:blue:wlan-5g,
+ .name = esr900:blue:wlan-5g,
.gpio = ESR900_GPIO_LED_WLAN_5G,
.active_low = 1,
}
--
1.9.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] New package: mailsend. A tool that allows to send emails without the need to install an smtp server. Supports ssl.
[ Original patch attachment removed for brevity ] Please consider (re-)submitting this as a pull-request to the new packages repository (https://github.com/openwrt/packages). Read over the CONTRIBUTING.md document before submitting. A couple of things to note about your submission: 1 - Does not have signed-off-by statement 2 - Does not have a PKG_MAINTAINER 3 - Does not have license info 4 - Has references to local file paths !! 5 - Copyright incorrect or out-dated. 6 - OpenSSL should not be required /ted ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] kirkwood / missing kernel-module?
Hi Bastian, On 20.08.2014 12:05 Bastian Bittorf wrote: during boot i see in a long loop these messages, which kernel module is missing or which symbol must be active? (kernel 3.14.17) That is very strange. I ran a make dirclean and built r42230 today for my Pogoplug E02. Both u-boot and OpenWrt run without any hitches. Have you tried running a dirclean and building with a clean buildroot? Regards, Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ar71xx: make LED names for EnGenius routers follow convention
On 21 August 2014 06:45, Forest Crossman cyro...@gmail.com wrote:
Signed-off-by: Forest Crossman cyro...@gmail.com
---
target/linux/ar71xx/base-files/etc/diag.sh| 4 ++--
target/linux/ar71xx/base-files/etc/uci-defaults/01_leds | 8
target/linux/ar71xx/files/arch/mips/ath79/mach-eap300v2.c | 6 +++---
target/linux/ar71xx/files/arch/mips/ath79/mach-esr900.c | 10 +-
4 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh
index 1864b11..0401b93 100755
--- a/target/linux/ar71xx/base-files/etc/diag.sh
+++ b/target/linux/ar71xx/base-files/etc/diag.sh
@@ -63,7 +63,7 @@ get_status_led() {
status_led=d-link:amber:power
;;
eap300v2)
- status_led=engenius:blue:power
+ status_led=eap300v2:blue:power
;;
Taking those buffalo, d-link and other routers as examples, I thought
the convention for naming leds should be `$brand:$color:$function.
yousong
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] scripts: allow pinning of SVN feeds
Previously, Git feeds could be pinned to a particular commit using
URL^commit notation. This patch provides the same functionality for
SVN-based feeds, using URL@revision notation. Just like pinned Git
feeds, pinned SVN feeds do not update when ./scripts/feeds update is
run.
Signed-off-by: Nate Hardison natehardi...@gmail.com
---
scripts/feeds | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/scripts/feeds b/scripts/feeds
index 26c2de0..1589bff 100755
--- a/scripts/feeds
+++ b/scripts/feeds
@@ -105,7 +105,8 @@ sub update_index($)
my %update_method = (
'src-svn' = {
- 'init' = svn checkout '%s' '%s',
+ 'init' = svn checkout '%s' '%s',
+ 'init_revision' = svn checkout -r '%s' '%s' '%s',
'update'= svn update,
'controldir'= .svn,
'revision' = svn info | grep 'Revision' | cut -d ' ' -f
2 | tr -d '\n'},
@@ -126,6 +127,7 @@ my %update_method = (
'revision' = git show --abbrev-commit HEAD | head -n 1 |
cut -d ' ' -f 2 | tr -d '\n'},
'src-gitsvn' = {
'init' = git svn clone -r HEAD '%s' '%s',
+ 'init_revision' = git svn clone -r '%s' '%s' '%s',
'update'= git svn rebase,
'controldir'= .git,
'revision' = git show --abbrev-commit HEAD | head -n 1 |
cut -d ' ' -f 2 | tr -d '\n'},
@@ -158,6 +160,7 @@ sub update_feed_via() {
$safepath =~ s/'/'\\''/;
my ($base_branch, $branch) = split(/;/, $src, 2);
my ($base_commit, $commit) = split(/\^/, $src, 2);
+ my ($base_revision, $revision) = split(/@/, $src, 2);
if( $relocate || !$m-{'update'} || !-d $localpath/$m-{'controldir'}
) {
system(rm -rf '$safepath');
@@ -165,11 +168,15 @@ sub update_feed_via() {
system(sprintf($m-{'init_branch'}, $branch,
$base_branch, $safepath)) == 0 or return 1;
} elsif ($m-{'init_commit'} and $commit) {
system(sprintf($m-{'init_commit'}, $base_commit,
$safepath, $safepath, $commit, $commit)) == 0 or return 1;
+ } elsif ($m-{'init_revision'} and $revision) {
+ system(sprintf($m-{'init_revision'}, $revision,
$base_revision, $safepath)) == 0 or return 1;
} else {
system(sprintf($m-{'init'}, $src, $safepath)) == 0 or
return 1;
}
} elsif ($m-{'init_commit'} and $commit) {
# in case git hash has been provided don't update the feed
+ } elsif ($m-{'init_revision'} and $revision) {
+ # in case svn revision has been provided don't update the feed
} else {
system(cd '$safepath'; $m-{'update'}) == 0 or return 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] [PATCH] ar71xx: make LED names for EnGenius routers follow convention
[Resending because I forgot to reply-all] That’s what I thought originally, but I asked Jon Suphammer why he used the model name instead of the manufacturer in his patch for the EnGenius ESR1750, he responded: Hi Forest, Vendors are not always consistent over time with what colour they use for their LED's. Several factors could play in, like matching LED with a tooling colour or just change of mind. It would be more safe to bind the LED to specific device rather than vendor. Best regards, Jon I agree with him in that it would be better to identify LEDs by model instead of by brand since there is a more direct relationship between the LED and that model than the LED and the manufacturer. In the end, what the LED is called doesn’t really matter since it’s just an arbitrary string. At some point, though, I think we should document one convention to be used across all platforms and models. Or, even better, get rid of the brand/manufacturer identifier entirely and make it something simpler like wlan2g:blue, power:amber, wps:green, wps:red, etc. -- Forest Crossman On August 20, 2014 at 9:24:28 PM, Yousong Zhou (yszhou4t...@gmail.com(mailto:yszhou4t...@gmail.com)) wrote: That’s what I thought originally, but I asked Jon Suphammer why he used the model name instead of the manufacturer in his patch for the EnGenius ESR1750, he responded: Hi Forest, Vendors are not always consistent over time with what colour they use for their LED's. Several factors could play in, like matching LED with a tooling colour or just change of mind. It would be more safe to bind the LED to specific device rather than vendor. Best regards, Jon I agree with him in that it would be better to identify LEDs by model instead of by brand since there is a more direct relationship between the LED and that model than the LED and the manufacturer. In the end, what the LED is called doesn’t really matter since it’s just an arbitrary string. At some point, though, I think we should document one convention to be used across all platforms and models. Or, even better, get rid of the brand/manufacturer identifier entirely and make it something simpler like “wlan2g:blue”, “power:amber”, “wps:green”, “wps:red”, etc. -- Forest Crossman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
