Re: [OpenWrt-Devel] Basic Package/Feed Workflow
Chad == Chad Monroe c...@monroe.io writes: Chad [...] The core problem I need to solve is how to compile/test a Chad package and make change after change after change to it, then Chad when itas ready, create a patch set. I have a feeling Iave been Chad doing things the hard way for a while and would appreciate a Chad push in the right direction. I love what OpenWRT is doing for Chad the community and an more than happy to contribute back; if this Chad is something that isnat in a wiki and should be Iam more than Chad happy to document it if someone can help me get the procedure Chad straight. Thanks for your time, Is this what you are looking for? http://wiki.openwrt.org/doc/devel/patches#iteratively.modify.patches.without.cleaning.the.source.tree -- 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] Basic Package/Feed Workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/28/2014 07:20 AM, Chad Monroe wrote: The core problem I need to solve is how to compile/test a package and make change after change after change to it, then when it’s ready, create a patch set. I have a feeling I’ve been doing things the hard way for a while and would appreciate a push in the right direction. I love what OpenWRT is doing for the community and an more than happy to contribute back; if this is something that isn’t in a wiki and should be I’m more than happy to document it if someone can help me get the procedure straight. Thanks for your time, What I do for step by step development is to create a soft link to my project folder: ln -s ~/myproject/.git openwrt/package/myproject/git-src Enable Advanced configuration options = Enable package source tree override so that OpenWrt will get follow the soft link. Now you can edit the sources of your package and hit compile every time. regards, mwarning -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJS52yzAAoJECHrh56PP4wp5bAH/AuqMRc+5rEjthFlGIAXkCy/ LSVa1osBeWZIWoww35fbHotBPVnY5K/Yx2ihVkX3IKnEQsUe3mO29Jd4dJcfa/Y7 pdbbNRXXxl2PW9QBVMnKoBOb4XM3Q3NGmVVy/pJx5GW3nnxQs1hK0EiNCzfgrBmr 34P5INV2owCuGWdxBGsLWAXvLALbgKXKwm8yi7WfRptMyYxvLAvl2gLAhe/AYSTC cLm9ydbi4HMmFp9gRNq5dvp0N0YJ6RObIGyDwm2FfNMpLZ5s+oYSv+jGCpLLuqqU UtvcCfW05J/KwYFuHgHk+BshzxC+1+bTnek1WewXZweLLWYDrKvnBskEu5YtSVM= =CrRi -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] ssh link-local fails with Servname not supported for ai_socktype
Am I the only one ssh'ing into link-local addresses from openwrt devices? I came across a recent regression that makes this impossible, and couldn't find any report on google / this list. It's bugging the hell out of me on recent trunks (last known good rev: r36140, first known broken: r38505, but didn't bisect further) root@OpenWrt_r38505:/# ssh fe80::f8d1:11ff:fea0:fc%wlan0 ssh: Exited: Error resolving 'fe80::f8d1:11ff:fea0:fc' port 'wlan0'. Servname not supported for ai_socktype root@OpenWrt_r38505:/# ssh [fe80::f8d1:11ff:fea0:fc%wlan0] ssh: Exited: Error resolving '[fe80::f8d1:11ff:fea0:fc' port 'wlan0]'. Servname not supported for ai_socktype root@OpenWrt_r38505:/# opkg list dropbear dropbear - 2013.59-1 while on r36140 I could perfectly do: root@OpenWrt_r36140:~# ssh fe80::6670:2ff:fe3d:a0f9%wlan1 root@fe80::6670:2ff:fe3d:a0f9%wlan1's password: root@OpenWrt_r36140:~# opkg list dropbear dropbear - 2012.55-2 Any pointers on this regression? or workarounds? I first thought this would be related to the busybox-menuconfig changes, but then i remembered this is actually dropbear, so unrelated... I dug around menuconfig, and checked dropbear Makefile, but there aren't many knobs to tweak It might perfectly be an upstream bug, so i'll poke around git logs and try to bisect a little Cheers! gui::/128 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ssh link-local fails with Servname not supported for ai_socktype
It's a bug in upstream dropbear afair. At some point they changed some scp port separator to % to fix another issue and that breaks the parsing of LL addrs. Bug introduced by this: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2013q2/001390.html ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Android connectivity issues - MyNet n600
Hi all, I've come up against an issue with my MyNet n600 on both the 5ghz and 2.4ghz radios. I'm currently using the latest trunk (r39406). I have an Android phone which will authenticate and stay connected but loses all network connectivity. Any other non Android device will stay connected and continue to work. This is similar to the fixed issue AR9344 wifi dying on WD N600 routers but it's happening on both radios and only with the Android device. Restarting the device restores connectivity to the Android device for a moment but then it loses it again. There are no messages in the logs to indicate that something has gone wrong. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Fwd: [Battlemesh] Battlemesh v7 Call for talks and workshops
Hello list, the battlemesh v7 call for talks is out, it would be great to see your WiFi/Mesh related talks and workshops in Leipzig this year. :) If you haven't booked a hotel yet, have a look at the accomodation package [1], where you can get bed and breakfast for the whole week (early bird price for 150EUR until Feb 15th). The event itself is free of charge. Cheers, Simon [1] http://battlemesh.org/BattleMeshV7#Participant_Registration_and_Fee Do you have an idea or project related to mesh routing protocols? Are you involved in a community networking project that uses a mesh network? Are you aware of a related issue that you think should be discussed? Your workshop or presentation proposal is welcomed to BattleMeshV7 Leipzig! What is Battlemesh? --- The Wireless Battle of the Mesh is an event that aims at bringing together people from across Europe and beyond to test the performance of different routing protocols for ad-hoc networks, like Babel, B.A.T.M.A.N., BMX, OLSR, 802.11s and Static Routing. It is a tournament with a social character. If you are a mesh networking enthusiast, community networking activist, or have an interest in mesh networks you might want to check this out ! The goal of the WirelessBattleMesh events is to set-up hands-on testbed for each available mesh routing protocol with a standard test procedure for the different mesh networks. During the different WBM events, similar hardware and software configuration will be used based on the OpenWRT BoardSupportPackage and packages for each protocol implementation. The WBM events are also a great opportunity to develop testing tools for PHY/MAC radio layers (drivers, scripts and PHY analyzers) . This years Battlemesh will take place from 12 - 18 May 2014 in Leipzig, Germany at the Sublab, Karl-Heine-Straße 93, 04229 Leipzig. http://battlemesh.org Format and topic of talks - Workshops or talks relating directly to open source mesh routing protocols will be prioritised, but we welcome proposals of anything you think may be of interest to mesh routing and community networking enthusiasts. They may take any format, for example a presentation, talk, discussion, debate, practical workshop, or film showing. To get an idea of the kinds of talks and workshops at the previous events, see http://battlemesh.org/BattleMeshV6/Agenda, http://battlemesh.org/BattleMeshV5/Agenda and http://battlemesh.org/BattleMeshV4/Agenda Lightening talks Lightening talks are shorter talks which can be submitted later than the main workshops deadline, to allow everybody to have the opportunity to present their project/idea. Each lightening talk will be 7 minutes long followed by 3 minutes of questions. Projector slides can be submitted before in PDF format to: submissi...@battlemesh.org Submissions --- To allow an efficient handling of your proposal, please provide the following information and send them by email to the email to the address below: * Your name * What format will it take (talk/workshop/panel discussion/lightening talk) * Your topic headline * Your topic description which can be brief (does not need to exceed a couple of lines) but should provide a reasonable summary of your talk * The dates of your stay at the event and (optional) preferred day for your slot * The length of the slot if you wish to do a workshop (all other slots will be limited to one hour) * Any requirements you need, for example, a projector. Deadline The deadline for proposals is the 1st of May. Contact --- Email your proposals or specific questions to: submissi...@battlemesh.org For general questions, please use the Battlemesh mailing list: http://ml.ninux.org/mailman/listinfo/battlemesh Please forward this message any groups or individuals who might be interested. ___ Battlemesh mailing list battlem...@ml.ninux.org http://ml.ninux.org/mailman/listinfo/battlemesh ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Android connectivity issues - MyNet n600
I'm no expert, but you could try running hostapd in debug mode and 'Capture Management Traffic' to see what you can find: See http://wiki.openwrt.org/doc/devel/debugging On Tue, Jan 28, 2014 at 4:59 AM, omggo oom...@gmail.com wrote: Hi all, I've come up against an issue with my MyNet n600 on both the 5ghz and 2.4ghz radios. I'm currently using the latest trunk (r39406). I have an Android phone which will authenticate and stay connected but loses all network connectivity. Any other non Android device will stay connected and continue to work. This is similar to the fixed issue AR9344 wifi dying on WD N600 routers but it's happening on both radios and only with the Android device. Restarting the device restores connectivity to the Android device for a moment but then it loses it again. There are no messages in the logs to indicate that something has gone wrong. ___ 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] [PATCH] [toolchain] add libubacktrace library
This patch adds support for backtrace functions also known from *glibc that are declared in execinfo.h. This functionality in uClibc is implemented in libubacktrace library. The application that needs to be compiled with backtrace functions must be linked against libubacktrace.so. Signed-off-by: Jiri Slachta slac...@cesnet.cz --- package/libs/toolchain/Makefile | 16 toolchain/uClibc/config-0.9.33.2/common |2 +- 2 files changed, 17 insertions(+), 1 deletion(-) diff --git a/package/libs/toolchain/Makefile b/package/libs/toolchain/Makefile index 202e9d0..d678486 100644 --- a/package/libs/toolchain/Makefile +++ b/package/libs/toolchain/Makefile @@ -175,6 +175,12 @@ $(call Package/libc/Default) TITLE:=POSIX thread library debugging support endef +define Package/libubacktrace +$(call Package/libc/Default) + DEPENDS:=@USE_UCLIBC + TITLE:=Backtrace functions library +endef + define Package/librt $(call Package/libc/Default) TITLE:=POSIX.1b RealTime extension library @@ -475,6 +481,15 @@ ifeq ($(CONFIG_EXTERNAL_TOOLCHAIN),) endif endef + define Package/libubacktrace/install + $(INSTALL_DIR) $(1)/lib + ifeq ($(USE_UCLIBC),y) + $(CP) \ + $(TOOLCHAIN_DIR)/lib/libubacktrace-$(LIBC_SO_VERSION).so.* + $(1)/lib/ + endif + endef + define Package/libpthread/install_lib $(if $(wildcard $(TOOLCHAIN_DIR)/lib/libpthread_so.a),$(CP) $(TOOLCHAIN_DIR)/lib/libpthread_so.a $(1)/lib/libpthread_pic.a) endef @@ -589,6 +604,7 @@ $(eval $(call BuildPackage,libssp)) $(eval $(call BuildPackage,libstdcpp)) $(eval $(call BuildPackage,libpthread)) $(eval $(call BuildPackage,libthread-db)) +$(eval $(call BuildPackage,libubacktrace)) $(eval $(call BuildPackage,librt)) $(eval $(call BuildPackage,libgfortran)) $(eval $(call BuildPackage,ldd)) diff --git a/toolchain/uClibc/config-0.9.33.2/common b/toolchain/uClibc/config-0.9.33.2/common index fce922e..a90e321 100644 --- a/toolchain/uClibc/config-0.9.33.2/common +++ b/toolchain/uClibc/config-0.9.33.2/common @@ -42,7 +42,7 @@ LDSO_RUNPATH=y # LDSO_STANDALONE_SUPPORT is not set # LINUXTHREADS_NEW is not set # LINUXTHREADS_OLD is not set -# UCLIBC_HAS_BACKTRACE is not set +UCLIBC_HAS_BACKTRACE=y UCLIBC_HAS_THREADS_NATIVE=y # MALLOC is not set MALLOC_GLIBC_COMPAT=y -- 1.7.9.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] b53: leaking packets for a second during initialization?
2014-01-21 Rafał Miłecki zaj...@gmail.com: I believe I'm observing packets leaking between WAN and LAN ports during OpenWrt booting process. That happens on devices with bgmac, but it seems to be related to the b53. Ping? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] Broadcom code found.
2014-01-11, José Vázquez Fernández ppvazquez...@gmail.com:
While Daniel González and me were fighting with jffs2 tested some code
extracted from Netgear. Here are what we found.
We only tested brcm_wait, broadcom checksum code and the modification in
tlbex.c and nothing strange happened when we flashed it.
Hope this could help for the Broadcom SoCs and maybe others.
diff -urN b/include/asm-mips/checksum.h a/include/asm-mips/checksum.h
--- b/include/asm-mips/checksum.h 2007-06-12 16:13:11.0 +0200
+++ a/include/asm-mips/checksum.h 2010-05-31 03:43:32.0 +0200
@@ -98,6 +98,64 @@
* By Jorge Cwik jo...@laser.satlink.net, adapted for linux by
* Arnt Gulbrandsen.
*/
+
+#if defined(CONFIG_MIPS_BRCM)
+
+/* Brcm version can handle unaligned data. Merged from brcm 2.6.8
kernel.*/
+static inline __sum16 ip_fast_csum(const void *iph, unsigned int ihl)
+{
+ if (((__u32)iph0x3) == 0) {
+ unsigned int *word = (unsigned int *) iph;
+ unsigned int *stop = word + ihl;
+ unsigned int csum;
+ int carry;
+
+ csum = word[0];
+ csum += word[1];
+ carry = (csum word[1]);
+ csum += carry;
+
+ csum += word[2];
+ carry = (csum word[2]);
+ csum += carry;
+
+ csum += word[3];
+ carry = (csum word[3]);
+ csum += carry;
+
+ word += 4;
+ do {
+ csum += *word;
+ carry = (csum *word);
+ csum += carry;
+ word++;
+ } while (word != stop);
+
+ return csum_fold(csum);
+ } else {
+ __u16 * buff = (__u16 *) iph;
+ __u32 sum=0;
+ __u16 i;
+
+ // make 16 bit words out of every two adjacent 8 bit words in
the packet
+ // and add them up
+ for (i=0;iihl*2;i++){
+ sum = sum + (__u32) buff[i];
+ }
+
+ // take only 16 bits out of the 32 bit sum and add up the
carries
+ while (sum16)
+ sum = (sum 0x)+(sum 16);
+
+ // one's complement the result
+ sum = ~sum;
+
+ return ((__sum16) sum);
+ }
+}
+
+#else
+
static inline __sum16 ip_fast_csum(const void *iph, unsigned int ihl)
{
const unsigned int *word = iph;
I've tested the above code and the network throughput improved between
0'5 to 1% while running rsync with cifs and a 500 GB usb hdd with a
BCM63281 based board.
___
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] hostapd: Fix basic_rate setup with netifd
Applied in r39411 - thanks! ~ Jow signature.asc Description: OpenPGP digital signature ___ 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] hostapd: Fix 80211w setup with netifd
Applied in r39412 - thanks! ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [ubus] lua: fix whitespaces and typo
Applied in b356773921a89b370f8ccb34c9ea5f21148115ea - thanks! ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [ubus] lua: allow methods with no arguments
Applied in 4e82a1fabb87b5e3c948a792e16b0fac3702721b - thanks! ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] b53: leaking packets for a second during initialization?
On Tue, Jan 28, 2014 at 8:41 PM, Rafał Miłecki zaj...@gmail.com wrote: 2014-01-21 Rafał Miłecki zaj...@gmail.com: I believe I'm observing packets leaking between WAN and LAN ports during OpenWrt booting process. That happens on devices with bgmac, but it seems to be related to the b53. Ping? Sorry, somehow forgot about this one. Probably moving the part enabling the software forwarding (and bailing out if the bit doesn't stick) in b53_switch_reset() after the call to b53_enable_ports() should fix it. Regards Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH]: Backporting of NAND support to mvebu
Hi all, Please find the follow repository: https://github.com/mazareeb/openwrt/commits/master This repository adds 5 patches that mainly aim to back port the recently added NAND support to mainline to openwrt. On the way other patches that address other aspects of mvebu are integrated. The 3 initial patches backport the relevant mainline patches accepted to 3.11, 3.12, and 3.13 respectively. 4th Patch updates the kernel config. 5th Patch adds support for the Armada XP GP board (DB-MV784MP-GP). Main testing platforms are armada-xp-gp, armada-370-rd boards. Thanks Seif ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
