[OpenWrt-Devel] Install-Dir of gsl include-files

2010-05-25 Thread Rainer Poisel
Hi,

I wanted to make a suggestion for the package Makefile of the gsl (GNU
Scientific Library). You find a patch attached to this e-Mail.

Applying it (I did not try it!) the include files for the gsl should be
installed into the usr/include/gsl directory (instead of usr/include
directly) of the SDK. This conforms more to the typical install routine
since the include-files themselves include all further gsl_*.h include
files from usr/include/gsl.

Don't hesitate to ask back if there is something unclear.

Thanks for thinking about my suggestion,
  Rainer 

-- 
Dipl.-Ing. (FH) Mag. Rainer Poisel
Institut für IT Sicherheitsforschung
Bereich Technologie

Fachhochschule St. Pölten GmbH
Matthias Corvinus-Straße 15, A-3100 St. Pölten
T: +43/2742/313 228 - 637 
F: +43/2742/313 228 - 219 
E: rpoi...@fhstp.ac.at
I: www.fhstp.ac.at

FN 146616m, LG St. Pölten, DVR 1028669F

Index: feeds/packages/libs/gsl/Makefile
===
--- feeds/packages/libs/gsl/Makefile(revision 21517)
+++ feeds/packages/libs/gsl/Makefile(working copy)
@@ -43,8 +43,8 @@
 endef
 
 define Build/InstallDev
