Re: [OpenWrt-Devel] [PATCH] ag71xx: fix a race involving netdev registration
2013.11.03. 9:16 keltezéssel, Catalin Patulea írta: In particular, phy_connect before register_netdev. This is because register_netdev runs the netdev notifiers, which can race with the rest of the initialization in ag71xx_probe. In my case this manifested in two ways: 1) If ag71xx is compiled as a module and inserted after netifd has started, netifd is notified by register_netdev before the call to ag71xx_phy_connect. netifd tries to bring the interface up, which calls ag71xx_open, which in turn enters ag71xx_phy_start. This keys off ag-phy_dev (which is still NULL) and thinks this is a fixed-link board, and enters ag71xx_link_adjust. This looks at ag-speed which is not yet initialized and hits the BUG() in the switch (ag-speed) in ag71xx_link_adjust. This is the wrong code path for ag71xx_phy_start - my board has PHYs that need to be brought up with phy_start. Doing ag71xx_phy_connect before register_netdev ensures that ag-phy_dev is non-NULL before ag71xx_phy_start is ever called. 2) When ag71xx is built into the kernel, and netconsole is enabled, there is a gap in the initial burst of replayed printks right after the netdev comes up. My assumption is that netconsole is also triggered by a netdev notifier, and part of this printk burst happens before the call into ag71xx_phy_connect, so part of the burst is lost while the PHY comes up. This patch fixes the gap - all the printks before eth0 comes up are bursted in full when netconsole initializes. ag71xx_phy_connect_xxx no longer runs with a registered netdev, so the logging has been adjusted accordingly to avoid unregistered net_device or eth%d messages in dmesg. Signed-off-by: Catalin Patulea c...@vv.carleton.ca Applied. Thanks, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] zram backport for Attitude Adjustment
Hi Ben, Thanks for the feedback. That's strange, although has logic. Even more strage is that your device has 32MB of Ram so it should be able to be handling things well. Can you compile the trunk (Barrier Breaker) and test with it on the same device to find out if it will behavior the same way ? Perhaps the problem is somewhere else or something specific to the way zram works on kernel 3.3 like Hauke mentioned in a earlier email. Regards, Fernando On 8 November 2013 05:40, Ben West b...@gowasabi.net wrote: As someone who runs AA r38247 patched to include zram support, I can add anecdotal experience that some processes don't behave well when paged to swap. I'm running AR7240 devices with 32MB RAM (i.e. UBNT M gear) as mesh nodes, and I've found that services like olsrd, coovachilli, and wpa_supplicant seem to behave erratically if they're swapped out and then back in. For this reason, I only enable 3MBytes of swap, preferring not to depend on it for normal operation. Only enough so that a node can detect when it's in a low-memory state and do something to recover (e.g. reboot). I've not had opportunity to test whether this problem also happens with the newer kernel under BB. On Thu, Nov 7, 2013 at 4:10 PM, Hauke Mehrtens ha...@hauke-m.de wrote: On 11/07/2013 12:08 AM, Fernando Frediani wrote: Hi Hauke, What you mean by zram worked differently ? As far as I know zram (previously known as compcache) has been merged to the Linux Kernel at 3.2 so it should be there on 3.3 as well (check drivers/staging/zram). In Kernel 3.3 zram depends on XVMALLOC being build into the kernel, but in OpenWrt our plan was to build zram completely in a module so if someone does not want it nothing changes. I have talked to Bastien in another conversation and he mentioned he has a WRT54G running fine with Barrier Breaker (which has zram as a kmod package), but not sure it's enabled by default or not. I'm interested to to hear if it's having any improvements (how effective the swap zram is being used) and if it is a stripped down build (no LuCI and other packages) or a normal build. Also how big the swap zram should be ? 6MB (as kalua script suggests) or 8MB (half of the memory) ? Yes Bastien made the patch which introduced zram support. If you want that in AA, it should be possible to make it also build as a kernel module. When it is there you can try out what is the best size. I have seen a couple of people saying they have managed to flash brcm47xx Attitude Adjustment to WRT54G routers but got instability issues (slowness or disconnects). Yes flashing works, it just runs out of memory very often and the OOM killer starts to kill processes. So if Barrier Breaker is working fine on WRT54G (with zram activated?) then what would be the challenges to port that work already done back to Attitude Adjustment ? I do not know if it works fine on these devices, but if it does with some traffic going over the router over some time then we should try to backport zram support. Best regards, Fernando On 6 November 2013 18:17, Hauke Mehrtens ha...@hauke-m.de mailto:ha...@hauke-m.de wrote: On 11/06/2013 05:15 PM, Fernando Frediani wrote: Hello Hauke, I have seen a few emails from you on openwrt-devel list about the zram module and also saw it is already present on the trunk(Barrier Breaker). Was wondering if there is any work going on or will be to backport it to Attitude Adjustment then perhaps we can run it on the good and old WRT54G and similar models with 16MB ? How difficult is it to backport to AA as it is already done for trunk ? Thanks and best regards, Fernando Hi Fernando, I have no plan to backport zram to Attitude Adjustment. Attitude Adjustment uses kernel 3.3 and there zram worked differently or was not included at all, I do not know exactly. But I would like to see zram backported to AA and would like to see a nice patch. Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Ben West http://gowasabi.net b...@gowasabi.net 314-246-9434 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Newbie needs help in building stable for newer hardware
Hello, anyone can provide insight? ;-) Thanks, Florian 2013/10/9 Florian Effenberger flo...@gmail.com: Hello, I consider myself quite experienced with OpenWRT already, having deployed a few devices, but sadly, I'm a totally development newbie - so sorry if my question is maybe stupid. ;-) I'd like to stick with OpenWRT stable for my deployments, to have the same base system. The problem, however, is that my favorite device (TP-Link WDR4300) is rapidly changing its hardware revision, making it necessary to use trunk for newer models. Is there an easy way to compile OpenWRT stable only with those patchsets necessary to make it work with newer hardware revisions? From what I recall, micro releases of OpenWRT stable often include newer hardware revisions, without any other changes from trunk, so I assume it must be possible in theory - lacking any practical experience, however, I seek for your help. :-) Thanks a lot, and keep up the good work - you folks rock! Florian ___ 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] mtd_get_mac_ascii bugfix
2013.11.07. 17:23 keltezéssel, Daniel Gimpelevich írta:
The mtd_get_mac_ascii utility function was broken. This fixes it.
Signed-off-by: Daniel Gimpelevich dan...@gimpelevich.san-francisco.ca.us
Index: package/base-files/files/lib/functions.sh
===
--- a/package/base-files/files/lib/functions.sh (revision 38679)
+++ b/package/base-files/files/lib/functions.sh (working copy)
@@ -248,15 +248,13 @@
local part
local mac_dirty
- . /lib/functions.sh
-
part=$(find_mtd_part $mtdname)
if [ -z $part ]; then
echo mtd_get_mac_ascii: partition $mtdname not found! 2
return
fi
- mac_dirty=$(strings $part | sed -n 's/'$key'=//p')
+ mac_dirty=$(strings $part | sed -n 's/^'$key'=//p')
# canonicalize mac
printf %02x:%02x:%02x:%02x:%02x:%02x 0x${mac_dirty//:/ 0x}
}
___
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] [PATCH 1/2] mtd_get_mac_ascii bugfix
2013.11.08. 13:20 keltezéssel, Gabor Juhos írta: 2013.11.07. 17:23 keltezéssel, Daniel Gimpelevich írta: The mtd_get_mac_ascii utility function was broken. This fixes it. Signed-off-by: Daniel Gimpelevich dan...@gimpelevich.san-francisco.ca.us Applied. Thanks, Gabor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] mtd_get_mac_ascii bugfix
On Fri, 2013-11-08 at 13:24 +0100, Gabor Juhos wrote: 2013.11.08. 13:20 keltezéssel, Gabor Juhos írta: 2013.11.07. 17:23 keltezéssel, Daniel Gimpelevich írta: The mtd_get_mac_ascii utility function was broken. This fixes it. Signed-off-by: Daniel Gimpelevich dan...@gimpelevich.san-francisco.ca.us Applied. Thanks, Gabor You changed it from using printf to using tr, which might not be good if colons are missing. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] add support for RIPEMD/160 to openssl
This patch adds support for RIPEMD/160 to openssl RIPEMD is needed to update erlang and i'd like to enable RIPEMD160 support in openssh. Size compared: openssl without RIPEMD/160 support: 647K 29. Okt 20:00 bin/ar71xx/packages/libopenssl_1.0.1e-2_ar71xx.ipk openssl with RIPEMD/160 support: 652K 8. Nov 15:11 bin/ar71xx/packages/libopenssl_1.0.1e-2_ar71xx.ipk So the file size just grows ~5kb, which shouldn't be a problem. Signed-off-by: Peter Wagner tripo...@gmx.atdiff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile index a280ff4..27b6e99 100644 --- a/package/libs/openssl/Makefile +++ b/package/libs/openssl/Makefile @@ -78,7 +78,7 @@ endef OPENSSL_NO_CIPHERS:= no-idea no-md2 no-mdc2 no-rc5 no-sha0 no-smime \ - no-rmd160 no-aes192 no-ripemd no-camellia no-ans1 no-krb5 + no-aes192 no-camellia no-ans1 no-krb5 OPENSSL_OPTIONS:= shared no-err no-hw no-threads zlib-dynamic no-sse2 ifdef CONFIG_OPENSSL_ENGINE_CRYPTO ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] DHCP renews triggering 6rd interface up/down flaps
I'm using the following configuration (6rd interface on top of an IPoEv4 interface) config interface 'wan' option proto 'dhcp' option ifname 'eth4' config interface '6rd' option proto '6rd' option peeraddr '192.88.99.1' option ip6prefix '2010:1234::' option ip6prefixlen '32' option ip4prefixlen '0' Bringing up the 6rd interface is working fine; however when the wan interface is renewing the 6rd interface is going down/up. Looking into the dhcp script it informs netifd with the received IP address and routes; which results in the 6rd interface flapping as it has a host dependency on a default IPv4 route. Due to the fact the 6rd interface flaps the delegated prefix is removed/inserted on the lan interface which results into two RA messages in quick succession from the 6relayd daemon with the preferred lifetime set 0 in the first message and 1800 secs in the second message for the delegated prefix. As long as the leasetime is quite large this is not a big issue; but with a small leasetime on the WAN (which is the case in my scenario) this is quite annoying as RA messages are transmitted on the LAN triggered by DHCP renew messages on the WAN which invalidate/validate the same prefix in a short time. Shouldn't netifd check if the received route differs from the previous received default route before tearing down/up the 6rd interface ? Br, Hans ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] mtrace
Hi, is it possible to use mtrace as referred here http://linux.die.net/man/3/mtrace in OpenWRT ? I tried using this https://dev.openwrt.org/ticket/7660 but my trace file is every time empty ... :-( Any ideas ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mtrace
Hi Le 08/11/2013 17:33, Pietro Paolini a écrit : Hi, is it possible to use mtrace as referred here http://linux.die.net/man/3/mtrace in OpenWRT ? Explain what you really want to do, maybe someone can 'show' you another soft? I've worked with strace (but it doesn't catch malloc) and i think gdb is working I tried using this https://dev.openwrt.org/ticket/7660 but my trace file is every time empty ... :-( Any ideas ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [RFC] uClibc: Deactivate oversized thread stack cache
From: Sven Eckelmann s...@open-mesh.com A small system like the common home router doesn't have 40 MiB per process for a dirty stack cache. This can easily lead to an overbooking OOM problem and caused a lot of hangs+reboots on 32 MiB systems running nodogsplash. Not using a stack cache can increase the time to spawn new threads. This is hopefully no problem for system not running a lot of parallel computations. Signed-off-by: Sven Eckelmann s...@open-mesh.com --- toolchain/uClibc/patches-0.9.33.2/990-no-stack-cache.patch | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 toolchain/uClibc/patches-0.9.33.2/990-no-stack-cache.patch diff --git a/toolchain/uClibc/patches-0.9.33.2/990-no-stack-cache.patch b/toolchain/uClibc/patches-0.9.33.2/990-no-stack-cache.patch new file mode 100644 index 000..8f0b511 --- /dev/null +++ b/toolchain/uClibc/patches-0.9.33.2/990-no-stack-cache.patch @@ -0,0 +1,11 @@ +--- a/libpthread/nptl/allocatestack.c b/libpthread/nptl/allocatestack.c +@@ -100,7 +100,7 @@ + /* Cache handling for not-yet free stacks. */ + + /* Maximum size in kB of cache. */ +-static size_t stack_cache_maxsize = 40 * 1024 * 1024; /* 40MiBi by default. */ ++static size_t stack_cache_maxsize = 0; /* embedded systems don't have enough ram for dirty stack caches */ + static size_t stack_cache_actsize; + + /* Mutex protecting this variable. */ -- 1.8.4.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [v3, 1/4] Add kernel support for Sagemcom F@ST2704V2 ADSL router
Can this pretty please not die to bitrot?
I need this merged so badly ;_;
On Thu, Oct 31, 2013 at 7:33 PM, Marcin Jurkowski marci...@gmail.comwrote:
This adds kernel support support for Sagemcom F@st 2704 wireless ADSL
router.
It's a BCM6328-based 802.11n wireless router with USB port and ADSL2+
modem equipped with 64 MiB RAM and 8 MiB flash.
---
.../brcm63xx/patches-3.10/536-board_fast2704.patch | 133
+
1 file changed, 133 insertions(+)
create mode 100644
target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
diff --git a/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
new file mode 100644
index 000..db34932
--- /dev/null
+++ b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
@@ -0,0 +1,133 @@
+--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
b/arch/mips/bcm63xx/boards/board_bcm963xx.c
+@@ -1477,6 +1477,122 @@ static struct board_info __initdata boar
+ },
+ };
+
++static struct board_info __initdata board_FAST2704V2 = {
++ .name = F@ST2704V2,
++ .expected_cpu_id= 0x6328,
++
++ .has_uart0 = 1,
++ .has_pci= 1,
++ .has_ohci0 = 1,
++ .has_ehci0 = 1,
++ .has_usbd = 1,
++
++ .has_enetsw = 1,
++
++ .enetsw = {
++ .used_ports = {
++ [0] = {
++ .used = 1,
++ .phy_id = 1,
++ .name = Port 1,
++ },
++ [1] = {
++ .used = 1,
++ .phy_id = 2,
++ .name = Port 2,
++ },
++ [2] = {
++ .used = 1,
++ .phy_id = 3,
++ .name = Port 3,
++ },
++ [3] = {
++ .used = 1,
++ .phy_id = 4,
++ .name = Port 4,
++ },
++ },
++ },
++
++ .leds = {
++ /* front LEDs */
++ {
++ .name = F@ST2704V2
:green:power,
++ .gpio = 4,
++ .active_low = 1,
++ .default_trigger= default-on,
++ },
++ {
++ .name = F@ST2704V2:red:power,
++ .gpio = 5,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:red:inet,
++ .gpio = 2,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:dsl,
++ .gpio = 3,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:inet,
++ .gpio = 11,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:usb,
++ .gpio = 1,
++ .active_low = 1,
++ },
++
++ /* side button LEDs */
++ {
++ .name = F@ST2704V2:green:wps,
++ .gpio = 10,
++ .active_low = 1,
++ },
++
++ /* FIXME: can't control gpio0 line in out state, needs
further investigation */
++ /*
++ {
++ .name = F@ST2704V2
:green:rfkill,
++ .gpio = 0,
++ .active_low = 1,
++ },
++ */
++
++ },
++ .buttons = {
++ {
++ .desc = reset,
++ .gpio = 23,
++ .active_low = 1,
++ .type = EV_KEY,
++ .code = KEY_RESTART,
++ .debounce_interval =
BCM963XX_KEYS_DEBOUNCE_INTERVAL,
++ },
++ {
++ .desc = wps,
++
Re: [OpenWrt-Devel] [v3, 1/4] Add kernel support for Sagemcom F@ST2704V2 ADSL router
Well if you need this that badly, you can patch it yourself :)
git clone git://git.openwrt.org/openwrt.git
2013/11/8 Weedy weedy2...@gmail.com:
Can this pretty please not die to bitrot?
I need this merged so badly ;_;
On Thu, Oct 31, 2013 at 7:33 PM, Marcin Jurkowski marci...@gmail.com
wrote:
This adds kernel support support for Sagemcom F@st 2704 wireless ADSL
router.
It's a BCM6328-based 802.11n wireless router with USB port and ADSL2+
modem equipped with 64 MiB RAM and 8 MiB flash.
---
.../brcm63xx/patches-3.10/536-board_fast2704.patch | 133
+
1 file changed, 133 insertions(+)
create mode 100644
target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
diff --git a/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
new file mode 100644
index 000..db34932
--- /dev/null
+++ b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
@@ -0,0 +1,133 @@
+--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
b/arch/mips/bcm63xx/boards/board_bcm963xx.c
+@@ -1477,6 +1477,122 @@ static struct board_info __initdata boar
+ },
+ };
+
++static struct board_info __initdata board_FAST2704V2 = {
++ .name = F@ST2704V2,
++ .expected_cpu_id= 0x6328,
++
++ .has_uart0 = 1,
++ .has_pci= 1,
++ .has_ohci0 = 1,
++ .has_ehci0 = 1,
++ .has_usbd = 1,
++
++ .has_enetsw = 1,
++
++ .enetsw = {
++ .used_ports = {
++ [0] = {
++ .used = 1,
++ .phy_id = 1,
++ .name = Port 1,
++ },
++ [1] = {
++ .used = 1,
++ .phy_id = 2,
++ .name = Port 2,
++ },
++ [2] = {
++ .used = 1,
++ .phy_id = 3,
++ .name = Port 3,
++ },
++ [3] = {
++ .used = 1,
++ .phy_id = 4,
++ .name = Port 4,
++ },
++ },
++ },
++
++ .leds = {
++ /* front LEDs */
++ {
++ .name =
F@ST2704V2:green:power,
++ .gpio = 4,
++ .active_low = 1,
++ .default_trigger= default-on,
++ },
++ {
++ .name = F@ST2704V2:red:power,
++ .gpio = 5,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:red:inet,
++ .gpio = 2,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:dsl,
++ .gpio = 3,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:inet,
++ .gpio = 11,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:usb,
++ .gpio = 1,
++ .active_low = 1,
++ },
++
++ /* side button LEDs */
++ {
++ .name = F@ST2704V2:green:wps,
++ .gpio = 10,
++ .active_low = 1,
++ },
++
++ /* FIXME: can't control gpio0 line in out state, needs
further investigation */
++ /*
++ {
++ .name =
F@ST2704V2:green:rfkill,
++ .gpio = 0,
++ .active_low = 1,
++ },
++ */
++
++ },
++ .buttons = {
++ {
++ .desc = reset,
++ .gpio = 23,
++ .active_low = 1,
++ .type = EV_KEY,
++ .code = KEY_RESTART,
++
Re: [OpenWrt-Devel] [v3, 1/4] Add kernel support for Sagemcom F@ST2704V2 ADSL router
Well if you need this that badly, you can patch it yourself :)
Checkout the git repository:
git clone git://git.openwrt.org/openwrt.git
download the patches and apply them to the local git repo.
the command for that is: git apply 'example.patch' (make sure that you
are in the openwrt directory)
I think you have to apply 4 patches since this one is 1/4.
Sorry for the earlier message that was incomplete.
-Martijn
2013/11/8 Martijn Zilverschoon thefriedzom...@gmail.com:
Well if you need this that badly, you can patch it yourself :)
git clone git://git.openwrt.org/openwrt.git
2013/11/8 Weedy weedy2...@gmail.com:
Can this pretty please not die to bitrot?
I need this merged so badly ;_;
On Thu, Oct 31, 2013 at 7:33 PM, Marcin Jurkowski marci...@gmail.com
wrote:
This adds kernel support support for Sagemcom F@st 2704 wireless ADSL
router.
It's a BCM6328-based 802.11n wireless router with USB port and ADSL2+
modem equipped with 64 MiB RAM and 8 MiB flash.
---
.../brcm63xx/patches-3.10/536-board_fast2704.patch | 133
+
1 file changed, 133 insertions(+)
create mode 100644
target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
diff --git a/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
new file mode 100644
index 000..db34932
--- /dev/null
+++ b/target/linux/brcm63xx/patches-3.10/536-board_fast2704.patch
@@ -0,0 +1,133 @@
+--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
b/arch/mips/bcm63xx/boards/board_bcm963xx.c
+@@ -1477,6 +1477,122 @@ static struct board_info __initdata boar
+ },
+ };
+
++static struct board_info __initdata board_FAST2704V2 = {
++ .name = F@ST2704V2,
++ .expected_cpu_id= 0x6328,
++
++ .has_uart0 = 1,
++ .has_pci= 1,
++ .has_ohci0 = 1,
++ .has_ehci0 = 1,
++ .has_usbd = 1,
++
++ .has_enetsw = 1,
++
++ .enetsw = {
++ .used_ports = {
++ [0] = {
++ .used = 1,
++ .phy_id = 1,
++ .name = Port 1,
++ },
++ [1] = {
++ .used = 1,
++ .phy_id = 2,
++ .name = Port 2,
++ },
++ [2] = {
++ .used = 1,
++ .phy_id = 3,
++ .name = Port 3,
++ },
++ [3] = {
++ .used = 1,
++ .phy_id = 4,
++ .name = Port 4,
++ },
++ },
++ },
++
++ .leds = {
++ /* front LEDs */
++ {
++ .name =
F@ST2704V2:green:power,
++ .gpio = 4,
++ .active_low = 1,
++ .default_trigger= default-on,
++ },
++ {
++ .name = F@ST2704V2:red:power,
++ .gpio = 5,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:red:inet,
++ .gpio = 2,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:dsl,
++ .gpio = 3,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:inet,
++ .gpio = 11,
++ .active_low = 1,
++ },
++ {
++ .name = F@ST2704V2:green:usb,
++ .gpio = 1,
++ .active_low = 1,
++ },
++
++ /* side button LEDs */
++ {
++ .name = F@ST2704V2:green:wps,
++ .gpio = 10,
++ .active_low = 1,
++ },
++
++ /* FIXME: can't control gpio0 line in out state, needs
further investigation */
++ /*
++ {
++ .name =
F@ST2704V2:green:rfkill,
++ .gpio = 0,
Re: [OpenWrt-Devel] [RFC] uClibc: Deactivate oversized thread stack cache
On 8 Nov 2013 12:52, s...@open-mesh.com wrote: From: Sven Eckelmann s...@open-mesh.com A small system like the common home router doesn't have 40 MiB per process for a dirty stack cache. This can easily lead to an overbooking OOM problem and caused a lot of hangs+reboots on 32 MiB systems running nodogsplash. Not using a stack cache can increase the time to spawn new threads. This is hopefully no problem for system not running a lot of parallel computations. Do you have any benches or log dumps that show this fixed it for you? Or just dropping it to 2mb or less? I shouldn't notice this. But anyone with running LUCI probably has enough process churn that this will hurt. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Newbie needs help in building stable for newer hardware
On 8 Nov 2013 05:10, Florian Effenberger flo...@gmail.com wrote: Hello, anyone can provide insight? ;-) Thanks, Florian Just use trunk. I update my 4300 once a week to HEAD. I I've had zero problems. 2013/10/9 Florian Effenberger flo...@gmail.com: Hello, I consider myself quite experienced with OpenWRT already, having deployed a few devices, but sadly, I'm a totally development newbie - so sorry if my question is maybe stupid. ;-) I'd like to stick with OpenWRT stable for my deployments, to have the same base system. The problem, however, is that my favorite device (TP-Link WDR4300) is rapidly changing its hardware revision, making it necessary to use trunk for newer models. Is there an easy way to compile OpenWRT stable only with those patchsets necessary to make it work with newer hardware revisions? From what I recall, micro releases of OpenWRT stable often include newer hardware revisions, without any other changes from trunk, so I assume it must be possible in theory - lacking any practical experience, however, I seek for your help. :-) Thanks a lot, and keep up the good work - you folks rock! Florian ___ 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] cmake.mk should use no-ccache variants of CC/CXX
I'm tired of forgetting to apply this patch. cmake can pick up a system ccache in a way that it is invoking itself. This causes configuration to fail. Since we have no-cache versions of CC and CXX configuration variables, use them as a basis for constructing the ccache version. Signed-off-by: Jay Carlson n...@nop.com --- include/cmake.mk |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/cmake.mk b/include/cmake.mk index 7746321..619ee98 100644 --- a/include/cmake.mk +++ b/include/cmake.mk @@ -24,9 +24,9 @@ else CCACHE:=$(STAGING_DIR_HOST)/bin/ccache endif CMAKE_C_COMPILER:=$(CCACHE) - CMAKE_C_COMPILER_ARG1:=$(filter-out ccache,$(TARGET_CC)) + CMAKE_C_COMPILER_ARG1:=$(filter-out ccache,$(TARGET_CC_NOCACHE)) CMAKE_CXX_COMPILER:=$(CCACHE) - CMAKE_CXX_COMPILER_ARG1:=$(filter-out ccache,$(TARGET_CXX)) + CMAKE_CXX_COMPILER_ARG1:=$(filter-out ccache,$(TARGET_CXX_NOCACHE)) endif define Build/Configure/Default -- 1.7.9.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] ar71xx: sysupgrade for My Net Wi-Fi Range Extender
This patch enables the convenient sysupgrade feature for
WD's Wi-Fi Range Extender.
The procedure is pretty much SOP. However, there is one
small trick to it: The customized u-boot loader verifies
the image's CRC32 against a reference each time the
device boots. Now, In case of a jffs2-root filesystem
the reference checksum would have to be updated every
time something on the fs changes... Obviously, this
wouldn't be very practial.
Luckily, the bootloader check can be defeated by modifying
the TRX header after the flash.
Signed-off-by: Christian Lamparter chunk...@googlemail.com
---
It seems the wrt160nl suffers from a similar issue. At least
there's an open ticket #8960 https://dev.openwrt.org/ticket/8960.
As far as I can tell, the current sysupgrade code already tries
to fix the TRX header (even on my Archer C7?!) but it fails:
Writing from stdin to firmware ...
Appending jffs2 data from /tmp/sysupgrade.tgz to firmware...
TRX header not found Error fixing up TRX header.
This is because the current sysupgrade code doesn't know that
the TRX header has a offset (32 bytes from the beginning).
---
.../ar71xx/base-files/lib/upgrade/mynet-rext.sh| 26 ++
.../ar71xx/base-files/lib/upgrade/platform.sh | 6 +
target/linux/ar71xx/image/Makefile | 3 +++
3 files changed, 35 insertions(+)
create mode 100644 target/linux/ar71xx/base-files/lib/upgrade/mynet-rext.sh
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/mynet-rext.sh
b/target/linux/ar71xx/base-files/lib/upgrade/mynet-rext.sh
new file mode 100644
index 000..ea4eddd
--- /dev/null
+++ b/target/linux/ar71xx/base-files/lib/upgrade/mynet-rext.sh
@@ -0,0 +1,26 @@
+#!/bin/sh
+
+. /lib/functions.sh
+. /lib/ar71xx.sh
+
+get_image_magic() {
+ local mtddev=$1
+ dd bs=8 count=1 skip=0 if=$mtddev 2/dev/null | hexdump -v -n 8 -e '1/1
%02x'
+}
+
+mynet_rext_check_image() {
+ local magic=$(get_magic_long $1)
+ local fw_magic=$(get_magic_long `find_mtd_part \firmware\`)
+
+ [ $fw_magic != $magic ] {
+ echo Invalid image, ID mismatch, got:$magic, but
need:$fw_magic
+ return 1
+ }
+
+ return 0;
+}
+
+platform_do_upgrade_mynet_rext() {
+ default_do_upgrade $ARGV
+ mtd -o 32 fixtrx firmware
+}
diff --git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
index ae04a8c..7932e76 100755
--- a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
@@ -169,6 +169,9 @@ platform_check_image() {
return 0;
;;
+ mynet-rext)
+ mynet_rext_check_image $1 return 0
+ ;;
mr600 | \
mr600v2 | \
om2p | \
@@ -318,6 +321,9 @@ platform_do_upgrade() {
tew-673gru)
platform_do_upgrade_dir825b $ARGV
;;
+ mynet-rext)
+ platform_do_upgrade_mynet_rext $ARGV
+ ;;
mr600 | \
mr600v2 | \
om2p | \
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 897aab9..ac9d7ed 100644
--- a/target/linux/ar71xx/image/Makefile
+++ b/target/linux/ar71xx/image/Makefile
@@ -683,6 +683,9 @@ Image/Build/CyberTANLZMA/buildkernel=$(call
MkuImageLzma,$(2),$(3) $(4))
define Image/Build/CyberTANLZMA
$(STAGING_DIR_HOST)/bin/trx -o $(KDIR)/image.tmp -f
$(KDIR_TMP)/vmlinux-$(2).uImage \
-x 32 -a 0x1 -x -32 -f $(KDIR)/root.$(1)
+ -$(STAGING_DIR_HOST)/bin/addpattern -B $(2) -v v$(5) \
+ -i $(KDIR)/image.tmp \
+ -o $(call sysupname,$(1),$(2))
-$(STAGING_DIR_HOST)/bin/addpattern -B $(2) -v v$(5) -g \
-i $(KDIR)/image.tmp \
-o $(call factoryname,$(1),$(2))
--
1.8.4.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/2] ar71xx: Use KEY_RESTART key code for the reset button on WD My Net N600 boards
Signed-off-by: Christian Lamparter chunk...@googlemail.com
---
target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n600.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n600.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n600.c
index f87fbf8..476cff8 100644
--- a/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n600.c
+++ b/target/linux/ar71xx/files/arch/mips/ath79/mach-mynet-n600.c
@@ -100,7 +100,7 @@ static struct gpio_keys_button mynet_n600_gpio_keys[]
__initdata = {
{
.desc = Reset button,
.type = EV_KEY,
- .code = KEY_WPS_BUTTON,
+ .code = KEY_RESTART,
.debounce_interval = MYNET_N600_KEYS_DEBOUNCE_INTERVAL,
.gpio = MYNET_N600_GPIO_BTN_RESET,
.active_low = 1,
--
1.8.4.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [OpenWRT-Devel][PATCH] add openvswitch 2.0.0 package
This is a patch for the most recent stable build of OpenvSwitch (2.0.0). It supports kernels 2.6.32 - 3.10.x It was taken and updated from Julius Shulz-Zander's work: https://github.com/schuza/openvswitch Signed-off-by: Peter Holland phollan...@gmail.com --- diff --git a/net/openvswitch/Makefile b/net/openvswitch/Makefile new file mode 100644 --- /dev/null +++ b/net/openvswitch/Makefile @@ -0,0 +1,178 @@ +# +# Copyright (C) 2013 Julius Schulz-Zander +# Copyright (C) 2013 Peter Holland +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id: Makefile $ + +include $(TOPDIR)/rules.mk + +PKG_NAME:=openvswitch + +PKG_RELEASE:=1 +PKG_VERSION:=2.0.0 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://openvswitch.org/releases/ +PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk +include $(INCLUDE_DIR)/kernel.mk + +PKG_FIXUP=libtool + +define Package/openvswitch/Default + SECTION:=net + SUBMENU:=OpenvSwitch + CATEGORY:=Network + URL:=http://www.openvswitchswitch.org/ + DEPENDS:=+libopenssl +librt +libpcap +endef + +define Package/openvswitch/Default/description + Open vSwitch is a production quality, multilayer, software-based, Ethernet + virtual switch. It is designed to enable massive network automation through + programmatic extension, while still supporting standard management interfaces + and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In + addition, it is designed to support distribution across multiple physical + servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus + 1000V. +endef + +define Package/openvswitch-common + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+libpcap +libopenssl +librt +kmod-openvswitch +endef + +define Package/openvswitch-common/description + openvswitch-common provides components required by both openvswitch-switch and + openvswitch-controller. +endef + +define Package/openvswitch-ipsec + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-ipsec/description + The ovs-monitor-ipsec script provides support for encrypting GRE tunnels with + IPsec. +endef + +define Package/openvswitch-controller + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-controller/description + The Open vSwitch controller enables OpenFlow switches that connect to it to + act as MAC-learning Ethernet switches. +endef + +define Package/openvswitch-switch + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-switch/description + openvswitch-switch provides the userspace components and utilities for the + Open vSwitch kernel-based switch. +endef + +define KernelPackage/openvswitch + SECTION:=kernel + CATEGORY:=Kernel modules + SUBMENU:=Network Support + TITLE:=Open Flow Data Path Drivers + KCONFIG:=CONFIG_BRIDGE + DEPENDS:=+kmod-stp +kmod-ipv6 +kmod-gre +kmod-lib-crc32c + FILES:= \ +$(PKG_BUILD_DIR)/datapath/linux/openvswitch.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,40,openvswitch) +endef + +define KernelPackage/openvswitch/description + This package contains the Open vSwitch kernel moodule and bridge compat + module. Furthermore, it supports OpenFlow. +endef + +CONFIGURE_ARGS += --with-linux=$(LINUX_DIR) --with-rundir=/var/run + +define Build/Configure + (cd $(PKG_BUILD_DIR); \ + autoreconf -v --install --force || exit 1 \ + ); + $(call Build/Configure/Default,$(CONFIGURE_ARGS)) +endef + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) \ + $(TARGET_CONFIGURE_OPTS) \ + CFLAGS=-I$(PKG_BUILD_DIR)/lib $(TARGET_CFLAGS) -std=gnu99 \ + LDFLAGS=-L$(PKG_BUILD_DIR)/lib $(TARGET_LDFLAGS) \ + LDFLAGS_MODULES=$(TARGET_LDFLAGS) -L$(PKG_BUILD_DIR)/lib \ + STAGING_DIR=$(STAGING_DIR) \ + DESTDIR=$(PKG_INSTALL_DIR)/usr \ + CROSS_COMPILE=$(TARGET_CROSS) \ + ARCH=$(LINUX_KARCH) \ + PATH=$(TARGET_PATH) \ + KCC=$(KERNEL_CC) +endef + +define Package/openvswitch-ipsec/install + $(INSTALL_DIR) $(1)/usr/sbin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/debian/ovs-monitor-ipsec $(1)/usr/sbin/ +endef + +define Package/openvswitch-common/install + $(INSTALL_DIR) $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-appctl $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-benchmark $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-ofctl $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-pki $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/ovsdb/ovsdb-client $(1)/usr/bin/ + $(INSTALL_DIR) $(1)/usr/sbin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/bugtool/ovs-bugtool $(1)/usr/sbin/ +endef + +define Package/openvswitch-controller/install + $(INSTALL_DIR)
Re: [OpenWrt-Devel] [OpenWRT-Devel][PATCH] add openvswitch 2.0.0 package
Hi. Comments inline. This is a patch for the most recent stable build of OpenvSwitch (2.0.0). It supports kernels 2.6.32 - 3.10.x It was taken and updated from Julius Shulz-Zander's work: https://github.com/schuza/openvswitch Signed-off-by: Peter Holland phollan...@gmail.com --- diff --git a/net/openvswitch/Makefile b/net/openvswitch/Makefile new file mode 100644 --- /dev/null +++ b/net/openvswitch/Makefile @@ -0,0 +1,178 @@ +# +# Copyright (C) 2013 Julius Schulz-Zander +# Copyright (C) 2013 Peter Holland +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id: Makefile $ + +include $(TOPDIR)/rules.mk + +PKG_NAME:=openvswitch + +PKG_RELEASE:=1 +PKG_VERSION:=2.0.0 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://openvswitch.org/releases/ +PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk +include $(INCLUDE_DIR)/kernel.mk + +PKG_FIXUP=libtool + +define Package/openvswitch/Default + SECTION:=net + SUBMENU:=OpenvSwitch + CATEGORY:=Network + URL:=http://www.openvswitchswitch.org/ + DEPENDS:=+libopenssl +librt +libpcap +endef + +define Package/openvswitch/Default/description + Open vSwitch is a production quality, multilayer, software-based, Ethernet + virtual switch. It is designed to enable massive network automation through + programmatic extension, while still supporting standard management interfaces + and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In + addition, it is designed to support distribution across multiple physical + servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus + 1000V. +endef + +define Package/openvswitch-common + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+libpcap +libopenssl +librt +kmod-openvswitch +endef + +define Package/openvswitch-common/description + openvswitch-common provides components required by both openvswitch-switch and + openvswitch-controller. +endef + +define Package/openvswitch-ipsec + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-ipsec/description + The ovs-monitor-ipsec script provides support for encrypting GRE tunnels with + IPsec. +endef + +define Package/openvswitch-controller + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-controller/description + The Open vSwitch controller enables OpenFlow switches that connect to it to + act as MAC-learning Ethernet switches. +endef + +define Package/openvswitch-switch + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-switch/description + openvswitch-switch provides the userspace components and utilities for the + Open vSwitch kernel-based switch. +endef + +define KernelPackage/openvswitch + SECTION:=kernel + CATEGORY:=Kernel modules + SUBMENU:=Network Support + TITLE:=Open Flow Data Path Drivers + KCONFIG:=CONFIG_BRIDGE + DEPENDS:=+kmod-stp +kmod-ipv6 +kmod-gre +kmod-lib-crc32c + FILES:= \ +$(PKG_BUILD_DIR)/datapath/linux/openvswitch.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,40,openvswitch) +endef + +define KernelPackage/openvswitch/description + This package contains the Open vSwitch kernel moodule and bridge compat + module. Furthermore, it supports OpenFlow. +endef + +CONFIGURE_ARGS += --with-linux=$(LINUX_DIR) --with-rundir=/var/run + +define Build/Configure + (cd $(PKG_BUILD_DIR); \ + autoreconf -v --install --force || exit 1 \ + ); + $(call Build/Configure/Default,$(CONFIGURE_ARGS)) +endef That section should be remeoved, manual autoreconf invocations will lead to problems on various build environments. Instead use PKG_FIXUP:=autoreconf . + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) \ + $(TARGET_CONFIGURE_OPTS) \ + CFLAGS=-I$(PKG_BUILD_DIR)/lib $(TARGET_CFLAGS) -std=gnu99 \ + LDFLAGS=-L$(PKG_BUILD_DIR)/lib $(TARGET_LDFLAGS) \ + LDFLAGS_MODULES=$(TARGET_LDFLAGS) -L$(PKG_BUILD_DIR)/lib \ + STAGING_DIR=$(STAGING_DIR) \ + DESTDIR=$(PKG_INSTALL_DIR)/usr \ + CROSS_COMPILE=$(TARGET_CROSS) \ + ARCH=$(LINUX_KARCH) \ + PATH=$(TARGET_PATH) \ + KCC=$(KERNEL_CC) +endef Instead of overriding the entire Build/Compile rule it is better to extend MAKE_VARS for the additional vars needed. + +define Package/openvswitch-ipsec/install + $(INSTALL_DIR) $(1)/usr/sbin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/debian/ovs-monitor-ipsec $(1)/usr/sbin/ +endef + +define Package/openvswitch-common/install + $(INSTALL_DIR) $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-appctl $(1)/usr/bin/ +
Re: [OpenWrt-Devel] [OpenWRT-Devel][PATCH] add openvswitch 2.0.0 package
when you say 'this should not be done', can you give a pointer to 'what should be done instead'? On Fri, Nov 8, 2013 at 3:58 PM, Pete Holland phollan...@gmail.com wrote: thanks for the suggestions... some of the questions (about sleeps, and what I presume is the postinst step) I don't immediately have answers to as I sourced the original patch from another developer, and, well it works... but I will figure them out and resubmit a patch. On Fri, Nov 8, 2013 at 3:50 PM, Jo-Philipp Wich j...@openwrt.org wrote: Hi. Comments inline. This is a patch for the most recent stable build of OpenvSwitch (2.0.0). It supports kernels 2.6.32 - 3.10.x It was taken and updated from Julius Shulz-Zander's work: https://github.com/schuza/openvswitch Signed-off-by: Peter Holland phollan...@gmail.com --- diff --git a/net/openvswitch/Makefile b/net/openvswitch/Makefile new file mode 100644 --- /dev/null +++ b/net/openvswitch/Makefile @@ -0,0 +1,178 @@ +# +# Copyright (C) 2013 Julius Schulz-Zander +# Copyright (C) 2013 Peter Holland +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id: Makefile $ + +include $(TOPDIR)/rules.mk + +PKG_NAME:=openvswitch + +PKG_RELEASE:=1 +PKG_VERSION:=2.0.0 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://openvswitch.org/releases/ +PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk +include $(INCLUDE_DIR)/kernel.mk + +PKG_FIXUP=libtool + +define Package/openvswitch/Default + SECTION:=net + SUBMENU:=OpenvSwitch + CATEGORY:=Network + URL:=http://www.openvswitchswitch.org/ + DEPENDS:=+libopenssl +librt +libpcap +endef + +define Package/openvswitch/Default/description + Open vSwitch is a production quality, multilayer, software-based, Ethernet + virtual switch. It is designed to enable massive network automation through + programmatic extension, while still supporting standard management interfaces + and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In + addition, it is designed to support distribution across multiple physical + servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus + 1000V. +endef + +define Package/openvswitch-common + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+libpcap +libopenssl +librt +kmod-openvswitch +endef + +define Package/openvswitch-common/description + openvswitch-common provides components required by both openvswitch-switch and + openvswitch-controller. +endef + +define Package/openvswitch-ipsec + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-ipsec/description + The ovs-monitor-ipsec script provides support for encrypting GRE tunnels with + IPsec. +endef + +define Package/openvswitch-controller + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-controller/description + The Open vSwitch controller enables OpenFlow switches that connect to it to + act as MAC-learning Ethernet switches. +endef + +define Package/openvswitch-switch + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-switch/description + openvswitch-switch provides the userspace components and utilities for the + Open vSwitch kernel-based switch. +endef + +define KernelPackage/openvswitch + SECTION:=kernel + CATEGORY:=Kernel modules + SUBMENU:=Network Support + TITLE:=Open Flow Data Path Drivers + KCONFIG:=CONFIG_BRIDGE + DEPENDS:=+kmod-stp +kmod-ipv6 +kmod-gre +kmod-lib-crc32c + FILES:= \ + $(PKG_BUILD_DIR)/datapath/linux/openvswitch.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,40,openvswitch) +endef + +define KernelPackage/openvswitch/description + This package contains the Open vSwitch kernel moodule and bridge compat + module. Furthermore, it supports OpenFlow. +endef + +CONFIGURE_ARGS += --with-linux=$(LINUX_DIR) --with-rundir=/var/run + +define Build/Configure + (cd $(PKG_BUILD_DIR); \ + autoreconf -v --install --force || exit 1 \ + ); + $(call Build/Configure/Default,$(CONFIGURE_ARGS)) +endef That section should be remeoved, manual autoreconf invocations will lead to problems on various build environments. Instead use PKG_FIXUP:=autoreconf . + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) \ + $(TARGET_CONFIGURE_OPTS) \ + CFLAGS=-I$(PKG_BUILD_DIR)/lib $(TARGET_CFLAGS) -std=gnu99 \ + LDFLAGS=-L$(PKG_BUILD_DIR)/lib $(TARGET_LDFLAGS) \ +
Re: [OpenWrt-Devel] [OpenWRT-Devel][PATCH] add openvswitch 2.0.0 package
thanks for the suggestions... some of the questions (about sleeps, and what I presume is the postinst step) I don't immediately have answers to as I sourced the original patch from another developer, and, well it works... but I will figure them out and resubmit a patch. On Fri, Nov 8, 2013 at 3:50 PM, Jo-Philipp Wich j...@openwrt.org wrote: Hi. Comments inline. This is a patch for the most recent stable build of OpenvSwitch (2.0.0). It supports kernels 2.6.32 - 3.10.x It was taken and updated from Julius Shulz-Zander's work: https://github.com/schuza/openvswitch Signed-off-by: Peter Holland phollan...@gmail.com --- diff --git a/net/openvswitch/Makefile b/net/openvswitch/Makefile new file mode 100644 --- /dev/null +++ b/net/openvswitch/Makefile @@ -0,0 +1,178 @@ +# +# Copyright (C) 2013 Julius Schulz-Zander +# Copyright (C) 2013 Peter Holland +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id: Makefile $ + +include $(TOPDIR)/rules.mk + +PKG_NAME:=openvswitch + +PKG_RELEASE:=1 +PKG_VERSION:=2.0.0 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://openvswitch.org/releases/ +PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk +include $(INCLUDE_DIR)/kernel.mk + +PKG_FIXUP=libtool + +define Package/openvswitch/Default + SECTION:=net + SUBMENU:=OpenvSwitch + CATEGORY:=Network + URL:=http://www.openvswitchswitch.org/ + DEPENDS:=+libopenssl +librt +libpcap +endef + +define Package/openvswitch/Default/description + Open vSwitch is a production quality, multilayer, software-based, Ethernet + virtual switch. It is designed to enable massive network automation through + programmatic extension, while still supporting standard management interfaces + and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In + addition, it is designed to support distribution across multiple physical + servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus + 1000V. +endef + +define Package/openvswitch-common + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+libpcap +libopenssl +librt +kmod-openvswitch +endef + +define Package/openvswitch-common/description + openvswitch-common provides components required by both openvswitch-switch and + openvswitch-controller. +endef + +define Package/openvswitch-ipsec + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-ipsec/description + The ovs-monitor-ipsec script provides support for encrypting GRE tunnels with + IPsec. +endef + +define Package/openvswitch-controller + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-controller/description + The Open vSwitch controller enables OpenFlow switches that connect to it to + act as MAC-learning Ethernet switches. +endef + +define Package/openvswitch-switch + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-switch/description + openvswitch-switch provides the userspace components and utilities for the + Open vSwitch kernel-based switch. +endef + +define KernelPackage/openvswitch + SECTION:=kernel + CATEGORY:=Kernel modules + SUBMENU:=Network Support + TITLE:=Open Flow Data Path Drivers + KCONFIG:=CONFIG_BRIDGE + DEPENDS:=+kmod-stp +kmod-ipv6 +kmod-gre +kmod-lib-crc32c + FILES:= \ +$(PKG_BUILD_DIR)/datapath/linux/openvswitch.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,40,openvswitch) +endef + +define KernelPackage/openvswitch/description + This package contains the Open vSwitch kernel moodule and bridge compat + module. Furthermore, it supports OpenFlow. +endef + +CONFIGURE_ARGS += --with-linux=$(LINUX_DIR) --with-rundir=/var/run + +define Build/Configure + (cd $(PKG_BUILD_DIR); \ + autoreconf -v --install --force || exit 1 \ + ); + $(call Build/Configure/Default,$(CONFIGURE_ARGS)) +endef That section should be remeoved, manual autoreconf invocations will lead to problems on various build environments. Instead use PKG_FIXUP:=autoreconf . + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) \ + $(TARGET_CONFIGURE_OPTS) \ + CFLAGS=-I$(PKG_BUILD_DIR)/lib $(TARGET_CFLAGS) -std=gnu99 \ + LDFLAGS=-L$(PKG_BUILD_DIR)/lib $(TARGET_LDFLAGS) \ + LDFLAGS_MODULES=$(TARGET_LDFLAGS) -L$(PKG_BUILD_DIR)/lib \ + STAGING_DIR=$(STAGING_DIR) \ + DESTDIR=$(PKG_INSTALL_DIR)/usr \ + CROSS_COMPILE=$(TARGET_CROSS) \ +
Re: [OpenWrt-Devel] [ath9k-devel] ath9k: Deaf QCA9558 when setting rxchainmask
Hi Sven, I've asked nbd about this some time ago. It doesn't work if you have gaps in the chain mask! Try chain mask 3 (110) and it should work with 2x2. Regards, -Julius On 06.11.2013, at 16:04, Sven Eckelmann s...@open-mesh.com wrote: Hi, I've needed to test some problems with a QCA9558 Rev 0 based 3x3 2.4G device. During these tests I've wanted to try different antenna configurations to reduce the complexity of the problem. This was done by setting the rxchainmask/txchainsmask to settings like 1, 5 and 7. Unfortunatelly, the setting 5 (antenna 0 and 1) turned the device completely deaf. Here an overview of the settings (excerpt) chainmask | ant 0 | ant 1 | ant 2 | Status 1 | 1 | 0 | 0 | works 5 | 1 | 0 | 1 | deaf 7 | 1 | 1 | 1 | works The antenna setting is used in ath9k at different places but trigger seems to be the AR_PHY_RX_CHAINMASK register write in ar9003_phy.c in the function ar9003_hw_set_chain_masks. Forcing it to 7 instead of the requested 5 avoids this deaf state (but makes the rx chainmask setting useless). Of course, this is not a valid workaround and quite unexpected. The test platform was a current trunk OpenWrt build together with compat- wireless 2013-02-22, compat-wireless 2013-06-27 and backports 2013-10-31. The settings were configured using the txantenna and rxantenna of the OpenWrt wireless config system. Both were always set to the same values during the tests. The deaf state was identified using 1x1 and 2x2 clients which could receive the beacons of the device. The QCA9558 device was then unable to receive the probe request from the clients or any other traffic on the air. This was also checked by a monitor (flags: control) interface on the same phy. Maybe someone knows whether this is a known problem with this SoC or what information can be gathered to debug this problem further. Kind regards, Sven ___ ath9k-devel mailing list ath9k-de...@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [ath9k-devel] ath9k: Deaf QCA9558 when setting rxchainmask
Hm, is the 0x5 chainmask triggering the ALT_CHAIN logic? What are you trying to do? Control the receive antenna config, or the transmit antenna config? -a On 8 November 2013 16:32, Julius Schulz-Zander jul...@net.t-labs.tu-berlin.de wrote: Hi Sven, I've asked nbd about this some time ago. It doesn't work if you have gaps in the chain mask! Try chain mask 3 (110) and it should work with 2x2. Regards, -Julius On 06.11.2013, at 16:04, Sven Eckelmann s...@open-mesh.com wrote: Hi, I've needed to test some problems with a QCA9558 Rev 0 based 3x3 2.4G device. During these tests I've wanted to try different antenna configurations to reduce the complexity of the problem. This was done by setting the rxchainmask/txchainsmask to settings like 1, 5 and 7. Unfortunatelly, the setting 5 (antenna 0 and 1) turned the device completely deaf. Here an overview of the settings (excerpt) chainmask | ant 0 | ant 1 | ant 2 | Status 1 | 1 | 0 | 0 | works 5 | 1 | 0 | 1 | deaf 7 | 1 | 1 | 1 | works The antenna setting is used in ath9k at different places but trigger seems to be the AR_PHY_RX_CHAINMASK register write in ar9003_phy.c in the function ar9003_hw_set_chain_masks. Forcing it to 7 instead of the requested 5 avoids this deaf state (but makes the rx chainmask setting useless). Of course, this is not a valid workaround and quite unexpected. The test platform was a current trunk OpenWrt build together with compat- wireless 2013-02-22, compat-wireless 2013-06-27 and backports 2013-10-31. The settings were configured using the txantenna and rxantenna of the OpenWrt wireless config system. Both were always set to the same values during the tests. The deaf state was identified using 1x1 and 2x2 clients which could receive the beacons of the device. The QCA9558 device was then unable to receive the probe request from the clients or any other traffic on the air. This was also checked by a monitor (flags: control) interface on the same phy. Maybe someone knows whether this is a known problem with this SoC or what information can be gathered to debug this problem further. Kind regards, Sven ___ ath9k-devel mailing list ath9k-de...@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-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
[OpenWrt-Devel] [PATCH] [packages] bluelog: update PKG_SOURCE_URL with new base path
Update bluelog PKG_SOURCE_URL to ftp://ftp.digifail.com/software/bluelog from ftp://ftp.digifail.com/downloads/software/bluelog Signed-off-by: Sandy McArthur Jr sa...@mcarthur.org --- diff --git a/utils/bluelog/Makefile b/utils/bluelog/Makefile index ac9b150..e40290d 100644 --- a/utils/bluelog/Makefile +++ b/utils/bluelog/Makefile @@ -12,7 +12,7 @@ PKG_VERSION:=1.1.0 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz -PKG_SOURCE_URL:=ftp://ftp.digifail.com/downloads/software/bluelog +PKG_SOURCE_URL:=ftp://ftp.digifail.com/software/bluelog PKG_MD5SUM:=a5327d64731cd45debb57ab1edbe6e43 PKG_INSTALL:=1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [packages] debootstrap: version bump to 1.0.55
Updates PKG_VERSION and PKG_MD5SUM to version 1.0.55 as that is actually available at http://ftp.debian.org/debian/pool/main/d/debootstrap/ This is part of my first attempt to build an OpenWrt image. I don't know the implications of this change beyond allowing my `make download` to continue. Signed-off-by: Sandy McArthur Jr sa...@mcarthur.org --- diff --git a/admin/debootstrap/Makefile b/admin/debootstrap/Makefile index e8e9472..73e15ef 100644 --- a/admin/debootstrap/Makefile +++ b/admin/debootstrap/Makefile @@ -9,12 +9,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=debootstrap -PKG_VERSION:=1.0.48 +PKG_VERSION:=1.0.55 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-udeb_$(PKG_VERSION)_all.udeb PKG_SOURCE_URL:=http://ftp.debian.org/debian/pool/main/d/debootstrap -PKG_MD5SUM:=fae3ba2258e41e17bcb77bbe84d26b2e +PKG_MD5SUM:=f01432f4d7c193ac7a868416ace41bad UNPACK_CMD=ar -p $(DL_DIR)/$(PKG_SOURCE) data.tar.xz | xzcat | tar -C $(1) -xf - ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWRT-Devel][PATCH] add openvswitch 2.0.0 package
nevermind... I figured it out. new patch addressing your issues is forthcoming. On Fri, Nov 8, 2013 at 3:59 PM, Pete Holland phollan...@gmail.com wrote: when you say 'this should not be done', can you give a pointer to 'what should be done instead'? On Fri, Nov 8, 2013 at 3:58 PM, Pete Holland phollan...@gmail.com wrote: thanks for the suggestions... some of the questions (about sleeps, and what I presume is the postinst step) I don't immediately have answers to as I sourced the original patch from another developer, and, well it works... but I will figure them out and resubmit a patch. On Fri, Nov 8, 2013 at 3:50 PM, Jo-Philipp Wich j...@openwrt.org wrote: Hi. Comments inline. This is a patch for the most recent stable build of OpenvSwitch (2.0.0). It supports kernels 2.6.32 - 3.10.x It was taken and updated from Julius Shulz-Zander's work: https://github.com/schuza/openvswitch Signed-off-by: Peter Holland phollan...@gmail.com --- diff --git a/net/openvswitch/Makefile b/net/openvswitch/Makefile new file mode 100644 --- /dev/null +++ b/net/openvswitch/Makefile @@ -0,0 +1,178 @@ +# +# Copyright (C) 2013 Julius Schulz-Zander +# Copyright (C) 2013 Peter Holland +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id: Makefile $ + +include $(TOPDIR)/rules.mk + +PKG_NAME:=openvswitch + +PKG_RELEASE:=1 +PKG_VERSION:=2.0.0 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://openvswitch.org/releases/ +PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk +include $(INCLUDE_DIR)/kernel.mk + +PKG_FIXUP=libtool + +define Package/openvswitch/Default + SECTION:=net + SUBMENU:=OpenvSwitch + CATEGORY:=Network + URL:=http://www.openvswitchswitch.org/ + DEPENDS:=+libopenssl +librt +libpcap +endef + +define Package/openvswitch/Default/description + Open vSwitch is a production quality, multilayer, software-based, Ethernet + virtual switch. It is designed to enable massive network automation through + programmatic extension, while still supporting standard management interfaces + and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In + addition, it is designed to support distribution across multiple physical + servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus + 1000V. +endef + +define Package/openvswitch-common + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+libpcap +libopenssl +librt +kmod-openvswitch +endef + +define Package/openvswitch-common/description + openvswitch-common provides components required by both openvswitch-switch and + openvswitch-controller. +endef + +define Package/openvswitch-ipsec + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-ipsec/description + The ovs-monitor-ipsec script provides support for encrypting GRE tunnels with + IPsec. +endef + +define Package/openvswitch-controller + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-controller/description + The Open vSwitch controller enables OpenFlow switches that connect to it to + act as MAC-learning Ethernet switches. +endef + +define Package/openvswitch-switch + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-switch/description + openvswitch-switch provides the userspace components and utilities for the + Open vSwitch kernel-based switch. +endef + +define KernelPackage/openvswitch + SECTION:=kernel + CATEGORY:=Kernel modules + SUBMENU:=Network Support + TITLE:=Open Flow Data Path Drivers + KCONFIG:=CONFIG_BRIDGE + DEPENDS:=+kmod-stp +kmod-ipv6 +kmod-gre +kmod-lib-crc32c + FILES:= \ + $(PKG_BUILD_DIR)/datapath/linux/openvswitch.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,40,openvswitch) +endef + +define KernelPackage/openvswitch/description + This package contains the Open vSwitch kernel moodule and bridge compat + module. Furthermore, it supports OpenFlow. +endef + +CONFIGURE_ARGS += --with-linux=$(LINUX_DIR) --with-rundir=/var/run + +define Build/Configure + (cd $(PKG_BUILD_DIR); \ + autoreconf -v --install --force || exit 1 \ + ); + $(call Build/Configure/Default,$(CONFIGURE_ARGS)) +endef That section should be remeoved, manual autoreconf invocations will lead to problems on various build environments. Instead use PKG_FIXUP:=autoreconf . + +define Build/Compile + $(MAKE) -C $(PKG_BUILD_DIR) \ +
Re: [OpenWrt-Devel] [OpenWRT-Devel][PATCH] add openvswitch 2.0.0 package
This is a patch for the most recent stable build of OpenvSwitch (2.0.0). It supports kernels 2.6.32 - 3.10.x It was taken and updated from Julius Shulz-Zander's work: https://github.com/schuza/openvswitch Signed-off-by: Peter Holland phollan...@gmail.com --- diff --git a/net/openvswitch/Makefile b/net/openvswitch/Makefile new file mode 100644 --- /dev/null +++ b/net/openvswitch/Makefile @@ -0,0 +1,152 @@ +# +# Copyright (C) 2013 Julius Schulz-Zander +# Copyright (C) 2013 Peter Holland +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# +# $Id: Makefile $ + +include $(TOPDIR)/rules.mk + +PKG_NAME:=openvswitch + +PKG_RELEASE:=1 +PKG_VERSION:=2.0.0 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://openvswitch.org/releases/ +PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION) + +include $(INCLUDE_DIR)/package.mk +include $(INCLUDE_DIR)/kernel.mk + +CONFIGURE_ARGS += --with-linux=$(LINUX_DIR) --with-rundir=/var/run + +PKG_FIXUP:=autoreconf + +define Package/openvswitch/Default + SECTION:=net + SUBMENU:=OpenvSwitch + CATEGORY:=Network + URL:=http://www.openvswitchswitch.org/ + DEPENDS:=+libopenssl +librt +libpcap +endef + +define Package/openvswitch/Default/description + Open vSwitch is a production quality, multilayer, software-based, Ethernet + virtual switch. It is designed to enable massive network automation through + programmatic extension, while still supporting standard management interfaces + and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag). In + addition, it is designed to support distribution across multiple physical + servers similar to VMware's vNetwork distributed vswitch or Cisco's Nexus + 1000V. +endef + +define Package/openvswitch-common + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+libpcap +libopenssl +librt +kmod-openvswitch +endef + +define Package/openvswitch-common/description + openvswitch-common provides components required by both openvswitch-switch and + openvswitch-controller. +endef + +define Package/openvswitch-ipsec + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-ipsec/description + The ovs-monitor-ipsec script provides support for encrypting GRE tunnels with + IPsec. +endef + +define Package/openvswitch-controller + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-controller/description + The Open vSwitch controller enables OpenFlow switches that connect to it to + act as MAC-learning Ethernet switches. +endef + +define Package/openvswitch-switch + $(call Package/openvswitch/Default) + TITLE:=Open Flow Switch Userspace Package + DEPENDS:=+openvswitch-common +endef + +define Package/openvswitch-switch/description + openvswitch-switch provides the userspace components and utilities for the + Open vSwitch kernel-based switch. +endef + +define KernelPackage/openvswitch + SECTION:=kernel + CATEGORY:=Kernel modules + SUBMENU:=Network Support + TITLE:=Open Flow Data Path Drivers + KCONFIG:=CONFIG_BRIDGE + DEPENDS:=+kmod-stp +kmod-ipv6 +kmod-gre +kmod-lib-crc32c + FILES:= \ +$(PKG_BUILD_DIR)/datapath/linux/openvswitch.$(LINUX_KMOD_SUFFIX) + AUTOLOAD:=$(call AutoLoad,40,openvswitch) +endef + +define KernelPackage/openvswitch/description + This package contains the Open vSwitch kernel moodule and bridge compat + module. Furthermore, it supports OpenFlow. +endef + +define Package/openvswitch-ipsec/install + $(INSTALL_DIR) $(1)/usr/sbin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/debian/ovs-monitor-ipsec $(1)/usr/sbin/ +endef + +define Package/openvswitch-common/install + $(INSTALL_DIR) $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-appctl $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-benchmark $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-ofctl $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-pki $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/ovsdb/ovsdb-client $(1)/usr/bin/ + $(INSTALL_DIR) $(1)/usr/sbin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/bugtool/ovs-bugtool $(1)/usr/sbin/ +endef + +define Package/openvswitch-controller/install + $(INSTALL_DIR) $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-controller $(1)/usr/bin/ +endef + +define Package/openvswitch-switch/install + $(INSTALL_DIR) $(1)/sbin $(1)/etc/init.d + $(INSTALL_BIN) ./files/etc/init.d/openvswitch.init $(1)/etc/init.d/openvswitch + + $(INSTALL_DIR) $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-dpctl $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-pcap $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-tcpundump $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/utilities/ovs-vlan-test $(1)/usr/bin/ + $(INSTALL_BIN)
[OpenWrt-Devel] A broadcom driver packaging method
Well, I decided to try and package device specific broadcom drivers together for ARM. I got to the point of them compiling alongside the kernel and creating the kernel_menuconfig section for them, but I don't really understand the OpenWRT packaging system well enough to get them fully integrated into a device image. The idea is basically creating device driver sets rather than trying to build something more universal. This way all the driver dependencies are all together. The package would essentially branch based on the device chosen which I managed to more or less get working in the kernel_menuconfig. Hopefully its somewhat understandable. Is this something that would be workable? https://github.com/Lightsword1942/broadcom-hnd ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
