Re: [OpenWrt-Devel] Testing packages (and images) under KVM/Qemu
On 13/06/2018 22:08, Philip Prindeville wrote: Hi all, Does anyone have a baseline KVM machine description (i.e. an domain.xml file) for testing x86_64 images? I’ve spotted a bug in Busybox that requires some debugging to root-cause it, but I don’t want to do this on an actual production router for obvious reasons and I’m a little short on development hardware right now (waiting for the PC Engines APU.4B4 to start shipping). My KVM has igb interfaces, so I can do the igb-vf stuff which is more efficient than the other NIC emulation. That said, most of the testing I need to do isn’t performance sensitive… it’s more about verifying basic sanity after version bumps, applying new patches, etc. A x86_64 (or i386) profile specifically for KVM testing might also be handy… sort of like the armvirt target. Does anyone want to start a wiki page or discussion about testing under KVM? I figure that I’m probably not the only person to find himself in this situation… and a logical follow-on for CI/CB might also be CT (i.e. booting a VM image, configuring it, seeing if it responds to pings, passes through packets, etc). Thanks, -Philip ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel There is an article about that, it's reasonably recent (there is a walk-through using it on Debian 7.1) but it may not be plug-and-play. https://openwrt.org/docs/guide-user/virtualization/qemu#openwrt_in_qemu_x86-64 I don't know much about the topic myself, so I can't help much more than this. If you try it and find issues please update the article if you can. -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
[OpenWrt-Devel] Testing packages (and images) under KVM/Qemu
Hi all, Does anyone have a baseline KVM machine description (i.e. an domain.xml file) for testing x86_64 images? I’ve spotted a bug in Busybox that requires some debugging to root-cause it, but I don’t want to do this on an actual production router for obvious reasons and I’m a little short on development hardware right now (waiting for the PC Engines APU.4B4 to start shipping). My KVM has igb interfaces, so I can do the igb-vf stuff which is more efficient than the other NIC emulation. That said, most of the testing I need to do isn’t performance sensitive… it’s more about verifying basic sanity after version bumps, applying new patches, etc. A x86_64 (or i386) profile specifically for KVM testing might also be handy… sort of like the armvirt target. Does anyone want to start a wiki page or discussion about testing under KVM? I figure that I’m probably not the only person to find himself in this situation… and a logical follow-on for CI/CB might also be CT (i.e. booting a VM image, configuring it, seeing if it responds to pings, passes through packets, etc). Thanks, -Philip ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Merged: x86: fix bios mkimage during efi image generation
The original work is about a year old now, I think. What do we still need to make it into master? Also, how did the target/host Makefile issue for sfdisk end up being resolved? Thanks, -Philip > On Mar 14, 2018, at 12:18 PM, Jo-Philipp Wich wrote: > > Merged into my staging tree at > http://git.openwrt.org/?p=openwrt/staging/jow.git. > > Thank you! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/4] tools: build squashfs (v3) for ath79
13.06.2018 10:51, Zoltan HERPAI: Certain Netgear devices use BE squashfs for the kernel image. As squashfs4 only supports creating LE images, add squashfs (v3) into the tools to be built for ath79. Trying to use an LE squashfs (thus trying to use squashfs4 only for building the image) for the kernel image results in the bootloader barfing and stopping. Signed-off-by: Zoltan HERPAI --- tools/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/Makefile b/tools/Makefile index d2b5daf..c8ef02c 100644 --- a/tools/Makefile +++ b/tools/Makefile @@ -31,6 +31,7 @@ tools-$(CONFIG_TARGET_orion_generic) += wrt350nv2-builder upslug2 tools-$(CONFIG_TARGET_x86) += qemu tools-$(CONFIG_TARGET_mxs) += elftosb sdimage tools-$(CONFIG_TARGET_ar71xx) += lzma-old squashfs +tools-$(CONFIG_TARGET_ath79) += squashfs tools-$(CONFIG_USES_MINOR) += kernel2minor tools-y += lzma squashfs4 tools-$(BUILD_B43_TOOLS) += b43-tools Hey Zoltan, I tried to do exactly the same at time I noticed the issue. If I apply your patch, the following (and even more related) new warnings are shown on my system: tools/Makefile:153: warning: overriding recipe for target 'tools/squashfs/clean' tools/Makefile:153: warning: ignoring old recipe for target 'tools/squashfs/clean' tools/Makefile:153: warning: overriding recipe for target 'tools/squashfs/download' tools/Makefile:153: warning: ignoring old recipe for target 'tools/squashfs/download' tools/Makefile:153: warning: overriding recipe for target 'tools/squashfs/prepare' tools/Makefile:153: warning: ignoring old recipe for target 'tools/squashfs/prepare' tools/Makefile:153: warning: overriding recipe for target 'tools/squashfs/compile' I've no idea what is going wrong. Instead I've the following change in my local tree since a few days (but didn't managed to send it yet): diff --git a/tools/Makefile b/tools/Makefile index d2b5daf..b546c64 100644 --- a/tools/Makefile +++ b/tools/Makefile @@ -30,7 +30,10 @@ tools-y += mtools dosfstools libressl tools-$(CONFIG_TARGET_orion_generic) += wrt350nv2-builder upslug2 tools-$(CONFIG_TARGET_x86) += qemu tools-$(CONFIG_TARGET_mxs) += elftosb sdimage -tools-$(CONFIG_TARGET_ar71xx) += lzma-old squashfs +tools-$(CONFIG_TARGET_ar71xx) += lzma-old +ifeq ($(CONFIG_TARGET_ar71xx)$(CONFIG_TARGET_ath79),y) + tools-y += squashfs +endif tools-$(CONFIG_USES_MINOR) += kernel2minor tools-y += lzma squashfs4 tools-$(BUILD_B43_TOOLS) += b43-tools Using this approach the squashfs3 binary is build for ar71xx and ath79 without these warning. Mathias ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/2] gemini: Add appropriate Wireless kernel modules
The D-Link DIR-685 has a RealTek RT2880 mini-PCI card in a slot. Activate the appropriate kernel module. The Square One SQ201 has a Ralink RT61-based mini-PCI card. Activate the appropriate kernel modules. This fixes the previous error just activating the firmware: the kernel module will bring in the firmware it needs. Signed-off-by: Linus Walleij --- target/linux/gemini/image/Makefile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/target/linux/gemini/image/Makefile b/target/linux/gemini/image/Makefile index b631452a0ffb..ba2ee02bfa7d 100644 --- a/target/linux/gemini/image/Makefile +++ b/target/linux/gemini/image/Makefile @@ -89,7 +89,8 @@ GEMINI_NAS_PACKAGES:=kmod-md-mod kmod-md-linear kmod-md-multipath \ define Device/dlink-dir-685 DEVICE_TITLE := D-Link DIR-685 Xtreme N Storage Router DEVICE_PACKAGES := $(GEMINI_NAS_PACKAGES) \ - kmod-switch-rtl8366rb swconfig + kmod-switch-rtl8366rb swconfig \ + rt2800-pci IMAGES += dir685-image IMAGE/dir685-image := dir685-images endef @@ -119,7 +120,7 @@ TARGET_DEVICES += rut1xx define Device/sq201 DEVICE_TITLE := ITian Square One SQ201 - DEVICE_PACKAGES := $(GEMINI_NAS_PACKAGES) rt61-pci-firmware + DEVICE_PACKAGES := $(GEMINI_NAS_PACKAGES) rt61-pci endef TARGET_DEVICES += sq201 -- 2.17.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] gemini: Cook a WRGG firmware image
This makes the Gemini build a WRGG-type firmware update image for the DIR-685. This should hopefully install the kernel from the web firmware upgrade API on the product switching it permanently to use OpenWRT. Signed-off-by: Linus Walleij --- target/linux/gemini/image/Makefile | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/target/linux/gemini/image/Makefile b/target/linux/gemini/image/Makefile index 3e122fc457ae..b631452a0ffb 100644 --- a/target/linux/gemini/image/Makefile +++ b/target/linux/gemini/image/Makefile @@ -7,9 +7,17 @@ include $(TOPDIR)/rules.mk include $(INCLUDE_DIR)/image.mk -# Just copy the zImage for D-Link DIR-685 +# Cook a "WRGG" image, this board is apparently one in the D-Link +# WRGG family and uses the exact same firmware format as other +# D-Link devices. define Build/dir685-images - cp $(IMAGE_KERNEL) $(BIN_DIR)/$(IMG_PREFIX)-dir685-zImage + mkwrggimg -i $(IMAGE_KERNEL) \ + -o $(BIN_DIR)/$(IMG_PREFIX)-dir685-fwupdate.bin \ + -d /dev/mtdblock/1 \ + -s wrgns01_dlwbr_dir685RBWW \ + -v 'N/A' \ + -m dir685 \ + -B 96bb endef # Build D-Link DNS-313 images using the special header tool. -- 2.17.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] iptables: increment PKG_RELEASE to force update
While support for the FLOWOFFLOAD target is available in the firmware images, it is still missing in some of the binary packages on downloads.openwrt.org, e.g. for the mipsel_mips32 architecture. Increment PKG_RELEASE to force an update of these packages. Also adjust the package description to include the FLOWOFFLOAD target. Signed-off-by: Mirko Parthey --- If accepted, I would also suggest backporting this to openwrt-18.06. package/network/utils/iptables/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/package/network/utils/iptables/Makefile b/package/network/utils/iptables/Makefile index d70dc11..44e24b2 100644 --- a/package/network/utils/iptables/Makefile +++ b/package/network/utils/iptables/Makefile @@ -10,7 +10,7 @@ include $(INCLUDE_DIR)/kernel.mk PKG_NAME:=iptables PKG_VERSION:=1.6.2 -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_SOURCE_PROTO:=git PKG_SOURCE_URL:=https://git.netfilter.org/iptables @@ -88,6 +88,7 @@ IP firewall administration tool. - DNAT - DROP - REJECT + - FLOWOFFLOAD - LOG - MARK - MASQUERADE -- 2.1.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/4] ath79: move Netgear build code into a common makefile
Signed-off-by: Zoltan HERPAI --- target/linux/ath79/image/common-netgear.mk | 22 ++ target/linux/ath79/image/generic.mk| 24 +--- 2 files changed, 23 insertions(+), 23 deletions(-) create mode 100644 target/linux/ath79/image/common-netgear.mk diff --git a/target/linux/ath79/image/common-netgear.mk b/target/linux/ath79/image/common-netgear.mk new file mode 100644 index 000..ca4e005 --- /dev/null +++ b/target/linux/ath79/image/common-netgear.mk @@ -0,0 +1,22 @@ +define Build/netgear-squashfs + rm -rf $@.fs $@.squashfs + mkdir -p $@.fs/image + cp $@ $@.fs/image/uImage + $(STAGING_DIR_HOST)/bin/mksquashfs-lzma \ + $@.fs $@.squashfs -be \ + -noappend -root-owned -b 65536 \ + $(if $(SOURCE_DATE_EPOCH),-fixed-time $(SOURCE_DATE_EPOCH)) + + dd if=/dev/zero bs=1k count=1 >> $@.squashfs + mkimage \ + -A mips -O linux -T filesystem -C none \ + -M $(NETGEAR_KERNEL_MAGIC) \ + -a 0xbf07 -e 0xbf07 \ + -n 'MIPS $(VERSION_DIST) Linux-$(LINUX_VERSION)' \ + -d $@.squashfs $@ + rm -rf $@.squashfs $@.fs +endef + +define Build/netgear-uImage + $(call Build/uImage,$(1) -M $(NETGEAR_KERNEL_MAGIC)) +endef diff --git a/target/linux/ath79/image/generic.mk b/target/linux/ath79/image/generic.mk index 9475d0a..6e662ce 100644 --- a/target/linux/ath79/image/generic.mk +++ b/target/linux/ath79/image/generic.mk @@ -1,26 +1,4 @@ -define Build/netgear-squashfs - rm -rf $@.fs $@.squashfs - mkdir -p $@.fs/image - cp $@ $@.fs/image/uImage - $(STAGING_DIR_HOST)/bin/mksquashfs-lzma \ - $@.fs $@.squashfs \ - -noappend -root-owned -be -b 65536 \ - $(if $(SOURCE_DATE_EPOCH),-fixed-time $(SOURCE_DATE_EPOCH)) - - dd if=/dev/zero bs=1k count=1 >> $@.squashfs - mkimage \ - -A mips -O linux -T filesystem -C none \ - -M $(NETGEAR_KERNEL_MAGIC) \ - -a 0xbf07 -e 0xbf07 \ - -n 'MIPS $(VERSION_DIST) Linux-$(LINUX_VERSION)' \ - -d $@.squashfs $@ - rm -rf $@.squashfs $@.fs -endef - -define Build/netgear-uImage - $(call Build/uImage,$(1) -M $(NETGEAR_KERNEL_MAGIC)) -endef - +include ./common-netgear.mk define Device/avm_fritz300e ATH_SOC := ar7242 -- 2.1.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 3/4] ath79: add Netgear WNR612 v2
Netgear WNR612 v2:
- cpu Atheros AR7240 (Python) @400MHz
- flash 4MB
- ram 32MB
- ethernet 10/100: 1xwan + 2xlan (only two)
- radio AR9285
As there is a rebranded WNR612v2 called ON Networks N150R, add
a dtsi which includes all device support, and add a separate dts
for the board only (allowing for a separate one for the subsequent
N150R).
Signed-off-by: Zoltan HERPAI
---
target/linux/ath79/base-files/etc/board.d/01_leds | 6 +
.../linux/ath79/base-files/etc/board.d/02_network | 5 +
.../etc/hotplug.d/firmware/10-ath9k-eeprom | 1 +
.../linux/ath79/dts/ar7240_netgear_wnr612-v2.dts | 10 ++
.../linux/ath79/dts/ar7240_netgear_wnr612-v2.dtsi | 147 +
target/linux/ath79/image/Makefile | 1 +
target/linux/ath79/image/tiny-netgear.mk | 19 +++
7 files changed, 189 insertions(+)
create mode 100644 target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dts
create mode 100644 target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dtsi
create mode 100644 target/linux/ath79/image/tiny-netgear.mk
diff --git a/target/linux/ath79/base-files/etc/board.d/01_leds
b/target/linux/ath79/base-files/etc/board.d/01_leds
index 0ba03b2..ee6568e 100755
--- a/target/linux/ath79/base-files/etc/board.d/01_leds
+++ b/target/linux/ath79/base-files/etc/board.d/01_leds
@@ -27,6 +27,12 @@ case "$board" in
"glinet,ar150")
ucidef_set_led_wlan "wlan" "WLAN" "gl-ar150:orange:wlan" "phy0tpt"
;;
+"netgear,wnr612-v2")
+ ucidef_set_led_netdev "wan" "WAN" "netgear:green:wan" "eth0"
+ ucidef_set_led_wlan "wlan" "WLAN" "netgear:green:wlan" "phy0tpt"
+ ucidef_set_led_switch "lan1" "LAN1" "netgear:green:lan1" "switch0"
"0x02" "0x0f"
+ ucidef_set_led_switch "lan2" "LAN2" "netgear:green:lan2" "switch0"
"0x04" "0x0f"
+ ;;
"tplink,tl-mr3020-v1")
ucidef_set_led_switch "lan" "LAN" "tp-link:green:lan" "switch0" "0x02"
;;
diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
b/target/linux/ath79/base-files/etc/board.d/02_network
index 8e3c917..f1f4bd0 100755
--- a/target/linux/ath79/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/base-files/etc/board.d/02_network
@@ -26,6 +26,11 @@ ath79_setup_interfaces()
"glinet,ar150")
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
+ "netgear,wnr612-v2")
+ ucidef_set_interfaces_lan_wan "eth1.1" "eth0"
+ ucidef_add_switch "switch0" \
+ "0@eth1" "1:lan" "2:lan" "3:lan:3" "4:lan:4"
+ ;;
"tplink,tl-mr3020-v1")
ucidef_set_interface_lan "eth0.1"
ucidef_add_switch "switch0" "0@eth0" "1:lan"
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
b/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
index 498cc4e..1ed7460 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
+++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
@@ -54,6 +54,7 @@ case "$FIRMWARE" in
"tplink,tl-wdr4300")
ath9k_eeprom_extract "art" 20480 1088
;;
+ "netgear,wnr612-v2"|\
"tplink,tl-wr740n-v2"|\
"ubnt,unifi")
ath9k_eeprom_extract "art" 4096 2048
diff --git a/target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dts
b/target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dts
new file mode 100644
index 000..d804064
--- /dev/null
+++ b/target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dts
@@ -0,0 +1,10 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include "ar7240_netgear_wnr612-v2.dtsi"
+
+/ {
+ model = "Netgear WNR612 v2";
+ compatible = "netgear,wnr612-v2";
+};
+
diff --git a/target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dtsi
b/target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dtsi
new file mode 100644
index 000..b86147e
--- /dev/null
+++ b/target/linux/ath79/dts/ar7240_netgear_wnr612-v2.dtsi
@@ -0,0 +1,147 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include
+#include
+
+#include "ar7240.dtsi"
+
+/ {
+ compatible = "netgear,wnr612-v2", "qca,ar7240";
+ model = "Netgear WNR612 V2";
+
+ aliases {
+ led-status = _power;
+ };
+
+ memory@0 {
+ device_type = "memory";
+ reg = <0x0 0x200>;
+ };
+
+ gpio-keys-polled {
+ compatible = "gpio-keys-polled";
+ #address-cells = <1>;
+ #size-cells = <0>;
+ poll-interval = <20>;
+
+ reset {
+ label = "reset";
+ linux,code = ;
+ gpios = < 7 GPIO_ACTIVE_LOW>;
+ debounce-interval = <60>;
+ };
+ };
+
+ gpio-leds {
+ compatible = "gpio-leds";
+ led_power: power {
+ label =
[OpenWrt-Devel] [PATCH 4/4] ath79: add support for ON Networks N150R (rebranded WNR612v2)
Signed-off-by: Zoltan HERPAI
---
target/linux/ath79/base-files/etc/board.d/01_leds | 3 ++-
target/linux/ath79/base-files/etc/board.d/02_network| 3 ++-
.../base-files/etc/hotplug.d/firmware/10-ath9k-eeprom | 1 +
target/linux/ath79/dts/ar7240_on_n150r.dts | 10 ++
target/linux/ath79/image/tiny-netgear.mk| 17 +
5 files changed, 32 insertions(+), 2 deletions(-)
create mode 100644 target/linux/ath79/dts/ar7240_on_n150r.dts
diff --git a/target/linux/ath79/base-files/etc/board.d/01_leds
b/target/linux/ath79/base-files/etc/board.d/01_leds
index ee6568e..47c9cab 100755
--- a/target/linux/ath79/base-files/etc/board.d/01_leds
+++ b/target/linux/ath79/base-files/etc/board.d/01_leds
@@ -27,7 +27,8 @@ case "$board" in
"glinet,ar150")
ucidef_set_led_wlan "wlan" "WLAN" "gl-ar150:orange:wlan" "phy0tpt"
;;
-"netgear,wnr612-v2")
+"netgear,wnr612-v2"|\
+"on,n150r")
ucidef_set_led_netdev "wan" "WAN" "netgear:green:wan" "eth0"
ucidef_set_led_wlan "wlan" "WLAN" "netgear:green:wlan" "phy0tpt"
ucidef_set_led_switch "lan1" "LAN1" "netgear:green:lan1" "switch0"
"0x02" "0x0f"
diff --git a/target/linux/ath79/base-files/etc/board.d/02_network
b/target/linux/ath79/base-files/etc/board.d/02_network
index f1f4bd0..ba4e7d4 100755
--- a/target/linux/ath79/base-files/etc/board.d/02_network
+++ b/target/linux/ath79/base-files/etc/board.d/02_network
@@ -26,7 +26,8 @@ ath79_setup_interfaces()
"glinet,ar150")
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
- "netgear,wnr612-v2")
+ "netgear,wnr612-v2"|\
+ "on,n150r")
ucidef_set_interfaces_lan_wan "eth1.1" "eth0"
ucidef_add_switch "switch0" \
"0@eth1" "1:lan" "2:lan" "3:lan:3" "4:lan:4"
diff --git
a/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
b/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
index 1ed7460..5b22b15 100644
--- a/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
+++ b/target/linux/ath79/base-files/etc/hotplug.d/firmware/10-ath9k-eeprom
@@ -55,6 +55,7 @@ case "$FIRMWARE" in
ath9k_eeprom_extract "art" 20480 1088
;;
"netgear,wnr612-v2"|\
+ "on,n150r"|\
"tplink,tl-wr740n-v2"|\
"ubnt,unifi")
ath9k_eeprom_extract "art" 4096 2048
diff --git a/target/linux/ath79/dts/ar7240_on_n150r.dts
b/target/linux/ath79/dts/ar7240_on_n150r.dts
new file mode 100644
index 000..cb4cf92
--- /dev/null
+++ b/target/linux/ath79/dts/ar7240_on_n150r.dts
@@ -0,0 +1,10 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include "ar7240_netgear_wnr612-v2.dtsi"
+
+/ {
+ model = "ON Network N150R";
+ compatible = "on,n150r";
+};
+
diff --git a/target/linux/ath79/image/tiny-netgear.mk
b/target/linux/ath79/image/tiny-netgear.mk
index 81f83fd..48d14e9 100644
--- a/target/linux/ath79/image/tiny-netgear.mk
+++ b/target/linux/ath79/image/tiny-netgear.mk
@@ -17,3 +17,20 @@ define Device/netgear_wnr612-v2
SUPPORTED_DEVICES := netgear,wnr612-v2 wnr612-v2
endef
TARGET_DEVICES += netgear_wnr612-v2
+
+define Device/n150r
+ ATH_SOC := ar7240
+ DEVICE_TITLE := ON Network N150R
+ DEVICE_DTS := ar7240_on_n150r
+ NETGEAR_KERNEL_MAGIC := 0x32303631
+ KERNEL := kernel-bin | append-dtb | lzma -d20 | netgear-uImage lzma
+ KERNEL_INITRAMFS := kernel-bin | append-dtb | lzma -d20 | netgear-uImage lzma
+ NETGEAR_BOARD_ID := N150R
+ IMAGE_SIZE := 3904k
+ IMAGES := sysupgrade.bin factory.img
+ IMAGE/default := append-kernel | pad-to (BLOCKSIZE) | netgear-squashfs |
append-rootfs | pad-rootfs
+ IMAGE/sysupgrade.bin := $$(IMAGE/default) | append-metadata | check-size
(IMAGE_SIZE)
+ IMAGE/factory.img := $$(IMAGE/default) | netgear-dni | check-size
(IMAGE_SIZE)
+ SUPPORTED_DEVICES := on,n150r n150r
+endef
+TARGET_DEVICES += n150r
--
2.1.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/4] tools: build squashfs (v3) for ath79
Certain Netgear devices use BE squashfs for the kernel image. As squashfs4 only supports creating LE images, add squashfs (v3) into the tools to be built for ath79. Trying to use an LE squashfs (thus trying to use squashfs4 only for building the image) for the kernel image results in the bootloader barfing and stopping. Signed-off-by: Zoltan HERPAI --- tools/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/Makefile b/tools/Makefile index d2b5daf..c8ef02c 100644 --- a/tools/Makefile +++ b/tools/Makefile @@ -31,6 +31,7 @@ tools-$(CONFIG_TARGET_orion_generic) += wrt350nv2-builder upslug2 tools-$(CONFIG_TARGET_x86) += qemu tools-$(CONFIG_TARGET_mxs) += elftosb sdimage tools-$(CONFIG_TARGET_ar71xx) += lzma-old squashfs +tools-$(CONFIG_TARGET_ath79) += squashfs tools-$(CONFIG_USES_MINOR) += kernel2minor tools-y += lzma squashfs4 tools-$(BUILD_B43_TOOLS) += b43-tools -- 2.1.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] iproute2: update to 4.17.0
On 13/06/2018 09:00, Russell Senior wrote: Hans Dedecker writes: Hi, On Sun, Jun 10, 2018 at 11:54 PM Russell Senior wrote: Signed-off-by: Russell Senior --- I get the following compile issues if the rdma utility is enabled : I wonder if rdma is actually useful in openwrt. As far as I can tell it's related to infiniband interfaces, which would seem to be rare in openwrt-supported devices. Comments? OpenWrt supports x86_64 PC/server hardware too, there you just need to add a pcie card. I don't know how many people do use that, though, it still caters to a specific use-case. -Alberto ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] iproute2: update to 4.17.0
> Hans Dedecker writes: > Hi, On Sun, Jun 10, 2018 at 11:54 PM Russell Senior > wrote: >> >> >> Signed-off-by: Russell Senior --- > I get the following compile issues if the rdma utility is enabled : I wonder if rdma is actually useful in openwrt. As far as I can tell it's related to infiniband interfaces, which would seem to be rare in openwrt-supported devices. Comments? -- Russell Senior, President russ...@personaltelco.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/listinfo/openwrt-devel
