Re: [OpenWrt-Devel] Fwd: Re: Contact info after Fosdem

2008-03-31 Thread Gregers Petersen
I'll send him an email + I'm putting a box with Zyxel things for you in
the mail today.

Florian Fainelli wrote:
 Might be of interest to talk with this guy in order not to create yet another 
 embedded framework.
 
 
 
 
 Subject:
 Re: Contact info after Fosdem
 From:
 Jelle de Jong [EMAIL PROTECTED]
 Date:
 Sun, 30 Mar 2008 21:06:32 +0200
 To:
 Florian Fainelli [EMAIL PROTECTED]
 
 To:
 Florian Fainelli [EMAIL PROTECTED]
 
 
 Florian Fainelli wrote:
 Hi Jelle,

 You gave me your card after my Fosdem presentation on OpenWrt, so now
 you have my contact informations. I do not remember your question
 about OpenWrt, can you as it again ?
 
 Hi Florian,
 
 Indeed you gave a nice presentation about openWrt. My resulting
 question/comment was:
 
 OpenWrt has a nice system creating device specific kernels and file system.
 
 I am working on the emdebian project, and one problems with mainline
 reposatory is that we can't maintain/create custom kernels for single
 devices.
 
 I was interested to create a more generic way for embedded system
 developers to create and maintain kernels resulting in more open devices.
 
 I am planning to create a new open design based embedded ARM development
 board and probably make kit available. I am planning this in this year.
 I hope to create an open SDK based on existing mainline components.
 
 So maybe we could work together on sustainable kernel creator system,
 guidelines
 
 Kind regards,
 
 Jelle de Jong
 
 
 
 
 
 
 
 
 
 
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

-- 
Gregers Petersen
Anthropology, talk and people-stuff
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] OpenWrt

2008-03-31 Thread Gregers Petersen
Hello Jelle

Florian told me about your questions, and interests.

IF you take a closer look at the OpenWrt buildsystem, to what an extend
does it already cover your needs/focus?

-- 
Gregers Petersen
Anthropology, talk and people-stuff

  ___ __
 |   |.-.-.-.|  |  |  |..|  |_
 |   -   ||  _  |  -__| ||  |  |  ||   _||   _|
 |___||   __|_|__|__||||__|  ||
  |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge) ---
  * 10 oz Vodka   Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Fwd: Re: Contact info after Fosdem

2008-03-31 Thread Oliver Ertl
 Might be of interest to talk with this guy in order not to create yet
 another 
 embedded framework.
It's normal for Opensource projects to reinvent the wheel over and over again. 
And everytime the code gets more crapier.

I really which that Opensource projects would work more together and 
concentrate the efforts on one less and have them with better quality...
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] br2684 routed runnig on AR7

2008-03-31 Thread Juan I . González
Hi All,

In these days I adapted the last patch for br2684 kernel module.

For some ISP it is necesary this implementation.

This is my case in Spain with Telefonica ISP and static IP.

Adapted support for kernel 2.6.24 

Implemented:
-
Kernel
  - target/linux/generic-2.6/patches-2.6.24/601-br2684-routed-support.patch
  - linux-2.6.24.2/include/linux/atmbr2684.h
  - linux-2.6.24.2/net/atm/br2684.c

Package
- package/br2684ctl/patches/101-routed_support.patch
  - br2684ctl-20040226.orig/br2684ctl.c
Scripts
  - package/br2684ctl/files/br2684ctl
  -
  
This changes the br2684 module of kernel 2.6.24, br2864ctl package and
br2684ctl script. With this changes it is posible 

Tested for 7 days with Linksys AG241v2-EU.
  
Configuracion /etc/config/network
-
config atm-bridge
option 'unit''0'
option 'vpi' '8'
option 'vci' '32'
option 'encaps'  'llc'
option 'payload' 'routed'

config 'interface' 'wan'
option 'ifname' 'nas0'
option 'proto' 'static'
option 'ipaddr' 'your ipaddr'
option 'netmask' 'your netmask'
option 'dns' 'your dns'
option 'gateway' 'your gateway'
-

cat /proc/net/atm/br2684  
-
  

[EMAIL PROTECTED]:/tmp# cat /proc/net/atm/br2684
dev nas0: num=1, mac=00:00:00:00:00:00 (auto)
  vcc 0.8.32: encaps=LLC payload=routed, failed copies 0/0
-Signed-off-by: 
Juan I. Gonzalez juan.i.gonzalez at subdown dot net


  


--
PRIVACIDAD:
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o CONFIDENCIAL. Si no es vd. el destinatario
indicado, queda notificado de que la utilización, divulgación y/o copia sin
autorización está prohibida en virtud de la legislación vigente. Si ha
recibido este mensaje por error, le rogamos que nos lo comunique
inmediatamente por esta misma vía y proceda a su destrucción.

PRIVACITY:
This message is intended exclusively for its addressee and may contain
information that is CONFIDENTIAL and protected by professional privilege. If
you are not the intended recipient you are hereby notified that any
dissemination, copy or disclosure of this communication is strictly
prohibited by law. If this message has been received in error, please
immediately notify us via e-mail and delete it.

Powered by Subdown System Network
Index: target/linux/generic-2.6/patches-2.6.24/601-br2684-routed-support.patch
===
--- target/linux/generic-2.6/patches-2.6.24/601-br2684-routed-support.patch	(revision 0)
+++ target/linux/generic-2.6/patches-2.6.24/601-br2684-routed-support.patch	(revision 0)
@@ -0,0 +1,730 @@
+diff -Nur linux-2.6.24.2/include/linux/atmbr2684.h linux-2.6.24.2-copy/include/linux/atmbr2684.h
+--- linux-2.6.24.2/include/linux/atmbr2684.h	2008-02-11 05:51:11.0 +
 linux-2.6.24.2-copy/include/linux/atmbr2684.h	2008-03-27 01:08:42.0 +
+@@ -14,6 +14,9 @@
+ #define BR2684_MEDIA_FDDI	(3)
+ #define BR2684_MEDIA_802_6	(4)	/* 802.6 */
+ 
++	/* used only at device creation:  */
++#define BR2684_FLAG_ROUTED	(116)	/* payload is routed, not bridged */
++
+ /*
+  * Is there FCS inbound on this VC?  This currently isn't supported.
+  */
+@@ -36,15 +39,22 @@
+ #define BR2684_ENCAPS_AUTODETECT (2)	/* Unsuported */
+ 
+ /*
++ * Is this VC bridged or routed?
++ */
++
++#define BR2684_PAYLOAD_ROUTED   (0)
++#define BR2684_PAYLOAD_BRIDGED  (1)
++
++/*
+  * This is for the ATM_NEWBACKENDIF call - these are like socket families:
+  * the first element of the structure is the backend number and the rest
+  * is per-backend specific
+  */
+ struct atm_newif_br2684 {
+-	atm_backend_t	backend_num;	/* ATM_BACKEND_BR2684 */
+-	int		media;		/* BR2684_MEDIA_* */
+-	char		ifname[IFNAMSIZ];
+-	int		mtu;
++	atm_backend_t backend_num;	/* ATM_BACKEND_BR2684 */
++	int media;		/* BR2684_MEDIA_*, flags in upper bits */
++	char ifname[IFNAMSIZ];
++	int mtu;
+ };
+ 
+ /*
+@@ -55,10 +65,10 @@
+ #define BR2684_FIND_BYNUM	(1)
+ #define BR2684_FIND_BYIFNAME	(2)
+ struct br2684_if_spec {
+-	int method;			/* BR2684_FIND_* */
++	int method;		/* BR2684_FIND_* */
+ 	union {
+-		char		ifname[IFNAMSIZ];
+-		int		devnum;
++		char ifname[IFNAMSIZ];
++		int devnum;
+ 	} spec;
+ };
+ 
+@@ -68,16 +78,16 @@
+  * is per-backend specific
+  */
+ struct atm_backend_br2684 {
+-	atm_backend_t	backend_num;	/* ATM_BACKEND_BR2684 */
++	atm_backend_t backend_num;	/* ATM_BACKEND_BR2684 */
+ 	struct br2684_if_spec ifspec;
+-	int	fcs_in;		/* BR2684_FCSIN_* */
+-	int	fcs_out;	/* BR2684_FCSOUT_* */
+-	int	fcs_auto;	/* 1: fcs_{in,out} disabled if no FCS rx'ed */
+-	int	encaps;