Re: [OpenWrt-Devel] [PATCH 2/3] bcm53xx: add specific device profiles
El 28/05/2015 a las 21:16, Rafał Miłecki escribió: On 28 May 2015 at 21:04, Álvaro Fernández Rojas nolt...@gmail.com wrote: Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com So will you extend your above explanation a bit? Sure, These profiles define the required packages for each specific device. There are devices which have WiFi chipsets which aren't compatible with any available driver, so they don't need b43/brcmsmac/wpad-mini at all. Another example would be if any specific device had no USB ports. In this case it would make no sense to build specific images for this device with usb support (this is just an example, every supported bcm53xx device has USB ports. However, any device without usb ports could be added in the future, that's why I included USB support packages in every specific profile). Furthermore, let's say we only need to generate an image for NETGEAR R8000. In this case there's no need to build every single image, but just the one we need, as it's done in other targets like ar71xx, brcm63xx, etc. And this is a needed step for achieving this goal. If you have any more questions please let me know. Regards, Álvaro. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] brcm47xx: drop global description in favour of subtarget ones
Defining a description in this makefile prevents the subtarget Target/Description sections to appear in menuconfig's help for the subtargets. However, this also removes the menuconfig's help text for the target itself, but I'm not skilled enough to avoid this. Signed-off-by: Michael Heimpold m...@heimpold.de --- target/linux/brcm47xx/Makefile |5 - 1 file changed, 5 deletions(-) diff --git a/target/linux/brcm47xx/Makefile b/target/linux/brcm47xx/Makefile index 22b8674..4ac644c 100644 --- a/target/linux/brcm47xx/Makefile +++ b/target/linux/brcm47xx/Makefile @@ -17,11 +17,6 @@ KERNEL_PATCHVER:=3.18 include $(INCLUDE_DIR)/target.mk - -define Target/Description - Build firmware images for Broadcom based BCM47xx/53xx routers with MIPS CPU, *not* ARM. -endef - DEFAULT_PACKAGES += swconfig wpad-mini nvram otrx \ kmod-leds-gpio kmod-gpio-button-hotplug \ kmod-ledtrig-default-on kmod-ledtrig-timer kmod-ledtrig-netdev -- 1.7.10.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] brcm47xx: drop global description in favour of subtarget ones
On 28 May 2015 at 23:35, Michael Heimpold m...@heimpold.de wrote: Defining a description in this makefile prevents the subtarget Target/Description sections to appear in menuconfig's help for the subtargets. However, this also removes the menuconfig's help text for the target itself, but I'm not skilled enough to avoid this. Guys, can we somehow improve (sub)targets handling? I'd expect 1) Target System use brcm47xx/Makefile 2) Subtarget use brcm47xx/*/target.mk ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
Hi, thanks for your feedback and sorry for my mistake. Now I tried openwrt-brcm47xx-legacy-asus-wl-500gp-v2-squashfs.trx from r45811 and it works. Great! I'm wondering whether we should improve the make menuconfig help text about subtarget selection a little bit. Just for users like me, not reading the wiki page _before_ running the compiler :-) Regards, mhei Am Donnerstag, 28. Mai 2015, 21:57:04 schrieb Rafał Miłecki: On 28 May 2015 at 21:44, Rafał Miłecki zaj...@gmail.com wrote: On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) So above file (asus-wl-520gp-v2) is indeed for Asus WL-500gP v2. It should be named 500, not 520, I fixed this mistake in r45811: https://dev.openwrt.org/changeset/45811/ So whatever file you have: openwrt-brcm47xx-legacy-asus-wl-500gp-v2-squashfs.trx openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx , please try it and let me know if it worked with original firmware. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/3] bcm53xx: add specific device profiles
Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com --- target/linux/bcm53xx/profiles/ASUS.mk| 43 ++ target/linux/bcm53xx/profiles/Buffalo.mk | 45 target/linux/bcm53xx/profiles/NETGEAR.mk | 36 + target/linux/bcm53xx/profiles/SmartRG.mk | 16 4 files changed, 140 insertions(+) create mode 100644 target/linux/bcm53xx/profiles/ASUS.mk create mode 100644 target/linux/bcm53xx/profiles/Buffalo.mk create mode 100644 target/linux/bcm53xx/profiles/NETGEAR.mk create mode 100644 target/linux/bcm53xx/profiles/SmartRG.mk diff --git a/target/linux/bcm53xx/profiles/ASUS.mk b/target/linux/bcm53xx/profiles/ASUS.mk new file mode 100644 index 000..51aa412 --- /dev/null +++ b/target/linux/bcm53xx/profiles/ASUS.mk @@ -0,0 +1,43 @@ +# +# Copyright (C) 2015 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/asus-rt-ac56u + NAME:=ASUS RT-AC56U + PACKAGES:=kmod-b43 wpad-mini \ + kmod-usb-ohci kmod-usb2 +endef +define Profile/asus-rt-ac56u/Description + Package set optimized for ASUS RT-AC56U. +endef +$(eval $(call Profile,asus-rt-ac56u)) + +define Profile/asus-rt-ac68u + NAME:=ASUS RT-AC68U + PACKAGES:=kmod-usb-ohci kmod-usb2 +endef +define Profile/asus-rt-ac68u/Description + Package set optimized for ASUS RT-AC68U. +endef +$(eval $(call Profile,asus-rt-ac68u)) + +define Profile/asus-rt-ac87u + NAME:=ASUS RT-AC87U + PACKAGES:=kmod-usb-ohci kmod-usb2 +endef +define Profile/asus-rt-ac87u/Description + Package set optimized for ASUS RT-AC87U. +endef +$(eval $(call Profile,asus-rt-ac87u)) + +define Profile/asus-rt-n18u + NAME:=ASUS RT-N18U + PACKAGES:=kmod-usb-ohci kmod-usb2 +endef +define Profile/asus-rt-n18u/Description + Package set optimized for ASUS RT-N18U. +endef +$(eval $(call Profile,asus-rt-n18u)) diff --git a/target/linux/bcm53xx/profiles/Buffalo.mk b/target/linux/bcm53xx/profiles/Buffalo.mk new file mode 100644 index 000..704eefd --- /dev/null +++ b/target/linux/bcm53xx/profiles/Buffalo.mk @@ -0,0 +1,45 @@ +# +# Copyright (C) 2015 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/buffalo-wzr-600dhp2 + NAME:=Buffalo WZR-600DHP2 + PACKAGES:=kmod-b43 wpad-mini \ + kmod-usb-ohci kmod-usb2 +endef +define Profile/buffalo-wzr-600dhp2/Description + Package set optimized for Buffalo WZR-600DHP2. +endef +$(eval $(call Profile,buffalo-wzr-600dhp2)) + +define Profile/buffalo-wzr-900dhp + NAME:=Buffalo WZR-900DHP + PACKAGES:=kmod-b43 wpad-mini \ + kmod-usb-ohci kmod-usb2 +endef +define Profile/buffalo-wzr-900dhp/Description + Package set optimized for Buffalo WZR-900DHP. +endef +$(eval $(call Profile,buffalo-wzr-900dhp)) + +define Profile/buffalo-wzr-1750dhp + NAME:=Buffalo WZR-1750DHP + PACKAGES:=kmod-b43 wpad-mini \ + kmod-usb-ohci kmod-usb2 +endef +define Profile/buffalo-wzr-1750dhp/Description + Package set optimized for Buffalo WZR-1750DHP. +endef +$(eval $(call Profile,buffalo-wzr-1750dhp)) + +define Profile/buffalo-wxr-1900dhp + NAME:=Buffalo WXR-1900DHP + PACKAGES:=kmod-usb-ohci kmod-usb2 +endef +define Profile/buffalo-wxr-1900dhp/Description + Package set optimized for Buffalo WXR-1900DHP. +endef +$(eval $(call Profile,buffalo-wxr-1900dhp)) diff --git a/target/linux/bcm53xx/profiles/NETGEAR.mk b/target/linux/bcm53xx/profiles/NETGEAR.mk new file mode 100644 index 000..c5a33c0 --- /dev/null +++ b/target/linux/bcm53xx/profiles/NETGEAR.mk @@ -0,0 +1,36 @@ +# +# Copyright (C) 2015 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +define Profile/netgear-r6250 + NAME:=NETGEAR R6250 + PACKAGES:=kmod-b43 wpad-mini \ + kmod-usb-ohci kmod-usb2 +endef +define Profile/netgear-r6250/Description + Package set optimized for NETGEAR R6250. +endef +$(eval $(call Profile,netgear-r6250)) + +define Profile/netgear-r6300-v2 + NAME:=NETGEAR R6300 v2 + PACKAGES:=kmod-b43 wpad-mini \ + kmod-usb-ohci kmod-usb2 +endef +define Profile/netgear-r6300-v2/Description + Package set optimized for NETGEAR R6300 v2. +endef +$(eval $(call Profile,netgear-r6300-v2)) + +define Profile/netgear-r8000 + NAME:=NETGEAR R8000 + PACKAGES:=kmod-brcmfmac wpad-mini \ + kmod-usb-ohci kmod-usb2 +endef +define Profile/netgear-r8000/Description + Package set optimized for NETGEAR R8000. +endef +$(eval $(call Profile,netgear-r8000)) diff --git a/target/linux/bcm53xx/profiles/SmartRG.mk b/target/linux/bcm53xx/profiles/SmartRG.mk new file mode 100644 index 000..2de26b2 --- /dev/null +++ b/target/linux/bcm53xx/profiles/SmartRG.mk @@ -0,0 +1,16 @@ +# +# Copyright (C) 2015 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information.
Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc1 / git-checkout
On May 28, 2015 12:14 PM, John Crispin blo...@openwrt.org wrote: On 28/05/2015 19:11, Jonathan Bennett wrote: On Wed, May 20, 2015 at 2:32 PM, Bastian Bittorf bitt...@bluebottle.com wrote: * Steven Barth cy...@openwrt.org [20.05.2015 19:43]: http://downloads.openwrt.org/chaos_calmer/15.05-rc1/ Thank you! when will this work?: git clone git://git.openwrt.org/15.05/openwrt.git Is there any update on when the 15.05 branch will be available via git? we will stay in trunk until at least rc2. depending on how that goes maybe even rc3. John Ah, so we haven't branched at all yet. Is there anything specific that needs work or testing before that happens? ~Jonathan bennett ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc1 / git-checkout
On 28/05/2015 19:11, Jonathan Bennett wrote: On Wed, May 20, 2015 at 2:32 PM, Bastian Bittorf bitt...@bluebottle.com wrote: * Steven Barth cy...@openwrt.org [20.05.2015 19:43]: http://downloads.openwrt.org/chaos_calmer/15.05-rc1/ Thank you! when will this work?: git clone git://git.openwrt.org/15.05/openwrt.git Is there any update on when the 15.05 branch will be available via git? we will stay in trunk until at least rc2. depending on how that goes maybe even rc3. John ~Jonathan bennett ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Chaos Calmer 15.05-rc1 / git-checkout
On Wed, May 20, 2015 at 2:32 PM, Bastian Bittorf bitt...@bluebottle.com wrote: * Steven Barth cy...@openwrt.org [20.05.2015 19:43]: http://downloads.openwrt.org/chaos_calmer/15.05-rc1/ Thank you! when will this work?: git clone git://git.openwrt.org/15.05/openwrt.git Is there any update on when the 15.05 branch will be available via git? ~Jonathan bennett ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 3/3] bcm53xx: allow building specific device images
Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com --- target/linux/bcm53xx/image/Makefile | 115 ++-- 1 file changed, 70 insertions(+), 45 deletions(-) diff --git a/target/linux/bcm53xx/image/Makefile b/target/linux/bcm53xx/image/Makefile index b22dfe5..4f188f8 100644 --- a/target/linux/bcm53xx/image/Makefile +++ b/target/linux/bcm53xx/image/Makefile @@ -1,5 +1,5 @@ # -# Copyright (C) 2013 OpenWrt.org +# Copyright (C) 2013-2015 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. @@ -56,78 +56,103 @@ endef define Build/asus-trx $(STAGING_DIR_HOST)/bin/asustrx \ - -p $(PRODUCTID) -i $@ -o $@.new + -p $(ASUS_ID) -i $@ -o $@.new mv $@.new $@ endef define Build/netgear-chk $(STAGING_DIR_HOST)/bin/mkchkimg \ - -o $@.new -k $@ -b $(BOARD_ID) -r $(REGION) + -o $@.new -k $@ -b $(NETGEAR_ID) -r $(NETGEAR_REGION) mv $@.new $@ endef -DEVICE_VARS += DT PRODUCTID BOARD_ID REGION - define Device/Default # .dtb files are prefixed by SoC type, e.g. bcm4708- which is not included in device/image names # extract the full dtb name based on the device info DT := $(patsubst %.dtb,%,$(notdir $(wildcard $(if $(IB),$(KDIR),$(DTS_DIR))/*-$(1).dtb))) + PROFILES = Generic $$(DEVICE_PROFILE) KERNEL := kernel-bin | append-dtb | lzma-d16 FILESYSTEMS := squashfs KERNEL_NAME := zImage IMAGE_NAME = $$(IMAGE_PREFIX)-$$(1).$$(2) + DEVICE_PROFILE := +endef +DEVICE_VARS += DT DEVICE_PROFILE + +define Device/trx_nand IMAGES := trx IMAGE/trx := trx-nand endef -define Device/asus +define Device/trx_serial IMAGES := trx - IMAGE/trx := trx-nand | asus-trx + IMAGE/trx := trx-serial endef -define AsusDevice - define Device/asus-$(1) - $$(Device/asus) - PRODUCTID := $(2) - endef - TARGET_DEVICES += asus-$(1) +define Device/asus + IMAGES := trx + IMAGE/trx := $$(IMAGE/trx) | asus-trx + ASUS_ID := endef +DEVICE_VARS += ASUS_ID define Device/netgear IMAGES := chk - IMAGE/chk := trx-nand | netgear-chk - REGION := 1 -endef - -define Device/netgear-r6250 - $(Device/netgear) - BOARD_ID := U12H245T00_NETGEAR -endef - -define Device/netgear-r6300-v2 - $(Device/netgear) - BOARD_ID := U12H240T00_NETGEAR -endef - -define Device/netgear-r8000 - $(Device/netgear) - BOARD_ID := U12H315T00_NETGEAR -endef - -define Device/smartrg-sr400ac - IMAGES := trx - IMAGE/trx := trx-serial + IMAGE/chk := $$(IMAGE/trx) | netgear-chk + NETGEAR_ID := + NETGEAR_REGION := +endef +DEVICE_VARS += NETGEAR_ID NETGEAR_REGION + +# $(1) = trx image +# $(2) = device name +define GenericDevice + define Device/$(2) +$$(Device/$(1)) +DEVICE_PROFILE := $(2) + endef + TARGET_DEVICES += $(2) endef -TARGET_DEVICES += \ - buffalo-wzr-1750dhp buffalo-wzr-600dhp2 buffalo-wzr-900dhp \ - buffalo-wxr-1900dhp \ - netgear-r6250 netgear-r6300-v2 netgear-r8000 \ - smartrg-sr400ac - -$(eval $(call AsusDevice,rt-ac56u,RT-AC56U)) -$(eval $(call AsusDevice,rt-ac68u,RT-AC68U)) -$(eval $(call AsusDevice,rt-ac87u,RT-AC87U)) -$(eval $(call AsusDevice,rt-n18u,RT-N18U)) +# $(1) = trx image +# $(2) = device name +# $(3) = asus id +define AsusDevice + define Device/asus-$(2) +$$(Device/$(1)) + $$(Device/asus) +DEVICE_PROFILE := asus-$(2) +ASUS_ID := $(3) + endef + TARGET_DEVICES += asus-$(2) +endef + +# $(1) = trx image +# $(2) = device name +# $(3) = netgear id +# $(4) = netgear region +define NetgearDevice + define Device/netgear-$(2) +$$(Device/$(1)) + $$(Device/netgear) +DEVICE_PROFILE := netgear-$(2) +NETGEAR_ID := $(3) +NETGEAR_REGION := $(4) + endef + TARGET_DEVICES += netgear-$(2) +endef + +$(eval $(call AsusDevice,trx_nand,rt-ac56u,RT-AC56U)) +$(eval $(call AsusDevice,trx_nand,rt-ac68u,RT-AC68U)) +$(eval $(call AsusDevice,trx_nand,rt-ac87u,RT-AC87U)) +$(eval $(call AsusDevice,trx_nand,rt-n18u,RT-N18U)) +$(eval $(call GenericDevice,trx_nand,buffalo-wxr-1900dhp)) +$(eval $(call GenericDevice,trx_nand,buffalo-wzr-1750dhp)) +$(eval $(call GenericDevice,trx_nand,buffalo-wzr-600dhp2)) +$(eval $(call GenericDevice,trx_nand,buffalo-wzr-900dhp)) +$(eval $(call GenericDevice,trx_serial,smartrg-sr400ac)) +$(eval $(call NetgearDevice,trx_nand,r6250,U12H245T00_NETGEAR,1)) +$(eval $(call NetgearDevice,trx_nand,r6300-v2,U12H240T00_NETGEAR,1)) +$(eval $(call NetgearDevice,trx_nand,r8000,U12H315T00_NETGEAR,1)) $(eval $(call BuildImage)) -- 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] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 21:44, Rafał Miłecki zaj...@gmail.com wrote: On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) So above file (asus-wl-520gp-v2) is indeed for Asus WL-500gP v2. It should be named 500, not 520, I fixed this mistake in r45811: https://dev.openwrt.org/changeset/45811/ So whatever file you have: openwrt-brcm47xx-legacy-asus-wl-500gp-v2-squashfs.trx openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx , please try it and let me know if it worked with original firmware. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/3] bcm53xx: move wpad-mini from Makefile to Generic profile
Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com --- target/linux/bcm53xx/Makefile| 2 +- target/linux/bcm53xx/profiles/100-Generic.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/target/linux/bcm53xx/Makefile b/target/linux/bcm53xx/Makefile index 8b7f71b..89c099f 100644 --- a/target/linux/bcm53xx/Makefile +++ b/target/linux/bcm53xx/Makefile @@ -23,7 +23,7 @@ endef KERNELNAME:=zImage dtbs -DEFAULT_PACKAGES += swconfig wpad-mini nvram otrx \ +DEFAULT_PACKAGES += swconfig nvram otrx \ kmod-gpio-button-hotplug \ kmod-leds-gpio kmod-ledtrig-default-on kmod-ledtrig-timer diff --git a/target/linux/bcm53xx/profiles/100-Generic.mk b/target/linux/bcm53xx/profiles/100-Generic.mk index d7e9005..3b998fb 100644 --- a/target/linux/bcm53xx/profiles/100-Generic.mk +++ b/target/linux/bcm53xx/profiles/100-Generic.mk @@ -7,7 +7,7 @@ define Profile/Generic NAME:=Broadcom SoC, BCM43xx WiFi (b43, brcmfmac, default) - PACKAGES:=kmod-b43 kmod-brcmfmac + PACKAGES:=kmod-b43 kmod-brcmfmac wpad-mini endef define Profile/Generic/Description -- 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] Looking for a Broadcom Asus tester(s)
Hi Rafał, I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( The OpenWrt version I tested was: git-svn-id: svn://svn.openwrt.org/openwrt/trunk@45810 3c298f89-4303-0410-b956-a3cf2f4a3e73 HTH + thanks for your hard work, regards, Michael Am Mittwoch, 27. Mai 2015, 22:32:57 schrieb Rafał Miłecki: Hi, With few recent commits OpenWrt can now generate Asus-specific TRX files for brcm47xx and bcm53xx. The magic is about some extra data at the end of TRX (so the format differs a bit, even it using the same file extension and layout). My request for someone having Broadcom-based Asus devices is: 1) Install original firmware 2) Try to install OpenWrt .trx firmware for that device 3) Let us know if it worked I don't have any Asus device around, so I'm not sure if OpenWrt generates really compatible images now. Above way is the only one to verify it for sure :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/3] bcm53xx: add specific device profiles
On 28 May 2015 at 21:04, Álvaro Fernández Rojas nolt...@gmail.com wrote: Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com So will you extend your above explanation a bit? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 21:44, Rafał Miłecki zaj...@gmail.com wrote: On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) Ahh, wait, I just noticed you use 500gP V2, not 520... let me take a look again. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Looking for a Broadcom Asus tester(s)
On 28 May 2015 at 21:31, Michael Heimpold m...@heimpold.de wrote: I have a Asus WL-500gP V2 router and restored original Asus Firmware version 3.0.4.4. Then I tried openwrt-brcm47xx-generic-squashfs.trx, openwrt-brcm47xx-generic-squashfs-gz.trx openwrt-brcm47xx-generic-squashfs-noloader-nodictionary.trx, but without look. The original firmware always rejected the image :-( You were supposed to test device-specific firmware, in your case it means openwrt-brcm47xx-legacy-asus-wl-520gp-v2-squashfs.trx (yes, there isn't any reason for you to use generic instead of legacy) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] procd: how to reload inittab?
Hi, I would like asi, if is any progress with this issue? Regards M. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Link detection - TP-Link Archer C7 v2
Am 27.05.2015 um 20:57 schrieb Gert Doering: (Which is how certain commercial platforms handle this - if all L2 ports in a given VLAN go down, the L3 routing interface will also go down, and I found that usually to be what I expect and want to happen) This would totally match my usecase. I like this solution. Best Christian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] tinc protocol handler
Hi,
I am working to create a protocol handler for tinc (chaos calmer).
I do not understand the following lines ?
proto_init_update * 1
proto_send_update $iface
Can someone take a look at the code below and give me some advice :-) or
point me to documentation.
Perry
#!/bin/sh
. /lib/functions.sh
. ../netifd-proto.sh
init_proto $@
proto_tinc_init_config() {
no_device=1
available=1
proto_config_add_string ipaddr
proto_config_add_string netmask
proto_config_add_string ifname
}
proto_tinc_setup() {
local config=$1
local iface=$2
# Code to start tinc interface.
/usr/sbin/tincd --net=$iface --pidfile=/var/run/tinc.$iface.pid
logger -p daemon.info -t Tinc interface started
proto_init_update * 1
proto_send_update $iface
return 0
}
proto_tinc_teardown() {
local iface=$1
# Code to stop tinc interface.
if [ -f /var/run/tinc.$iface.pid ]
then
pid=`cat /var/run/tinc.$iface.pid`
kill $pid
fi
proto_init_update * 0
proto_send_update $iface
return 0
}
add_protocol tinc
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ar71xx: How to integrate UniFi AP Outdoor Plus HSR?
Hi, Stefan On 05/27/2015 11:48 PM, Stefan Rompf wrote: Integration into the kernel driver like your latest patch does. Caveat: The build process seems to assume that all routers in the ar71xx/generic target share the same set of kernel modules. So patching and compiling yourself is no problem, but a working image on downloads.openwrt.org is not feasible as every router would get the HSR driver. Correct me if I am wrong. This is not a problem because it is possible to use full platform name, which includes a profile name, as a dependency. The ubiquity driver checks some flags before enabling hsr, but I can't still track down where they store them. May be somewhere in eeprom. Or making ath9k expose the gpio and driving from user space. A generic patch for ath9k to register its gpio pins via the standard gpio subsystem. This should go upstream to the kernel and may prove usable for other access points to. An Unifi specific user space daemon listens to scan and channel change events via netlink (will check next weekend if channel change is broadcasted reliably) and tune the filter via sysfs interface accordingly like hsr.c tried. I like this idea because in this case it'll be much easier to correct problems or add changes. However for more general use a patch to the driver is much better. PS: I've started working on the wiki page http://wiki.openwrt.org/toh/ubiquiti/unifi_outdoorplus that I hope to move to supported soon ;-) I have a couple photos of pcb (one with annotated serial port), can send them if you need. Kirill. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
