[OpenWrt-Devel] [PATCH 1/1] [uhttpd]: Fix appending https ports to cmdline
Otherwise uhttpd is started only on non-secure ports. Signed-off-by: Wojciech Dubowik wojciech.dubo...@neratec.com --- package/network/services/uhttpd/files/uhttpd.init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/network/services/uhttpd/files/uhttpd.init b/package/network/services/uhttpd/files/uhttpd.init index 51f7547..ce30483 100755 --- a/package/network/services/uhttpd/files/uhttpd.init +++ b/package/network/services/uhttpd/files/uhttpd.init @@ -112,7 +112,7 @@ start_instance() append_arg $cfg key -K for listen in $https; do - append UHTTPD_ARGS -s $listen + procd_append_param command -s $listen done } } -- 1.8.1.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/1] [uhttpd]: Fix appending https ports to cmdline
On 2013-09-25 9:38 AM, Wojciech Dubowik wrote: Otherwise uhttpd is started only on non-secure ports. Signed-off-by: Wojciech Dubowik wojciech.dubo...@neratec.com Applied in r38171 Thanks, - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] SoC NAND driver ar934x/OpenWRT support on WNDR4300
2013.09.24. 23:07 keltezéssel, Stefan Agner írta: Am 2013-09-24 19:09, schrieb Gabor Juhos: A dd command with conv=noerror leads to a image witch is 16KiB smaller than it should be. Don't use dd on NAND flashes. Use the nanddump utility from the mtd-utils package instead. Ok I understand that /dev/mtdblock[x] is not the way to handle NAND, but reading should work anyway. Yes, it should work. However the mtdblock layer can't handle bad blocks/ecc errors so that throws error messages. By using nanddump I could successfully dump the images, although the ECC check corrected bitflips. I guess that when using this NAND through mtdblock, this leads to an I/O error (since its the exactly same place, 2880*512 = 0x00168000). root@OpenWrt:/tmp# dd if=/dev/mtdblock10 of=/tmp/gaga [ 1350.92] end_request: I/O error, dev mtdblock10, sector 2880 [ 1350.92] Buffer I/O error on device mtdblock10, logical block 360 [ 1351.00] end_request: I/O error, dev mtdblock10, sector 2880 [ 1351.00] Buffer I/O error on device mtdblock10, logical block 360 dd: /dev/mtdblock10: Input/output error root@OpenWrt:/tmp# nanddump /dev/mtd10 /tmp/wndr4300-mtd10-nanddump.img --omito ob --bb=skipbad ECC failed: 0 ECC corrected: 48 Number of bad blocks: 0 Number of bbt blocks: 0 Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x and ending at 0x0190... ECC: 16 corrected bitflip(s) at offset 0x00168000 But this is not a showstopper than, since the driver seems to work correctly using the mtd interface. Did you write/erase the any of the partitions by any chance? Hm, I think I played around mounting the jffs2 partition once.. this should be after the CRC checked squashfs, but maybe I used the wrong mtd. This would explain the error. I reflashed the image, since then it boots fine even after using nanddump etc. from initram Ok. Even if you have used the correct mtd device, writing something into that can cause bit-flips in other erase blocks due to the common 'Write Disturb' problem. Now I tried to create a UBI volume using the initramfs-Kernel. I get this kernel crash dump: # ubiattach -m 8 /dev/ubi_ctrl [ 3712.32] UBI: attaching mtd8 to ubi0 [ 3712.51] UBI: scanning is finished [ 3712.52] UBI: empty MTD device detected [ 3712.52] CPU 0 Unable to handle kernel paging request at virtual address , epc == , ra == 802094fc [ 3712.53] Oops[#1]: [ 3712.53] CPU: 0 PID: 1216 Comm: ubiattach Not tainted 3.10.12 #10 [ 3712.53] task: 878b5d50 ti: 8654c000 task.ti: 8654c000 [ 3712.53] $ 0 : 0001 8037c810 [ 3712.53] $ 4 : 87826010 0001 01ff 0200 [ 3712.53] $ 8 : 0005 80064830 [ 3712.53] $12 : d8197822 [ 3712.53] $16 : 878261b8 87826010 86e34000 [ 3712.53] $20 : 0200 86e34500 86e34d00 0007 [ 3712.53] $24 : [ 3712.53] $28 : 8654c000 8654dae8 802094fc [ 3712.53] Hi: [ 3712.53] Lo: 0010 [ 3712.53] epc : (null) [ 3712.53] Not tainted [ 3712.53] ra: 802094fc nand_write_subpage_hwecc+0xa0/0x1c4 Hm, this is a NULL pointer dereference. It seems that the nand_write_subpage_hwecc function tries to run a callback which is not initialized by the ar934x-nfc driver. I will look into that later. In the past, I have tested the ar934x-nfc driver (w/o hw ECC) with the modules provided by the mtdtests package and it passed all tests. Ideally, it should be tested again with hw ECC support but that is quite dangerous on devices which are using a NAND flash only. -Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to enable Seama firmware parser for Ramips?
2013.09.24. 23:57 keltezéssel, Flávio Silveira írta: Jacek Kikiewicz wrote: Don't you have to have partition called rootfs in your definition? Then it should pick it up... Regards, Jacek Hi Jacek, thanks for your quick answer. I don't know, ít's not what I'm seeing in others dts files and when I was starting to port this device I was told to keep only u-boot, u-boot-env and devdata partitions from stock firmware, but I decided to put u-boot-env together with devdata. Here is stock boot log: http://codepad.org/stXQWQSQ Looking at https://dev.openwrt.org/changeset/38114 it seems the parser is disabled for anything else besides ar71xx. Yes, it is disabled by default because it is only tested on ar71xx so far. However it should work on ramips as well, and it will be enabled once I have a chance to test it on the DIR-645. If you want to try it on the DIR-610, you can enable it in the kernel config: 'Device Drivers Memory Technology Device (MTD) support OpenWrt specific MTD options Seama firmware parser' Also, when I look at the parser code itself, it seems that it searches for rootfs in firmware partition, after the kernel https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/mtd/mtdsplit_seama.c?rev=38114 Correct. The Seama images are starting with the kernel and the rootfs is placed after that. At least on the devices I have. -Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/1] [ramips]: Change size of image for DIR-320 B1 to 8MB
DIR-320 B1 has 8MB flash, so building image with this size will good. Signed-off-by: Vladimir Stolyarov xakep6...@yandex.ru --- diff --git a/target/linux/ramips/image/Makefile b/target/linux/ramips/image/Makefile index 5ee76a6..963e97c 100644 --- a/target/linux/ramips/image/Makefile +++ b/target/linux/ramips/image/Makefile @@ -391,7 +391,7 @@ Image/Build/Profile/MPRA1=$(call BuildFirmware/Default4M/$(1),$(1),mpr-a1,MPRA1, Image/Build/Profile/MPRA2=$(call BuildFirmware/Default8M/$(1),$(1),mpr-a2,MPRA2,Linux Kernel Image) Image/Build/Profile/DIR-300-B7=$(call BuildFirmware/Default4M/$(1),$(1),dir-300-b7,DIR-300-B7) -Image/Build/Profile/DIR-320-B1=$(call BuildFirmware/Default4M/$(1),$(1),dir-320-b1,DIR-320-B1) +Image/Build/Profile/DIR-320-B1=$(call BuildFirmware/Default8M/$(1),$(1),dir-320-b1,DIR-320-B1) Image/Build/Profile/NBG-419N=$(call BuildFirmware/Default4M/$(1),$(1),nbg-419n,NBG-419N) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [1/5] AA: ARV4518PWR01. Update machtypes.h
Update machtypes.h to support ARV4518PWR01 diff -urN a/arch/mips/lantiq/machtypes.h b/arch/mips/lantiq/machtypes.h --- a/arch/mips/lantiq/machtypes.h 2013-09-25 13:14:59.0 +0200 +++ b/arch/mips/lantiq/machtypes.h 2013-09-25 13:34:39.665808763 +0200 @@ -34,6 +34,7 @@ /* Arcadyan */ LANTIQ_MACH_ARV3527P, /* Arcor easybox a401 */ LANTIQ_MACH_ARV4510PW, /* Wippies Homebox */ + LANTIQ_MACH_ARV4518PWR01, /* SMC-7908A-ISP */ LANTIQ_MACH_ARV4518PW, /* Airties WAV-221, SMC-7908A-ISP */ LANTIQ_MACH_ARV4519PW, /* Vodafone, Pirelli */ LANTIQ_MACH_ARV4520PW, /* Airties WAV-281, Arcor EasyboxA800 */ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [1/5] AA: ARV4518PWR01. Update machtypes.h
Update machtypes.h to support ARV4518PWR01 Signed off by: José Vázquez Fernández ppvazquez...@gmail.com Tested by: Carles Gadea Roig carles...@gmail.com diff -urN a/arch/mips/lantiq/machtypes.h b/arch/mips/lantiq/machtypes.h --- a/arch/mips/lantiq/machtypes.h 2013-09-25 13:14:59.0 +0200 +++ b/arch/mips/lantiq/machtypes.h 2013-09-25 13:34:39.665808763 +0200 @@ -34,6 +34,7 @@ /* Arcadyan */ LANTIQ_MACH_ARV3527P, /* Arcor easybox a401 */ LANTIQ_MACH_ARV4510PW, /* Wippies Homebox */ + LANTIQ_MACH_ARV4518PWR01, /* SMC-7908A-ISP */ LANTIQ_MACH_ARV4518PW, /* Airties WAV-221, SMC-7908A-ISP */ LANTIQ_MACH_ARV4519PW, /* Vodafone, Pirelli */ LANTIQ_MACH_ARV4520PW, /* Airties WAV-281, Arcor EasyboxA800 */ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [1/5] AA: ARV4518PWR01. Board definition.
Board definition for the ARV4518PWR01.
In the board definition, leds and buttons of the ARV4518PW were used.
Signed off by: José Vázquez Fernández ppvazquez...@gmail.com
Tested by: Carles Gadea Roig carles...@gmail.com
diff -urN a/arch/mips/lantiq/xway/mach-arv.c b/arch/mips/lantiq/xway/mach-arv.c
--- a/arch/mips/lantiq/xway/mach-arv.c 2013-09-17 21:07:00.0 +0200
+++ b/arch/mips/lantiq/xway/mach-arv.c 2013-09-25 13:32:14.013421918 +0200
@@ -516,6 +516,38 @@
arv4510pw_init);
static void __init
+arv4518pwr01_init(void)
+{
+#define ARV4518PWR01_EBU 0
+#define ARV4518PWR01_USB 14
+#define ARV4518PWR01_SWITCH_RESET 13
+#define ARV4518PWR01_ATH_ADDR 0x3f0400
+#define ARV4518PWR01_MAC_ADDR 0x3f0016
+
+ ltq_register_gpio_ebu(ARV4518PWR01_EBU);
+ ltq_add_device_gpio_leds(-1, ARRAY_SIZE(arv4518pw_gpio_leds), arv4518pw_gpio_leds);
+ ltq_register_gpio_keys_polled(-1, LTQ_KEYS_POLL_INTERVAL,
+ARRAY_SIZE(arv4518pw_gpio_keys), arv4518pw_gpio_keys);
+ arv_load_nor(0x40);
+ ltq_pci_data.clock = PCI_CLOCK_INT;
+ ltq_register_pci(ltq_pci_data);
+ xway_register_dwc(ARV4518PWR01_USB);
+ arv_register_ethernet(ARV4518PWR01_MAC_ADDR);
+ arv_register_ath5k(ARV4518PWR01_ATH_ADDR, ARV4518PWR01_MAC_ADDR);
+ ltq_register_ath5k(arv_ath5k_eeprom_data, arv_athxk_eeprom_mac);
+ ltq_register_tapi();
+
+ gpio_request(ARV4518PWR01_SWITCH_RESET, switch);
+ gpio_direction_output(ARV4518PW_SWITCH_RESET, 1);
+ gpio_export(ARV4518PWR01_SWITCH_RESET, 0);
+}
+
+MIPS_MACHINE(LANTIQ_MACH_ARV4518PWR01,
+ ARV4518PWR01,
+ Arcadyan ARV4518PWR01,
+ arv4518pwr01_init);
+
+static void __init
arv4518pw_init(void)
{
#define ARV4518PW_EBU 0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [3/5] AA: ARV4518PWR01. Change leds behavior.
This change the led behavior at init.
With this patch only the power led remains powered on when the board is
flashed with openwrt.
Signed off by: José Vázquez Fernández ppvazquez...@gmail.com
Tested by: Carles Gadea Roig carles...@gmail.com
diff -urN a/arch/mips/lantiq/xway/mach-arv.c b/arch/mips/lantiq/xway/mach-arv.c
--- a/arch/mips/lantiq/xway/mach-arv.c 2013-09-17 21:07:00.0 +0200
+++ b/arch/mips/lantiq/xway/mach-arv.c 2013-09-25 13:43:06.083366539 +0200
@@ -153,16 +153,16 @@
static struct gpio_led
arv4518pw_gpio_leds[] __initdata = {
{ .name = soc:green:power, .gpio = 3, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:adsl, .gpio = 4, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:internet, .gpio = 5, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:wifi, .gpio = 6, .active_low = 1, .default_trigger = default-on },
- { .name = soc:yellow:wps, .gpio = 7, .active_low = 1, .default_trigger = default-on },
- { .name = soc:red:fail, .gpio = 8, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:usb, .gpio = 19, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:voip, .gpio = 100, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:fxs1, .gpio = 101, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:fxs2, .gpio = 102, .active_low = 1, .default_trigger = default-on },
- { .name = soc:green:fxo, .gpio = 103, .active_low = 1, .default_trigger = default-on },
+ { .name = soc:green:adsl, .gpio = 4, .active_low = 1, },
+ { .name = soc:green:internet, .gpio = 5, .active_low = 1, },
+ { .name = soc:green:wifi, .gpio = 6, .active_low = 1, },
+ { .name = soc:yellow:wps, .gpio = 7, .active_low = 1, },
+ { .name = soc:red:fail, .gpio = 8, .active_low = 1, },
+ { .name = soc:green:usb, .gpio = 19, .active_low = 1, },
+ { .name = soc:green:voip, .gpio = 100, .active_low = 1, },
+ { .name = soc:green:fxs1, .gpio = 101, .active_low = 1, },
+ { .name = soc:green:fxs2, .gpio = 102, .active_low = 1, },
+ { .name = soc:green:fxo, .gpio = 103, .active_low = 1, },
};
static struct gpio_keys_button
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [2/5] AA: ARV4518PWR01. Board definition.
Board definition for the ARV4518PWR01.
In the board definition, leds and buttons of the ARV4518PW were used.
Signed off by: José Vázquez Fernández ppvazquez...@gmail.com
Tested by: Carles Gadea Roig carles...@gmail.com
diff -urN a/arch/mips/lantiq/xway/mach-arv.c b/arch/mips/lantiq/xway/mach-arv.c
--- a/arch/mips/lantiq/xway/mach-arv.c 2013-09-17 21:07:00.0 +0200
+++ b/arch/mips/lantiq/xway/mach-arv.c 2013-09-25 13:32:14.013421918 +0200
@@ -516,6 +516,38 @@
arv4510pw_init);
static void __init
+arv4518pwr01_init(void)
+{
+#define ARV4518PWR01_EBU 0
+#define ARV4518PWR01_USB 14
+#define ARV4518PWR01_SWITCH_RESET 13
+#define ARV4518PWR01_ATH_ADDR 0x3f0400
+#define ARV4518PWR01_MAC_ADDR 0x3f0016
+
+ ltq_register_gpio_ebu(ARV4518PWR01_EBU);
+ ltq_add_device_gpio_leds(-1, ARRAY_SIZE(arv4518pw_gpio_leds), arv4518pw_gpio_leds);
+ ltq_register_gpio_keys_polled(-1, LTQ_KEYS_POLL_INTERVAL,
+ARRAY_SIZE(arv4518pw_gpio_keys), arv4518pw_gpio_keys);
+ arv_load_nor(0x40);
+ ltq_pci_data.clock = PCI_CLOCK_INT;
+ ltq_register_pci(ltq_pci_data);
+ xway_register_dwc(ARV4518PWR01_USB);
+ arv_register_ethernet(ARV4518PWR01_MAC_ADDR);
+ arv_register_ath5k(ARV4518PWR01_ATH_ADDR, ARV4518PWR01_MAC_ADDR);
+ ltq_register_ath5k(arv_ath5k_eeprom_data, arv_athxk_eeprom_mac);
+ ltq_register_tapi();
+
+ gpio_request(ARV4518PWR01_SWITCH_RESET, switch);
+ gpio_direction_output(ARV4518PW_SWITCH_RESET, 1);
+ gpio_export(ARV4518PWR01_SWITCH_RESET, 0);
+}
+
+MIPS_MACHINE(LANTIQ_MACH_ARV4518PWR01,
+ ARV4518PWR01,
+ Arcadyan ARV4518PWR01,
+ arv4518pwr01_init);
+
+static void __init
arv4518pw_init(void)
{
#define ARV4518PW_EBU 0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [4/5] AA: ARV4518PWR01. Image and config generation.
Generates the ARV4518PWR01 image and defines the board in target.mk Signed off by: José Vázquez Fernández ppvazquez...@gmail.com Tested by: Carles Gadea Roig carles...@gmail.com diff -urN a/target/linux/lantiq/danube/profiles/002-arcadyan.mk b/target/linux/lantiq/danube/profiles/002-arcadyan.mk --- a/target/linux/lantiq/danube/profiles/002-arcadyan.mk 2013-09-17 20:14:40.0 +0200 +++ b/target/linux/lantiq/danube/profiles/002-arcadyan.mk 2013-09-25 13:57:11.786318465 +0200 @@ -35,6 +35,19 @@ $(eval $(call Profile,ARV4518PW)) +define Profile/ARV4518PWR01 + NAME:=ARV4518PWR01 - SMC7908A-ISP + PACKAGES:= kmod-usb-core kmod-usb-dwc-otg kmod-ledtrig-usbdev \ + kmod-ath5k wpad-mini \ + kmod-ltq-dsl-firmware-a-danube +endef + +define Profile/ARV4518PWR01/Description + Package set optimized for the ARV4518PWR01 +endef + +$(eval $(call Profile,ARV4518PWR01)) + define Profile/ARV4519PW NAME:=ARV4519PW - Vodafone, Pirelli PACKAGES:= kmod-usb-core kmod-usb-dwc-otg kmod-ledtrig-usbdev \ diff -urN a/target/linux/lantiq/image/Makefile b/target/linux/lantiq/image/Makefile --- a/target/linux/lantiq/image/Makefile 2013-09-17 20:14:43.0 +0200 +++ b/target/linux/lantiq/image/Makefile 2013-09-25 14:31:13.396636757 +0200 @@ -109,6 +109,7 @@ Image/BuildKernel/Profile/ARV3527P=$(call Image/BuildKernel/Template,ARV3527P,$(xway_cmdline)) Image/BuildKernel/Profile/ARV4510PW=$(call Image/BuildKernel/Template,ARV4510PW,$(xway_cmdline)) Image/BuildKernel/Profile/ARV4518PW=$(call Image/BuildKernel/Template,ARV4518PW,$(xway_cmdline)) +Image/BuildKernel/Profile/ARV4518PWR01=$(call Image/BuildKernel/Template,ARV4518PWR01,$(xway_cmdline)) Image/BuildKernel/Profile/ARV4519PW=$(call Image/BuildKernel/Template,ARV4519PW,$(xway_cmdline)) Image/BuildKernel/Profile/ARV4520PW=$(call Image/BuildKernel/Template,ARV4520PW,$(xway_cmdline)) Image/BuildKernel/Profile/ARV4525PW=$(call Image/BuildKernel/Template,ARV4525PW,$(xway_cmdline)) @@ -125,6 +126,7 @@ Image/Build/Profile/ARV3527P=$(call Image/Build/$(1),$(1),ARV3527P) Image/Build/Profile/ARV4510PW=$(call Image/Build/$(1),$(1),ARV4510PW) Image/Build/Profile/ARV4518PW=$(call Image/Build/$(1),$(1),ARV4518PW) +Image/Build/Profile/ARV4518PWR01=$(call Image/Build/$(1),$(1),ARV4518PWR01) Image/Build/Profile/ARV4519PW=$(call Image/Build/$(1),$(1),ARV4519PW,BRNDA4519,0x12345678,memsize=32) Image/Build/Profile/ARV4520PW=$(call Image/Build/$(1),$(1),ARV4520PW,BRNDANUBE,0x12345678,memsize=32) Image/Build/Profile/ARV4525PW=$(call Image/Build/$(1),$(1),ARV4525PW,BRNDTW502,0x12345678,memsize=32) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [1/5] AA: ARV4518PWR01. Update machtypes.h
On 25/09/13 17:14, José Vázquez Fernández wrote: Update machtypes.h to support ARV4518PWR01 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel Hi, the series looks good i will add it to my queue John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [5/5] AA: ARV4518PWR01. Led definitions for onboard devices.
Led definitions for onboard devices. Defines some leds when the related devices are activated/deactivated. Signed off by: José Vázquez Fernández ppvazquez...@gmail.com Tested by: Carles Gadea Roig carles...@gmail.com diff -urN a/target/linux/lantiq/base-files/etc/uci-defaults/leds b/target/linux/lantiq/base-files/etc/uci-defaults/leds --- a/target/linux/lantiq/base-files/etc/uci-defaults/leds 2013-09-17 20:14:43.0 +0200 +++ b/target/linux/lantiq/base-files/etc/uci-defaults/leds 2013-09-25 13:54:06.665649834 +0200 @@ -10,6 +10,18 @@ board=$(lantiq_board_name) case $board in +ARV4518PW) + ucidef_set_led_wlan wifi wifi soc:green:wifi phy0radio + ucidef_set_led_netdev internet internet soc:green:internet pppoe-wan + ucidef_set_led_usbdev usb USB soc:green:usb 1-1 + ;; + +ARV4518PWR01) + ucidef_set_led_wlan wifi wifi soc:green:wifi phy0radio + ucidef_set_led_netdev internet internet soc:green:internet pppoe-wan + ucidef_set_led_usbdev usb USB soc:green:usb 1-1 + ;; + ARV4520PW|ARV452CPW) ucidef_set_led_netdev wifi wifi soc:blue:wifi wlan0 ucidef_set_led_usbdev usb USB soc:blue:usb 1-1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] atheros: fix kernel warning about usage of reset gpio
2013.09.17. 22:15 keltezéssel, Michael Heimpold írta: During a reset the gpiolib warns about using the reset gpio without explicit requesting it before: [ 147.93] [ cut here ] [ 147.93] WARNING: at drivers/gpio/gpiolib.c:103 gpio_ensure_requested+0x68/0xcc() [ 147.93] autorequest GPIO-5 [ 147.93] Modules linked in: ath5k ath mac80211 ipv6 cfg80211 compat arc4 crypto_blkcipher aead gpio_button_hotplug [ 147.93] Call Trace: [ 147.93] [8004e3bc] dump_stack+0x8/0x34 [ 147.93] [80058430] warn_slowpath_common+0x78/0xa4 [ 147.93] [800584e4] warn_slowpath_fmt+0x2c/0x38 [ 147.93] [80166f18] gpio_ensure_requested+0x68/0xcc [ 147.93] [80167264] gpio_direction_output+0xdc/0x168 [ 147.93] [8004aba8] ar2315_restart+0x28/0x54 [ 147.93] [80069778] sys_reboot+0x178/0x1c0 [ 147.93] [80043670] stack_done+0x20/0x40 [ 147.93] [ 147.93] ---[ end trace 2c7a53d8549562d6 ]--- This is fixed with this patch by using another gpiolib api call which includes the missing request. Signed-off-by: Michael Heimpold m...@heimpold.de Applied. Thanks, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add hwmon driver for ADT7410
2013.09.22. 0:55 keltezéssel, Hartmut Knaack írta: Add support for the ADT7410 hwmon driver, a high precision I2C temperature sensor. Signed-off-by: Hartmut Knaack knaac...@gmx.de Applied. Thanks, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Add support for industrial-io and AD799x
2013.09.22. 0:55 keltezéssel, Hartmut Knaack írta: Add support for industrial IO core and (still staging) driver for AD799x, a high precision I2C ADC family. Signed-off-by: Hartmut Knaack knaac...@gmx.de Applied. Thanks, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to enable Seama firmware parser for Ramips?
Hi Gabor Gabor Juhos wrote: 2013.09.24. 23:57 keltezéssel, Flávio Silveira írta: Jacek Kikiewicz wrote: Don't you have to have partition called rootfs in your definition? Then it should pick it up... Regards, Jacek Hi Jacek, thanks for your quick answer. I don't know, ít's not what I'm seeing in others dts files and when I was starting to port this device I was told to keep only u-boot, u-boot-env and devdata partitions from stock firmware, but I decided to put u-boot-env together with devdata. Here is stock boot log: http://codepad.org/stXQWQSQ Looking at https://dev.openwrt.org/changeset/38114 it seems the parser is disabled for anything else besides ar71xx. Yes, it is disabled by default because it is only tested on ar71xx so far. However it should work on ramips as well, and it will be enabled once I have a chance to test it on the DIR-645. If you want to try it on the DIR-610, you can enable it in the kernel config: 'Device Drivers Memory Technology Device (MTD) support OpenWrt specific MTD options Seama firmware parser' Here is my feedback, it seems to be working, bootlog below: http://codepad.org/JyXaTjrA Let me know if you need anything else! Thanks! Also, when I look at the parser code itself, it seems that it searches for rootfs in firmware partition, after the kernel https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/mtd/mtdsplit_seama.c?rev=38114 Correct. The Seama images are starting with the kernel and the rootfs is placed after that. At least on the devices I have. -Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 0/2] i.MX6 U-Boot updates
While investigating what it would take to add support for our boards to OpenWRT, I ran across a snag building U-Boot for Wandboard. The Denx FTP server is rejecting requests for a tar-ball download, and I figured I'd offer up a solution, and add the easy part of support for our Nitrogen6x boards (which are in main-line U-Boot). Eric Nelson (2): U-Boot: Use git instead of FTP, consolidate download uboot-imx6: add support for Nitrogen6x boards package/boot/uboot-envtools/Makefile | 10 - package/boot/uboot-imx6/Makefile | 39 2 files changed, 40 insertions(+), 9 deletions(-) -- 1.8.1.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/2] uboot-imx6: add support for Nitrogen6x boards
Signed-off-by: Eric Nelson eric.nel...@boundarydevices.com --- package/boot/uboot-imx6/Makefile | 30 ++ 1 file changed, 30 insertions(+) diff --git a/package/boot/uboot-imx6/Makefile b/package/boot/uboot-imx6/Makefile index 080079f..1f73460 100644 --- a/package/boot/uboot-imx6/Makefile +++ b/package/boot/uboot-imx6/Makefile @@ -37,7 +37,37 @@ define uboot/wandboard_quad TITLE:=U-Boot for the Wandboard Quad endef +define uboot/nitrogen6q + TITLE:=U-Boot for Nitrogen6x/SABRE Lite (MX6Q/1GB) +endef + +define uboot/nitrogen6q2g + TITLE:=U-Boot for Nitrogen6x i.MX6Quad 2GB board +endef + +define uboot/nitrogen6s + TITLE:=U-Boot for Nitrogen6x i.MX6Solo 512MB board +endef + +define uboot/nitrogen6s1g + TITLE:=U-Boot for Nitrogen6x i.MX6Solo 1GB board +endef + +define uboot/nitrogen6dl + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 512MB board +endef + +define uboot/nitrogen6dl1g + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 1GB board +endef + UBOOTS := \ + nitrogen6q \ + nitrogen6q2g \ + nitrogen6dl \ + nitrogen6dl1g \ + nitrogen6s \ + nitrogen6s1g \ wandboard_solo \ wandboard_dl \ wandboard_quad -- 1.8.1.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] OpenWRT N00b hoping to add support for i.MX6 boards
Hi all, Nudged by some customers, I've been looking at how to add support for our i.MX6-based boards to OpenWRT to make their lives easier, and have some questions. U-Boot seems relatively simple for our Nitrogen6X and SABRE Lite boards, which are supported directly by Main-line U-Boot by extending the support currently in place for Wandboards. I sent patches for that a moment ago. I'm not quite sure what to do with the kernel. There is support for i.MX6, but it appears to be based on 3.10, and though we expect to have a 3.10 kernel version in the coming weeks for our i.MX6Q (quad-core) boards, I wouldn't recommend it for typical applications. Our production ready kernel version is based on 3.0.35, and I'm not sure whether to re-factor things in the target/linux/imx6/ directory or to simply create a target/linux/boundary/ directory. We're hoping to point at our Github repository for the kernel sources, and I didn't see any references to other git repositories in the target/linux/ tree. Is there OpenWRT policy regarding use of main-line? Any guidance is appreciated. Regards, Eric Nelson Boundary Devices http://boundarydevices.com/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] U-Boot: Use git instead of FTP, consolidate download
Hi Eric, On Wed, Sep 25, 2013 at 03:43:00PM -0700, Eric Nelson wrote: While attempting to build for i.MX6, the FTP transfer of U-Boot v2013.07 failed. I'm not certain whether ftp access to tarballs has been promised by Denx, but it seems more reasonable to use the git:// protocol which is in wide use within the U-Boot community. NACK. Bumping the package every 3 monts with new release is good enough IMO. About the download issue... Please remove uboot source in your dl directory. Then run: make package/uboot-envtools/download V=s and/or make package/uboot-imx6/download V=s Many people use uboot-envtools package and no download issues were reported. Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] uboot-imx6: add support for Nitrogen6x boards
Hi Eric, On Wed, Sep 25, 2013 at 03:43:01PM -0700, Eric Nelson wrote: Signed-off-by: Eric Nelson eric.nel...@boundarydevices.com --- package/boot/uboot-imx6/Makefile | 30 ++ 1 file changed, 30 insertions(+) diff --git a/package/boot/uboot-imx6/Makefile b/package/boot/uboot-imx6/Makefile index 080079f..1f73460 100644 --- a/package/boot/uboot-imx6/Makefile +++ b/package/boot/uboot-imx6/Makefile @@ -37,7 +37,37 @@ define uboot/wandboard_quad TITLE:=U-Boot for the Wandboard Quad endef +define uboot/nitrogen6q + TITLE:=U-Boot for Nitrogen6x/SABRE Lite (MX6Q/1GB) +endef + +define uboot/nitrogen6q2g + TITLE:=U-Boot for Nitrogen6x i.MX6Quad 2GB board +endef + +define uboot/nitrogen6s + TITLE:=U-Boot for Nitrogen6x i.MX6Solo 512MB board +endef + +define uboot/nitrogen6s1g + TITLE:=U-Boot for Nitrogen6x i.MX6Solo 1GB board +endef + +define uboot/nitrogen6dl + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 512MB board +endef Shouldn't here be 1024MB? +define uboot/nitrogen6dl1g + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 1GB board +endef This board does not exist in 2013.07 uboot nor in the git repo. You mean nitrogen6dl2g, right? Please double check all the boards one more time. Update your patch and sort the boards alphabetically. I know wandboards are not sorted that way, so you can include that change too or I'll do it in separate commit. Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] U-Boot: Use git instead of FTP, consolidate download
Hi Luka, On 09/25/2013 04:55 PM, Luka Perkov wrote: Hi Eric, On Wed, Sep 25, 2013 at 03:43:00PM -0700, Eric Nelson wrote: While attempting to build for i.MX6, the FTP transfer of U-Boot v2013.07 failed. I'm not certain whether ftp access to tarballs has been promised by Denx, but it seems more reasonable to use the git:// protocol which is in wide use within the U-Boot community. NACK. Bumping the package every 3 monts with new release is good enough IMO. I wasn't suggesting anything different, and the patch includes the same tag (v2013.07). Decisions about when to update are completely separate from the protcol, right? About the download issue... Please remove uboot source in your dl directory. Then run: make package/uboot-envtools/download V=s and/or make package/uboot-imx6/download V=s Many people use uboot-envtools package and no download issues were reported. I've tried this on a number of Ubuntu-based machines (10.04/13.04) and wget versions with the same result: ~/openwrt$ make package/uboot-envtools/download V=s make[1]: Entering directory `/home/ericn/openwrt' make[2]: Entering directory `/home/ericn/openwrt/package/boot/uboot-envtools' mkdir -p /home/ericn/openwrt/dl /home/ericn/openwrt/scripts/download.pl /home/ericn/openwrt/dl u-boot-2013.07.tar.bz2 8445162690052e6afd4b8f87af2bb557 ftp://ftp.denx.de/pub/u-boot; --2013-09-25 17:26:04-- ftp://ftp.denx.de/pub/u-boot/u-boot-2013.07.tar.bz2 = '-' Resolving ftp.denx.de (ftp.denx.de)... 81.169.202.5 Connecting to ftp.denx.de (ftp.denx.de)|81.169.202.5|:21... connected. Logging in as anonymous ... Error in server greeting. Retrying. --2013-09-25 17:26:11-- ftp://ftp.denx.de/pub/u-boot/u-boot-2013.07.tar.bz2 (try: 2) = '-' Connecting to ftp.denx.de (ftp.denx.de)|81.169.202.5|:21... connected. Logging in as anonymous ... Error in server greeting. Retrying. ... --2013-09-25 17:26:23-- http://downloads.openwrt.org/sources/u-boot-2013.07.tar.bz2 Resolving downloads.openwrt.org (downloads.openwrt.org)... 78.24.191.177 Connecting to downloads.openwrt.org (downloads.openwrt.org)|78.24.191.177|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-09-25 17:26:23 ERROR 404: Not Found. Download failed. No more mirrors to try - giving up. Using curl also fails: ~/openwrt$ curl ftp://ftp.denx.de/pub/u-boot/u-boot-2013.07.tar.bz2 -o u-boot-2013.07.tar.bz2 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- 0:00:01 --:--:-- 0 curl: (8) Got a 425 ftp-server response when 220 was expected I don't have a strong preference for one route over the other, I just thought I'd offer up a patch in case this package was sitting broken in the repository. Is anyone else able to grab this tar-ball from Denx? Is there/should there be a fallback at openwrt.org? We're more than happy to host a mirror if that's what it takes to make this work, though we don't have any ftp servers (only git and http). I also know that the git server at denx.de is really robust, since I pull from it at least a couple of times a week. Please advise, Eric ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenWRT N00b hoping to add support for i.MX6 boards
Hi Eric, On Wed, Sep 25, 2013 at 03:58:58PM -0700, Eric Nelson wrote: I'm not quite sure what to do with the kernel. There is support for i.MX6, but it appears to be based on 3.10, and though we expect to have a 3.10 kernel version in the coming weeks for our i.MX6Q (quad-core) boards, I wouldn't recommend it for typical applications. imx6 will stay on 3.10 for some time at least until the new BB release is out. Our production ready kernel version is based on 3.0.35, and I'm not sure whether to re-factor things in the target/linux/imx6/ directory or to simply create a target/linux/boundary/ directory. Don't create target/linux/boundary/ directory, add support for your boards on top of existing imx6 target. There are some Gateworks boards which supported. You can use them as a reference. We're hoping to point at our Github repository for the kernel sources, and I didn't see any references to other git repositories in the target/linux/ tree. Is there OpenWRT policy regarding use of main-line? That won't be accepted, see above. I'm trying to keep imx6 clean with backports when needed (patches not in upstream are ok too). Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] uboot-imx6: add support for Nitrogen6x boards
Thanks Luka, On 09/25/2013 05:16 PM, Luka Perkov wrote: Hi Eric, snip +define uboot/nitrogen6dl + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 512MB board +endef Shouldn't here be 1024MB? Ouch! You're right of course. You'd think I'd know our own product lineup without having to read boards.cfg. Can you tell that the DL variants aren't very popular? It seems that everybody either wants speed and goes for the Quad, or price, and goes for the Solo. +define uboot/nitrogen6dl1g + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 1GB board +endef This board does not exist in 2013.07 uboot nor in the git repo. You mean nitrogen6dl2g, right? Please double check all the boards one more time. Will do. Update your patch and sort the boards alphabetically. I know wandboards are not sorted that way, so you can include that change too or I'll do it in separate commit. I can take care of that. It's probably cleaner (easier to read) in two commits though. My first pass made it look like we were replacing wandboards with nitrogen6's... Regards, Eric ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to enable Seama firmware parser for Ramips?
Hi Gabor, Gabor Juhos wrote: 2013.09.25. 21:07 keltezéssel, Flávio Silveira írta: ... If you want to try it on the DIR-610, you can enable it in the kernel config: 'Device Drivers Memory Technology Device (MTD) support OpenWrt specific MTD options Seama firmware parser' Here is my feedback, it seems to be working, bootlog below: http://codepad.org/JyXaTjrA Nice, although the jffs2 messages are ugly. Let me know if you need anything else! How did you flash the image? Those messages are present even after sysupgrade? -Gabor I flashed straight from stock firmware, because that what I was testing. I didn't try after sysupgrade, do you want me to? Regards, Flavio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] uboot-imx6: alphabetize wandboard variants
Signed-off-by: Eric Nelson eric.nel...@boundarydevices.com --- package/boot/uboot-imx6/Makefile | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/package/boot/uboot-imx6/Makefile b/package/boot/uboot-imx6/Makefile index 21c7b09..21fc9bd 100644 --- a/package/boot/uboot-imx6/Makefile +++ b/package/boot/uboot-imx6/Makefile @@ -24,10 +24,6 @@ define uboot/Default IMAGE:= endef -define uboot/wandboard_solo - TITLE:=U-Boot for the Wandboard Solo -endef - define uboot/wandboard_dl TITLE:=U-Boot for the Wandboard Dual Lite endef @@ -36,10 +32,14 @@ define uboot/wandboard_quad TITLE:=U-Boot for the Wandboard Quad endef +define uboot/wandboard_solo + TITLE:=U-Boot for the Wandboard Solo +endef + UBOOTS := \ - wandboard_solo \ wandboard_dl \ - wandboard_quad + wandboard_quad \ + wandboard_solo define Package/uboot/template define Package/uboot-imx6-$(1) -- 1.8.1.2 ___ 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] uboot-imx6: add support for Nitrogen6x boards
Signed-off-by: Eric Nelson eric.nel...@boundarydevices.com --- V2 alphabetizes the list and fixes nitrogen6dl/dl2g. Depends on patch uboot-imx6: alphabetize wandboard variants Patch 1/2 was nacked, so no update will be sent. package/boot/uboot-imx6/Makefile | 30 ++ 1 file changed, 30 insertions(+) diff --git a/package/boot/uboot-imx6/Makefile b/package/boot/uboot-imx6/Makefile index 21fc9bd..009d579 100644 --- a/package/boot/uboot-imx6/Makefile +++ b/package/boot/uboot-imx6/Makefile @@ -24,6 +24,30 @@ define uboot/Default IMAGE:= endef +define uboot/nitrogen6dl + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 1GB board +endef + +define uboot/nitrogen6dl2g + TITLE:=U-Boot for Nitrogen6x i.MX6Dual-Lite 2GB board +endef + +define uboot/nitrogen6q + TITLE:=U-Boot for Nitrogen6x/SABRE Lite (MX6Q/1GB) +endef + +define uboot/nitrogen6q2g + TITLE:=U-Boot for Nitrogen6x i.MX6Quad 2GB board +endef + +define uboot/nitrogen6s + TITLE:=U-Boot for Nitrogen6x i.MX6Solo 512MB board +endef + +define uboot/nitrogen6s1g + TITLE:=U-Boot for Nitrogen6x i.MX6Solo 1GB board +endef + define uboot/wandboard_dl TITLE:=U-Boot for the Wandboard Dual Lite endef @@ -37,6 +61,12 @@ define uboot/wandboard_solo endef UBOOTS := \ + nitrogen6dl \ + nitrogen6dl1g \ + nitrogen6q \ + nitrogen6q2g \ + nitrogen6s \ + nitrogen6s1g \ wandboard_dl \ wandboard_quad \ wandboard_solo -- 1.8.1.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