-   $(INSTALL_DIR) $(1)/usr/include $(1)/usr/lib
-   $(CP) $(PKG_INSTALL_DIR)/usr/include/gsl/*.h $(1)/usr/include/
+   $(INSTALL_DIR) $(1)/usr/include/gsl $(1)/usr/lib
+   $(CP) $(PKG_INSTALL_DIR)/usr/include/gsl/*.h $(1)/usr/include/gsl
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libgsl.* $(1)/usr/lib/
$(CP) $(PKG_INSTALL_DIR)/usr/lib/libgslcblas.* $(1)/usr/lib/
 endef
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] mtd / Samsung flash chips

2010-05-25 Thread Matthias Buecher / Germany
Salut Florian,

you took care of ticket #6552 [1] and committed the patch into trunk.
It came out that the patch broke compiling the Orion platform, that was
reported in ticket #7348 [2].
Inside this ticket the reporter of #6552 and I came to a much cleaner
approach.
Would be great if you could have a look at it.

Kind regards
Matthias Maddes Bücher

[1] https://dev.openwrt.org/ticket/6552
[2] https://dev.openwrt.org/ticket/7348

-- 
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] Custom firewall script

2010-05-25 Thread Roberto Riggio

Hi,

before the firewall upgrade I used a very simple firewall.user script
whose only function was to add an interface to a newtwork:

addif mesh xr0 mesh

the mesh zone was defined in /etc/config/firewall as follow

config 'zone' 'z_mesh'
option 'name' 'mesh'
option 'input' 'ACCEPT'
option 'output' 'ACCEPT'
option 'forward' 'REJECT'
option 'masq' '1'

The new firewal does not define the fucntion addif anymore. Which
is the new style to acheive the same result?

Thanks
R.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] mtd / Samsung flash chips

2010-05-25 Thread Florian Fainelli
Hello Matthias,

On Tuesday 25 May 2010 14:20:19 Matthias Buecher / Germany wrote:
 Salut Florian,
 
 you took care of ticket #6552 [1] and committed the patch into trunk.
 It came out that the patch broke compiling the Orion platform, that was
 reported in ticket #7348 [2].
 Inside this ticket the reporter of #6552 and I came to a much cleaner
 approach.
 Would be great if you could have a look at it.

Sure, I will have a look at this, sorry for the patch clashing.

 
 Kind regards
 Matthias Maddes Bücher
 
 [1] https://dev.openwrt.org/ticket/6552
 [2] https://dev.openwrt.org/ticket/7348
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] mtd / Samsung flash chips

2010-05-25 Thread Guillaume LECERF
2010/5/25 Florian Fainelli flor...@openwrt.org:
 Hello Matthias,

 On Tuesday 25 May 2010 14:20:19 Matthias Buecher / Germany wrote:
 Salut Florian,

 you took care of ticket #6552 [1] and committed the patch into trunk.
 It came out that the patch broke compiling the Orion platform, that was
 reported in ticket #7348 [2].
 Inside this ticket the reporter of #6552 and I came to a much cleaner
 approach.
 Would be great if you could have a look at it.

 Sure, I will have a look at this, sorry for the patch clashing.

Hi.

A patch has been recently committed upstream that *may* solve this problem :

http://git.infradead.org/mtd-2.6.git/commitdiff/412da2f6e083eba6e4bd91ff2e78abb4735357a7

 Kind regards
 Matthias Maddes Bücher

 [1] https://dev.openwrt.org/ticket/6552
 [2] https://dev.openwrt.org/ticket/7348
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel




-- 
Guillaume LECERF
GeeXboX developer - www.geexbox.org
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] mtd / Samsung flash chips

2010-05-25 Thread Guillaume LECERF
2010/5/25 Guillaume LECERF glec...@gmail.com:
 A patch has been recently committed upstream that *may* solve this problem :

 http://git.infradead.org/mtd-2.6.git/commitdiff/412da2f6e083eba6e4bd91ff2e78abb4735357a7

Please forget this comment, it was a brainfart.

-- 
Guillaume LECERF
GeeXboX developer - www.geexbox.org
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Custom firewall script

2010-05-25 Thread Jo-Philipp Wich
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Try this:

fw_configure_interface $network add $device

~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkv8CVUACgkQdputYINPTPNZdACePWR9xPBH143jvP9RHGKua3kB
3ukAn1wiTC5WXFA/QNZoYa9r/ZG4VDGg
=kH+5
-END PGP SIGNATURE-
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Matthias Buecher / Germany
Today I checked out how to access the U-Boot variables of my WRT350N v2
(Orion) from Linux.

Installed uboot-envtools and created a fitting /etc/fw_env.config:
# WRT350N v2
# MTD device nameDevice offsetEnv. sizeFlash sector size
/dev/mtd50x0003c0000x20000x1000

I can read all U-Boot env vars, but not change any.
This seems to be a problem of the huge erase site 0x0001 of mtd.
Can I specify a separate erase size for the U-Boot partition?


static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
...
}, {
.name   = u-boot,
.offset = 0x007c,
.size   = 0x0004,
}, {
...
},
};

linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c

OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch

Maddes

-- 
http://www.maddes.net/
Home: Earth / Germany / Ruhr-Area
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Bernhard Loos
There is already a patch for this in openwrt, so it should work (in theory).
Do you use trunk or backfire or something older?

2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Today I checked out how to access the U-Boot variables of my WRT350N v2
 (Orion) from Linux.

 Installed uboot-envtools and created a fitting /etc/fw_env.config:
 # WRT350N v2
 # MTD device name    Device offset    Env. size    Flash sector size
 /dev/mtd5        0x0003c000    0x2000    0x1000

 I can read all U-Boot env vars, but not change any.
 This seems to be a problem of the huge erase site 0x0001 of mtd.
 Can I specify a separate erase size for the U-Boot partition?


 static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
        {
 ...
        }, {
                .name           = u-boot,
                .offset         = 0x007c,
                .size           = 0x0004,
        }, {
 ...
        },
 };

 linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c

 OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch

 Maddes

 --
 http://www.maddes.net/
 Home: Earth / Germany / Ruhr-Area
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Matthias Buecher / Germany
Both, backfire and latest trunk.
Can you hint me where this patch is?

Maddes

On 25.05.2010 21:59, Bernhard Loos wrote:
 There is already a patch for this in openwrt, so it should work (in theory).
 Do you use trunk or backfire or something older?
 
 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Today I checked out how to access the U-Boot variables of my WRT350N v2
 (Orion) from Linux.

 Installed uboot-envtools and created a fitting /etc/fw_env.config:
 # WRT350N v2
 # MTD device nameDevice offsetEnv. sizeFlash sector size
 /dev/mtd50x0003c0000x20000x1000

 I can read all U-Boot env vars, but not change any.
 This seems to be a problem of the huge erase site 0x0001 of mtd.
 Can I specify a separate erase size for the U-Boot partition?


 static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
 ...
}, {
.name   = u-boot,
.offset = 0x007c,
.size   = 0x0004,
}, {
 ...
},
 };

 linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c

 OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch

 Maddes

 --
 http://www.maddes.net/
 Home: Earth / Germany / Ruhr-Area
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Bernhard Loos
https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch

2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Both, backfire and latest trunk.
 Can you hint me where this patch is?

 Maddes

 On 25.05.2010 21:59, Bernhard Loos wrote:
 There is already a patch for this in openwrt, so it should work (in theory).
 Do you use trunk or backfire or something older?

 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Today I checked out how to access the U-Boot variables of my WRT350N v2
 (Orion) from Linux.

 Installed uboot-envtools and created a fitting /etc/fw_env.config:
 # WRT350N v2
 # MTD device name    Device offset    Env. size    Flash sector size
 /dev/mtd5        0x0003c000    0x2000    0x1000

 I can read all U-Boot env vars, but not change any.
 This seems to be a problem of the huge erase site 0x0001 of mtd.
 Can I specify a separate erase size for the U-Boot partition?


 static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
        {
 ...
        }, {
                .name           = u-boot,
                .offset         = 0x007c,
                .size           = 0x0004,
        }, {
 ...
        },
 };

 linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c

 OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch

 Maddes

 --
 http://www.maddes.net/
 Home: Earth / Germany / Ruhr-Area
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Matthias Buecher / Germany
So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see
how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to
0x3dfff gets erased.
The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2
are very important and shouldn't be touched.
Or should this work out of the box with uboot-envtools?

Maddes

On 25.05.2010 23:14, Bernhard Loos wrote:
 https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch
 
 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Both, backfire and latest trunk.
 Can you hint me where this patch is?

 Maddes

 On 25.05.2010 21:59, Bernhard Loos wrote:
 There is already a patch for this in openwrt, so it should work (in theory).
 Do you use trunk or backfire or something older?

 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Today I checked out how to access the U-Boot variables of my WRT350N v2
 (Orion) from Linux.

 Installed uboot-envtools and created a fitting /etc/fw_env.config:
 # WRT350N v2
 # MTD device nameDevice offsetEnv. sizeFlash sector size
 /dev/mtd50x0003c0000x20000x1000

 I can read all U-Boot env vars, but not change any.
 This seems to be a problem of the huge erase site 0x0001 of mtd.
 Can I specify a separate erase size for the U-Boot partition?


 static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
 ...
}, {
.name   = u-boot,
.offset = 0x007c,
.size   = 0x0004,
}, {
 ...
},
 };

 linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c

 OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch

 Maddes

 --
 http://www.maddes.net/
 Home: Earth / Germany / Ruhr-Area
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Bernhard Loos
It should work out of the box with the patch.
It will (should) set the erase size to the right value.

2010/5/26 Matthias Buecher / Germany m...@maddes.net:
 So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see
 how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to
 0x3dfff gets erased.
 The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2
 are very important and shouldn't be touched.
 Or should this work out of the box with uboot-envtools?

 Maddes

 On 25.05.2010 23:14, Bernhard Loos wrote:
 https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch

 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Both, backfire and latest trunk.
 Can you hint me where this patch is?

 Maddes

 On 25.05.2010 21:59, Bernhard Loos wrote:
 There is already a patch for this in openwrt, so it should work (in 
 theory).
 Do you use trunk or backfire or something older?

 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Today I checked out how to access the U-Boot variables of my WRT350N v2
 (Orion) from Linux.

 Installed uboot-envtools and created a fitting /etc/fw_env.config:
 # WRT350N v2
 # MTD device name    Device offset    Env. size    Flash sector size
 /dev/mtd5        0x0003c000    0x2000    0x1000

 I can read all U-Boot env vars, but not change any.
 This seems to be a problem of the huge erase site 0x0001 of mtd.
 Can I specify a separate erase size for the U-Boot partition?


 static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
        {
 ...
        }, {
                .name           = u-boot,
                .offset         = 0x007c,
                .size           = 0x0004,
        }, {
 ...
        },
 };

 linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c

 OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch

 Maddes

 --
 http://www.maddes.net/
 Home: Earth / Germany / Ruhr-Area
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Felix Fietkau
On 2010-05-26 12:02 AM, Matthias Buecher / Germany wrote:
 So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see
 how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to
 0x3dfff gets erased.
 The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2
 are very important and shouldn't be touched.
 Or should this work out of the box with uboot-envtools?
You can't limit the erase size. It's not a partition setting, it's
hardware defined. The chip can only erase in specifically sized blocks
and not arbitrary ranges.

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH] Kernel patch in trunk (version 21251) to support Netgear WNR3500L

2010-05-25 Thread Felix Fietkau
On 2010-05-26 12:10 AM, Per Åstrand wrote:
 Hi!
 
 I've updated the patch for wnr3500l to build against @21567.
 I don't have access to the router for a couple of more days, so it's
 untested so far.
Please remove all #ifdef CONFIG_WNR3500L
It makes the code harder to read and it's not acceptable for upstream.

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] different mtd erase size for a specific partion possible?

2010-05-25 Thread Matthias Buecher / Germany
Tried to set that flag, but can not find the right spot.
Any help?

Maddes

On 26.05.2010 00:08, Bernhard Loos wrote:
 It should work out of the box with the patch.
 It will (should) set the erase size to the right value.
 
 2010/5/26 Matthias Buecher / Germany m...@maddes.net:
 So I can mark the partition with MTD_ERASE_PARTIAL, but I can not see
 how I can limit erase size to 0x1000 so that only mtd offsets 0x3c000 to
 0x3dfff gets erased.
 The last 128 bytes (0x3ff80 - 3) of the mtd partition on WRT350N v2
 are very important and shouldn't be touched.
 Or should this work out of the box with uboot-envtools?

 Maddes

 On 25.05.2010 23:14, Bernhard Loos wrote:
 https://dev.openwrt.org/browser/trunk/target/linux/generic-2.6/patches-2.6.32/222-partial_eraseblock_write.patch

 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Both, backfire and latest trunk.
 Can you hint me where this patch is?

 Maddes

 On 25.05.2010 21:59, Bernhard Loos wrote:
 There is already a patch for this in openwrt, so it should work (in 
 theory).
 Do you use trunk or backfire or something older?

 2010/5/25 Matthias Buecher / Germany m...@maddes.net:
 Today I checked out how to access the U-Boot variables of my WRT350N v2
 (Orion) from Linux.

 Installed uboot-envtools and created a fitting /etc/fw_env.config:
 # WRT350N v2
 # MTD device nameDevice offsetEnv. sizeFlash sector size
 /dev/mtd50x0003c0000x20000x1000

 I can read all U-Boot env vars, but not change any.
 This seems to be a problem of the huge erase site 0x0001 of mtd.
 Can I specify a separate erase size for the U-Boot partition?


 static struct mtd_partition wrt350n_v2_nor_flash_partitions[] = {
{
 ...
}, {
.name   = u-boot,
.offset = 0x007c,
.size   = 0x0004,
}, {
 ...
},
 };

 linux: arch/arm/mach-orion5x/wrt350n-v2-setup.c

 OpenWrt: target/linux/orion/patches/100-openwrt_partition_map.patch

 Maddes

 --
 http://www.maddes.net/
 Home: Earth / Germany / Ruhr-Area
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel

 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel