[OpenWrt-Devel] please commit asap - [packages] tinc: update to 1.0.15

2011-06-25 Thread ZioPRoTo (Saverio Proto)
Hello,

following patch to Makefile updates tinc-vpn to upstream release 1.0.15.

I tested the patch and it compiles ok.

ciao,

Saverio

PS I have some issues with my svn+ssh access, looks like I cant commit
anymore :( Maybe I'm restricted only to olsrd folder ? How can I check
this out without doing stupid test commits on the repository ? thanks


Makefile.diff
Description: Binary data
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Porting questions

2011-06-25 Thread Florian Fainelli
Hi Alberich

On Saturday 25 June 2011 01:08:41 Alberich de megres wrote:
 Hi Mates,
 
 I'm new on this list, and i like to make openwrt working on some of my
 home routers, the one where i'm most interested is cisco e3000. But I
 got some questions of the porting itself.
 (I searched before some info about this routers and its serial/jtag
 connection). I never worked with platforms like mips (only x86 and
 similars).
 
 I saw the cpu is supported by vanilla linux kernel (bcm47xx). In case
 I just incorporate the code to openwrt kernel, or even more simple,
 compile vanilla kernel what happens with the boot loader? how can i
 make it work with the router? I mean does it need to interact with CFE
 env? is there any possibilitied to blow up CFE when testing firmwares
 or CFE is only writable when you try to update it?

The vanilla bcm47xx code only support the old-style: BCM47xx and BCM53xx 
family of System-on-Chip. The new style SoC like BCM4716 and BCM4718 are still 
work in progress both for mainline kernel and for OpenWrt kernels.

 
 I'm a little bit lost whit the start point. Is there some significant
 modification on the openwrt kernel version (code level) that makes it
 different from vanilla?

Since patches for BCM4716 and BCM4718 have been posted to the linux-mips 
mailing-list, it would be easier to just throw them in 
target/linux/brcm47xx/patches-3.0/ and rebuild a kernel with the appropriate 
options.
-- 
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] device renaming in hotplug2?

2011-06-25 Thread Dave Taht
Can hotplug2 do device renaming? I went looking for syntax that was the
equivalent of udev's:

KERNEL==eth*, ATTR{address}==00:52:8b:d5:04:48, NAME=out0

And didn't find it.

iptables has the concept of a pattern match, where
you could specify something like this:

iptables -i out+ -o out+ -j ACCEPT

which could simplify firewall rules creation something considerable, by
pushing device naming directly into the 'firewall zone' concept.


-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH v3 1/1] pciutils: need to specify -lresolv explicitly when using eglibc

2011-06-25 Thread Mirko Vogt

On Fri, 24 Jun 2011 19:02:05 -0700, Philip Prindeville wrote:

eglibc's libc doesn't include libresolv as part of it.

Redux: Need to annotate libbsd dependency as well.

Redux: Include support for glibc as well.

Signed-off-by: Philip Prindeville phil...@redfish-solutions.com


Why did you add 'libbsd' as dependency for pciutils when using 
glibc/eglibc?
I just tried building pciutils within an glibc and eglibc toolchain and 
it compiles fine without getting linked against libbsd.


Regarding '-lresolv' you're right - pciutils needs to get linked 
against libresolv.so (commited in 27281).


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


Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team

2011-06-25 Thread Philip Prindeville
On 3/26/11 7:45 AM, Luca Olivetti wrote:
 Al 26/03/11 12:25, En/na Maarten Bezemer ha escrit:
 On Thu, 2011-03-24 at 17:57 -0500, Layne Edwards wrote:

 I want to contribute, but I don't feel like I'm getting a warm
 welcome.

 I feel the same way. Tried to contribute by fixing/patching things I
 found while using OpenWRT, but none of them are applied (I think) even
 after reminders.
 
 Well, I've been told to sit tight and wait, how's that for a warm welcome?
 
 Bye

Well, now the answer is sit tight and wait while some changes are made to 
improve things, but 2-1/2 months after we had an IRC brainstorming session to 
improve things, I'm not seeing any noticeable change.

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


[OpenWrt-Devel] link layer

2011-06-25 Thread scolfield
Hi all,

CSMA/CA is implemented at hardware level on the interface wireless.
And it is possible to reprogram this interface card? to burn firmware?
I've looked that the mesh module is developing with HWMP. Well,
this protocol, in accordance of the draft, modify the control access
mechanism, right?
Well, my questions, maybe already were answered... but I would like to
confirm.

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


Re: [OpenWrt-Devel] [PATCH v2 1/1] alix2: add config files for bridging

2011-06-25 Thread Florian Fainelli
On Monday 13 June 2011 00:26:07 Philip Prindeville wrote:
 Redux, as it was requested that I not use uci-defaults.
 
 Redux**2, I removed the wifi stuff so it could be auto-generated.
 
 Borrowed from the omap24xx configs.

Applied in r27286, thanks!
-- 
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH 1/1] geos: deprecate uci-defaults files

2011-06-25 Thread Florian Fainelli
On Monday 13 June 2011 02:40:45 Philip Prindeville wrote:
 Use preconfigured files rather than uci-defaults.
 
 Signed-off-by: Philip Prindeville phil...@redfish-solutions.com

Applied in r27287, thanks!
-- 
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] busybox 1.18.5 update patch

2011-06-25 Thread Florian Fainelli
On Sunday 19 June 2011 12:57:20 Peter Wagner wrote:
 Hi,
 
 this patch updates busybox to 1.18.5
 
 /Peter

Applied in r27288, thanks Peter!
-- 
Florian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] [PATCH 1/1] geos: finish removal of etc/uci-defaults

2011-06-25 Thread Philip Prindeville
Patch r27287 was not complete.

etc/uci-defaults/wireless needs to be deleted. Then etc/uci-defaults itself 
needs to be manually deleted (this is somehow not reflected in svn diff even 
though svn status shows the directory as deleted). sigh.

Signed-off-by: Philip Prindeville phil...@redfish-solutions.com
Index: target/linux/x86/geos/base-files/etc/uci-defaults/wireless
===
--- target/linux/x86/geos/base-files/etc/uci-defaults/wireless  (revision 27288)
+++ target/linux/x86/geos/base-files/etc/uci-defaults/wireless  (working copy)
@@ -1,27 +0,0 @@
-#!/bin/sh
-
-[ -f /etc/config/wireless ] || echo package wireless  /etc/config/wireless
-
-uci batch __EOF__
-
-delete wireless.radio0
-delete wireless.@wifi-iface[0]
-
-set wireless.wlan0=wifi-device
-set wireless.wlan0.type=mac80211
-set wireless.wlan0.phy=phy0
-set wireless.wlan0.channel=11
-set wireless.wlan0.hwmode=11g
-set wireless.wlan0.country=US
-
-add wireless wifi-iface
-set wireless.@wifi-iface[-1].device=wlan0
-set wireless.@wifi-iface[-1].network=lan
-set wireless.@wifi-iface[-1].mode=ap
-set wireless.@wifi-iface[-1].ssid=typhoon
-set wireless.@wifi-iface[-1].encryption=psk2+aes
-set wireless.@wifi-iface[-1].key=passphrase
-set wireless.@wifi-iface[-1].hidden=0
-
-commit wireless
-__EOF__
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel