Re: [OpenWrt-Devel] protobuf broken in BB
Hello again, Please comment on the attached patch commit if you are OK. Thanks Le 26/11/2014 08:10, John Crispin a écrit : Hi, so which patch do i use now ? John On 19/11/2014 13:24, Guillaume Déflache wrote: Hi all Sorry obconseil and John for the delay, my work priorities got shifted to other things... @John: good idea to ping me personally! ;) Am 06.11.2014 10:23, schrieb obconseil: Le 05/11/2014 22:43, Guillaume Déflache a écrit : Fine, but that's not the problem as I said before (see the very 1st quoted text in this message): *installing protoc at the right location* (that is .../build_dir/host/bin/protoc IIRC) is the problem. I checked that with our pre-BB snapshot it was installed where expected and that with the BB release it is not. You can try executing `make install` from the host build directory to convince yourself that that does what is required from the OpenWrt Makefile but currently missing in BB's. That's what I did and then the problem was gone. So you have to try using protoc to generate some source code files in order to really stumble on the problem. Apart from that everything works fine indeed. Oh. I admit I overlooked this in your previous message. Thanks. What about the attached patch ? I had no time to test it unfortunately but I made one myself (see below) in parallel to get something working for us internally. By the way, maybe somebody else could enlighten me on this but in BB, it seems that the host tools directory is .../staging_dir/host/bin rather than .../build_dir/host/bin . I have no .../build_dir/host/bin directory on my build tree. You are right, .../staging_dir/host/bin is correct: AFAICU only staging_dir/ sports global filesystem hierarchies for all packages with bin/, include/, lib/, ... (one for the host, two per compiled target for the toolchain and the device itself). The patch do install protoc in .../staging_dir/host/bin , along with all other programs like bison,... I think this is the correct thing to do, and that's also what I do in my patch. Since the snapshot we used previously PKG_USE_MIPS16:=0 also got added, does that mean we should also use that on all packages that compile Protocol Buffer generated code and/or link with the PB library? After a second though I think this line was to avoid an assembler error on some plateform. I still need to test the current compiler/assembler on a MIPS16 platform, but for now you can safely leave this line out for your platform. [...] I would have no objections to 2.6.1 if it also works for us too (I can test that at the same time). Yes, please test report : I would much better push upstream a patch with the newest version of protobuf. For us 2.6.0 and 2.5.0 definitely do not work (I think I also tested with 2.6.1, not sure anymore). When I made the patch I stumbled upon https://www.mail-archive.com/protobuf@googlegroups.com/msg10536.html (Re: [protobuf] Re: Issue 670 in protobuf: Not Able to compile protobuf for mips platform) which looks exactly like the problem I had. Alas I did not notify either of OpenWrt or protobuf of the others' problem then. I guess there was some kind of regression from 2.4.1, probably someone should point the upstream protobuf developers to this thread. What works for us is the patch below: - as I said only 2.4.1 worked - removing the src/google/protobuf/stubs/platform_macros.h patch chunk also did help *IIRC* - PKG_USE_MIPS16:=0 or 1 made no difference *IIRC* ##\brief protobuf 2.4.1 without MIPS16 ## ## For the full rationale see https://lists.openwrt.org/pipermail/openwrt-devel/2014-November/029107.html. ## ## This is a Git patch against GitHub OpenWrt's 'packages' feed v14.07. # diff --git a/libs/protobuf/Makefile b/libs/protobuf/Makefile index 1553a7e..1411a82 100644 --- a/libs/protobuf/Makefile +++ b/libs/protobuf/Makefile @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=protobuf -PKG_VERSION:=2.5.0 +PKG_VERSION:=2.4.1 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 PKG_SOURCE_URL:=http://protobuf.googlecode.com/files -PKG_MD5SUM:=a72001a9067a4c2c4e0e836d0f92ece4 +PKG_MD5SUM:=ed436802019c9e1f40cc750eaf78f318 PKG_BUILD_DEPENDS:=protobuf/host PKG_USE_MIPS16:=0 @@ -38,14 +38,7 @@ define Package/protobuf/description of its internal RPC protocols and file formats. endef -define Host/Compile - $(MAKE) -C $(HOST_BUILD_DIR) -endef - -define Host/Install -endef - -CONFIGURE_ARGS += --with-protoc=$(HOST_BUILD_DIR)/src/protoc +CONFIGURE_ARGS += --with-protoc=$(STAGING_DIR_HOST)/bin/protoc define Build/InstallDev $(INSTALL_DIR) \ diff --git a/libs/protobuf/patches/001-mipseb-compile.patch b/libs/protobuf/patches/001-mipseb-compile.patch deleted file mode 100644 index 6eb0590..000 --- a/libs/protobuf/patches/001-mipseb-compile.patch +++ /dev/null @@ -1,11 +0,0 @@ a/src/google/protobuf/stubs/platform_macros.h -+++ b/src/google/protobuf/stubs/platform_macros.h -@@ -49,7 +49,7 @@ - #elif
Re: [OpenWrt-Devel] [PATCH 3/5] add new target 'oxnas'
Hi John, On Wed, Nov 26, 2014 at 08:14:18AM +0100, John Crispin wrote: seems to all be functional. one last question ... I found yet another small thing to fix ehci which I recently broke. It also seems like xhci support doesn't work on 3.18 yet. Most boards, (except for kd20) don't come with USB 3, so this is something I can fix later on and once xhci is confirmed to work on other platforms on 3.18. you use oxnas everywhere apart from the string that the user sees in menuconfig. i had to look twice to find the right target option in menuconfig as i was looking for Oxna dna not plxtech Hm, right, that might be confusing. The mach name 'oxnas' wasn't changed despite the frequent changes in marketing names of the SoC, similar to sunxi or xburst which are also marketed with different names today... I guess the best would be to change the board name 'PLXTECH NAS782X' to 'Oxford OX82x / PLXTECH NAS782x' (or the other way around, so to have the currently still used marketing name followed by historic names) I'll post a patch doing that and fixing EHCI in sec. Cheers Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] (no subject)
The following changes since commit 576d8531a744377b1c9e322d8d1533474064b880: [ar71xx]: fix the r6100's wan led name (2014-11-26 11:38:59 +) are available in the git repository at: https://gitorious.org/openwrt-oxnas/openwrt-oxnas.git for you to fetch changes up to cd4f739b2d35744b6b9dacfa1e4edcaf6e2337d5: oxnas: change visible board name (2014-11-26 14:04:50 +0100) Daniel Golle (2): oxnas: ehci: rename vendor prefix plxtch to plxtech oxnas: change visible board name target/linux/oxnas/Makefile| 2 +- target/linux/oxnas/files/arch/arm/boot/dts/ox820.dtsi | 2 +- target/linux/oxnas/files/drivers/usb/host/ehci-oxnas.c | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] mac80211: disable wlcore for Kernel 3.15
upstream wlcore in mac80211 requires Kernel = 3.15 since series: backports: synch up to next-20140311 exact commit text: bump kernel reqs for WL1251_SDIO and WLCORE_SDIO this should fix a compile error complaining about missing wlcore_sdio.ko that gets not generated because its Kconfig depends on Linux Kernel = 3.15 this should fix https://dev.openwrt.org/ticket/18410 Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de --- package/kernel/mac80211/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index ab46a18..4f74e00 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1001,7 +1001,7 @@ endef define KernelPackage/wlcore $(call KernelPackage/mac80211/Default) TITLE:=TI common driver part - DEPENDS+= @TARGET_omap +kmod-mac80211 +@DRIVER_11N_SUPPORT + DEPENDS+= @(!LINUX_3_10!LINUX_3_13!LINUX_3_14) @TARGET_omap +kmod-mac80211 +@DRIVER_11N_SUPPORT FILES:= \ $(PKG_BUILD_DIR)/drivers/net/wireless/ti/wlcore/wlcore.ko \ $(PKG_BUILD_DIR)/drivers/net/wireless/ti/wlcore/wlcore_sdio.ko -- 2.1.3 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] (no subject)
Patch to add the buildprofile for the GL-Init-6408A-v1 and the GL-Inet-6416A-v1 Both devices are identical, only difference is one comes with 8MB flash and the other with 16MB flash Official website: http://www.gl-inet.com/w/?page_id=241lang=en Comprehensive list of specs: https://revspace.nl/GL-Inet Official ebay store: http://www.ebay.com/sch/alfie.zhao/m.html?_nkw=_armrs=1_ipg=_from= Official amazon store: http://www.amazon.com/gp/aag/main?ie=UTF8seller=A364119SDJA4QG ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: Add build profile for the gl-inet 6416A and 6408A
Signed-off-by: Martijn Zilverschoon mart...@friedzombie.com --- target/linux/ar71xx/image/Makefile |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/target/linux/ar71xx/image/Makefile b/target/linux/ar71xx/image/Makefile index 1c78898..791c4b7 100644 --- a/target/linux/ar71xx/image/Makefile +++ b/target/linux/ar71xx/image/Makefile @@ -1253,7 +1253,8 @@ $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V1,archer-c7-v1,ARCHER-C7 $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V2,archer-c7-v2,ARCHER-C7,ttyS0,115200,0xc702,1,16Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ELM150,el-m150,EL-M150,ttyATH0,115200,0x01500101,1,8Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ELMINI,el-mini,EL-MINI,ttyATH0,115200,0x01530001,1,8Mlzma)) -$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,GLINET,gl-inet-v1,GL-INET,ttyATH0,115200,0x0801,1,8Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,GLINET6408A,gl-inet-6408A-v1,GL-INET,ttyATH0,115200,0x0801,1,8Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,GLINET6416A,gl-inet-6416A-v1,GL-INET,ttyATH0,115200,0x0801,1,16Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR10U,tl-mr10u-v1,TL-MR10U,ttyATH0,115200,0x00100101,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV1,tl-mr11u-v1,TL-MR11U,ttyATH0,115200,0x00110101,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV2,tl-mr11u-v2,TL-MR11U,ttyATH0,115200,0x00110102,1,4Mlzma)) @@ -1340,6 +1341,7 @@ $(eval $(call MultiProfile,AP136,AP136_010 AP136_020)) $(eval $(call MultiProfile,ARCHERC7, ARCHERC5 ARCHERC7V1 ARCHERC7V2)) $(eval $(call MultiProfile,EWDORIN, EWDORINAP EWDORINRT EWDORIN16M)) $(eval $(call MultiProfile,OPENMESH,OM2P OM5P MR600 MR900)) +$(eval $(call MultiProfile,GLINET,GLINET6408A GLINET6416A)) $(eval $(call MultiProfile,TEW652BRP,TEW652BRP_FW TEW652BRP_RECOVERY)) $(eval $(call MultiProfile,TLMR11U,TLMR11UV1 TLMR11UV2)) $(eval $(call MultiProfile,TLMR3040,TLMR3040V1 TLMR3040V2)) -- 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] ar71xx: Add build profile for the gl-inet 6416A and 6408A
Sorry for the messup with the message without a subject, they should have send as one. So here by the text from the seperate message: Patch to add the buildprofile for the GL-Init-6408A-v1 and the GL-Inet-6416A-v1 Both devices are identical, only difference is one comes with 8MB flash and the other with 16MB flash Official website: http://www.gl-inet.com/w/?page_id=241lang=en Comprehensive list of specs: https://revspace.nl/GL-Inet Official ebay store: http://www.ebay.com/sch/alfie.zhao/m.html?_nkw=_armrs=1_ipg=_from= Official amazon store: http://www.amazon.com/gp/aag/main?ie=UTF8seller=A364119SDJA4QG Martijn Zilverschoon schreef op 26-11-2014 om 19:13: Signed-off-by: Martijn Zilverschoon mart...@friedzombie.com --- target/linux/ar71xx/image/Makefile |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/target/linux/ar71xx/image/Makefile b/target/linux/ar71xx/image/Makefile index 1c78898..791c4b7 100644 --- a/target/linux/ar71xx/image/Makefile +++ b/target/linux/ar71xx/image/Makefile @@ -1253,7 +1253,8 @@ $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V1,archer-c7-v1,ARCHER-C7 $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ARCHERC7V2,archer-c7-v2,ARCHER-C7,ttyS0,115200,0xc702,1,16Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ELM150,el-m150,EL-M150,ttyATH0,115200,0x01500101,1,8Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,ELMINI,el-mini,EL-MINI,ttyATH0,115200,0x01530001,1,8Mlzma)) -$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,GLINET,gl-inet-v1,GL-INET,ttyATH0,115200,0x0801,1,8Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,GLINET6408A,gl-inet-6408A-v1,GL-INET,ttyATH0,115200,0x0801,1,8Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,GLINET6416A,gl-inet-6416A-v1,GL-INET,ttyATH0,115200,0x0801,1,16Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR10U,tl-mr10u-v1,TL-MR10U,ttyATH0,115200,0x00100101,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV1,tl-mr11u-v1,TL-MR11U,ttyATH0,115200,0x00110101,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV2,tl-mr11u-v2,TL-MR11U,ttyATH0,115200,0x00110102,1,4Mlzma)) @@ -1340,6 +1341,7 @@ $(eval $(call MultiProfile,AP136,AP136_010 AP136_020)) $(eval $(call MultiProfile,ARCHERC7, ARCHERC5 ARCHERC7V1 ARCHERC7V2)) $(eval $(call MultiProfile,EWDORIN, EWDORINAP EWDORINRT EWDORIN16M)) $(eval $(call MultiProfile,OPENMESH,OM2P OM5P MR600 MR900)) +$(eval $(call MultiProfile,GLINET,GLINET6408A GLINET6416A)) $(eval $(call MultiProfile,TEW652BRP,TEW652BRP_FW TEW652BRP_RECOVERY)) $(eval $(call MultiProfile,TLMR11U,TLMR11UV1 TLMR11UV2)) $(eval $(call MultiProfile,TLMR3040,TLMR3040V1 TLMR3040V2)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [base-files] functions.sh: default_postinst() - create user:group first
1.) create user:group
2.) run postinst-pkg
now you can change owner and permission of installed files and directories
in postinst-pkg (Makefile/postinst)
otherwise you can't
3.) clear luci cache
4.) enable/start service
Signed-off-by: Christian Schoenebeck christian.schoeneb...@gmail.com
---
package/base-files/files/lib/functions.sh | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/package/base-files/files/lib/functions.sh
b/package/base-files/files/lib/functions.sh
index d53be3e..3d987cf 100755
--- a/package/base-files/files/lib/functions.sh
+++ b/package/base-files/files/lib/functions.sh
@@ -173,7 +173,7 @@ default_prerm() {
default_postinst() {
local name rusers
name=$(echo $(basename $1) | cut -d. -f1)
- [ -f ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ] ( .
${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg )
+
rusers=$(grep Require-User:
${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.control)
[ -n $rusers ] {
local user group uid gid
@@ -212,6 +212,10 @@ default_postinst() {
done
done
}
+
+ [ -f ${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg ] ( .
${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.postinst-pkg )
+ [ -n ${IPKG_INSTROOT} ] || rm -f /tmp/luci-indexcache 2/dev/null
+
[ $PKG_UPGRADE = 1 ] || for i in `cat
${IPKG_INSTROOT}/usr/lib/opkg/info/${name}.list | grep ^/etc/init.d/`; do
[ -n ${IPKG_INSTROOT} ] $(which bash)
${IPKG_INSTROOT}/etc/rc.common ${IPKG_INSTROOT}$i enable; \
[ -n ${IPKG_INSTROOT} ] || {
@@ -219,7 +223,6 @@ default_postinst() {
$i start
}
done
- [ -n ${IPKG_INSTROOT} ] || rm -f /tmp/luci-indexcache 2/dev/null
return 0
}
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
On Nov 19 18:43 +0100, Rafał Miłecki wrote: On 12 November 2014 21:59, Alex Henrie alexhenri...@gmail.com wrote: 2014-11-11 23:51 GMT-07:00 Rafał Miłecki zaj...@gmail.com: On 11 November 2014 23:26, Alex Henrie alexhenri...@gmail.com wrote: Is no one interested? Come on, I'm offering free hardware to play with ;-) I already have about 10-20 Broadcom based boars in my drawer ;) Not that excited with another one. However I'd be happy to help adding support for WNR1000 v3. Could you attach serial console to it and test some patched OpenWrt builds? It sounds like a fun project, but SGT. Garcia darwinsker...@gmail.com volunteered to work on it, and I have already mailed the device to him. I'm sure SGT. Garcia will contact you for help once he receives the device. Thanks for your work on OpenWrt! Hi Garcia, Could you provide us NVRAM dump once you get this device? You have access to nvram show command in both: CFE and original firmware I believe. -- Rafał hi Rafał, first question, do i absolutely need a serial console to get an interface with CFE? i tried telnetenable from NetGearTelnetEnable and it did work so far as establishing connection with no prompt. so i couldn't run any command (nvram show) at that point. then made a cardinal mistake of upgrading the firmware and now it refuses to allow telnet connection. i might be able to roll back the firmware. the default firmware does provide upgrading from it's GUI interface and i'm hoping to try the img you suggested in the thread to see if i can get a partially working openwrt (mainly telnet/ssh/shell prompt) and take it from there. this all has to wait for a while though. i can get back to this towards the end of December when i have more time. in the mean time please keep your ideas/suggestions coming. thanks for the help. SGT. Garcia ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
On Nov 19 18:43 +0100, Rafał Miłecki wrote: Hi Garcia, Could you provide us NVRAM dump once you get this device? You have access to nvram show command in both: CFE and original firmware I believe. -- Rafał oh and i don't see (couldn't find) where i can run 'nvram show' in the original firmware (netgear genie). someone here might know? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Oopses on ZyXEL NBG6716 (atheros)
Hi! Thanks for the hint. I could now isoliate it to this bug: https://dev.openwrt.org/ticket/18325 Kind regards, André On 25.11.2014 16:23, John Crispin wrote: build an image with KALLSYMS please and send a new log Mit freundlichen Grüßen André Valentin Systemadministrator -- Internet * Netzwerk * Mobile Daten Citrix Silver Solution Advisor Ausserhalb unserer Geschäftszeiten (Montag bis Freitag von 8:30 Uhr bis 17:30 Uhr, ausgenommen gesetzliche Feiertage in NRW) stehen wir Ihnen gemäß Ihrer jeweiligen Service-Level-Agreements unter der Ihnen mitgeteilten Telefonnummer für Störungen und Notfälle zur Verfügung. Sie können natürlich auch gerne jederzeit unter supp...@marcant.net ein Ticket eröffnen, welches am nächsten Arbeitstag bearbeitet wird. MarcanT GmbH, Ravensberger Str. 10 G, D - 33602 Bielefeld Fon: +49 (521) 95945-0 | Fax -18 URL: http://www.marcant.net | http://www.global-m2m.com Geschäftsführer: Thorsten Hojas Handelsregister: AG Bielefeld, HRB 35827 USt-ID Nr.: DE 190203238 ___ CONFIDENTIALITY NOTICE The contents of this email are confidential to the ordinary user of the email address to which it was addressed and may also be privileged. If you are not the addressee of this email you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this email in error please email the sender by replying to this message. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
SGT == SGT Garcia darwinsker...@gmail.com writes: SGT first question, do i absolutely need a serial console to get an SGT interface with CFE? [...] SGT [...] this all has to wait for a while though. i can get back to this SGT towards the end of December when i have more time. in the mean time SGT please keep your ideas/suggestions coming. thanks for the help. Everyone should have one. At this price (or similar), there isn't a good reason to not have several: http://www.ebay.com/itm/USB-To-RS232-TTL-UART-PL2303HX-Auto-Converter-USB-to-COM-Cable-Adapter-Module-/310676792112 ... particularly if you've got some lead time, since coming from china might mean you need to wait a while. -- Russell Senior, President russ...@personaltelco.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
Russell Senior russ...@personaltelco.net wrote: Everyone should have one. At this price (or similar), there isn't a good reason to not have several: http://www.ebay.com/itm/USB-To-RS232-TTL-UART-PL2303HX-Auto-Converter-USB-to-COM-Cable-Adapter-Module-/310676792112 ... particularly if you've got some lead time, since coming from china might mean you need to wait a while. And if you are near Ottawa, ON (Toronto, Montreal), I bought like 30 of them, and I'd be happy to mail you one, since they fit in a standard Canada Post envelope. Unicast me. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] I'd like to donate a Netgear N150 WNR1000 v3
On 26 November 2014 at 23:41, SGT. Garcia darwinsker...@gmail.com wrote: On Nov 19 18:43 +0100, Rafał Miłecki wrote: On 12 November 2014 21:59, Alex Henrie alexhenri...@gmail.com wrote: 2014-11-11 23:51 GMT-07:00 Rafał Miłecki zaj...@gmail.com: On 11 November 2014 23:26, Alex Henrie alexhenri...@gmail.com wrote: Is no one interested? Come on, I'm offering free hardware to play with ;-) I already have about 10-20 Broadcom based boars in my drawer ;) Not that excited with another one. However I'd be happy to help adding support for WNR1000 v3. Could you attach serial console to it and test some patched OpenWrt builds? It sounds like a fun project, but SGT. Garcia darwinsker...@gmail.com volunteered to work on it, and I have already mailed the device to him. I'm sure SGT. Garcia will contact you for help once he receives the device. Thanks for your work on OpenWrt! Could you provide us NVRAM dump once you get this device? You have access to nvram show command in both: CFE and original firmware I believe. first question, do i absolutely need a serial console to get an interface with CFE? i tried telnetenable from NetGearTelnetEnable and it did work so far as establishing connection with no prompt. so i couldn't run any command (nvram show) at that point. Yes. CFE doesn't implement ssh/telnet, so serial console is the way to talk with it. Plus you need serial console to watch OpenWrt booting process, so we can what goes wrong. then made a cardinal mistake of upgrading the firmware and now it refuses to allow telnet connection. i might be able to roll back the firmware. You mean upgrading to the latest Netgear firmware? Well, it doesn't matter if they disabled telnet server in it. We don't really telnet access to the Netgear's firmware. the default firmware does provide upgrading from it's GUI interface and i'm hoping to try the img you suggested in the thread to see if i can get a partially working openwrt (mainly telnet/ssh/shell prompt) and take it from there. First provide me NVRAM dump, so I can add support for WNR1000 v3. Don't try to install OpenWrt before me doing that. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] netifd v2: Fix source routing for IPv4
Thanks, applied. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] O_DIRECT not supported on openwrt?
Hi, I try to open file with O_DIRECT flag on openwrt, But error EINVAL is returned. I have selected O_DIRECT support in kernel_menuconfig. Are there any other configuration about this? Best Regards, zhenjun_...@icloudaegis.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Oopses on ZyXEL NBG6716 (atheros)
Hi! thanks for your offer. Please wait a week for me the test it, just to proove it. I will post here and in the ticket. Kind regards, André On 27.11.2014 08:28, John Crispin wrote: Hi, do we need only this - http://patchwork.ozlabs.org/patch/349076/ or all 6 from the series ? John Mit freundlichen Grüßen André Valentin Systemadministrator -- Internet * Netzwerk * Mobile Daten Citrix Silver Solution Advisor Ausserhalb unserer Geschäftszeiten (Montag bis Freitag von 8:30 Uhr bis 17:30 Uhr, ausgenommen gesetzliche Feiertage in NRW) stehen wir Ihnen gemäß Ihrer jeweiligen Service-Level-Agreements unter der Ihnen mitgeteilten Telefonnummer für Störungen und Notfälle zur Verfügung. Sie können natürlich auch gerne jederzeit unter supp...@marcant.net ein Ticket eröffnen, welches am nächsten Arbeitstag bearbeitet wird. MarcanT GmbH, Ravensberger Str. 10 G, D - 33602 Bielefeld Fon: +49 (521) 95945-0 | Fax -18 URL: http://www.marcant.net | http://www.global-m2m.com Geschäftsführer: Thorsten Hojas Handelsregister: AG Bielefeld, HRB 35827 USt-ID Nr.: DE 190203238 ___ CONFIDENTIALITY NOTICE The contents of this email are confidential to the ordinary user of the email address to which it was addressed and may also be privileged. If you are not the addressee of this email you may not copy, forward, disclose or otherwise use it or any part of it in any form whatsoever. If you have received this email in error please email the sender by replying to this message. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
