[OpenWrt-Devel] Generic Gpio Support Status
what is the status of the new generic gpio support? In the current trunk build, I am not seeing the /dev/gpio node being built when the settings are enabled at least not on IXP4XX (Avila gw2345). I know this was working in my 2.6.23 builds, but I'm unsure if I've missed a setting in the new 2.6.25.x kernel? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] IPv6 Routing und Tunneling Patch
This Makefile patch adds support for the Privacy Extensions, IP-in-IPv6 tunnel, Multiple Routing Tables and source address based routing in the 2.6 Kernel. Signed-off-by: Alina Friedrichsen [EMAIL PROTECTED] --- Index: package/kernel/modules/network.mk === --- package/kernel/modules/network.mk (Revision 11232) +++ package/kernel/modules/network.mk (Arbeitskopie) @@ -208,7 +208,7 @@ define KernelPackage/iptunnel6 SUBMENU:=$(NETWORK_SUPPORT_MENU) TITLE:=IPv6 tunneling - DEPENDS:= @LINUX_2_6 + DEPENDS:= @LINUX_2_6 +kmod-ipv6 KCONFIG:= \ CONFIG_INET6_TUNNEL FILES:= $(foreach mod,tunnel6, \ @@ -227,7 +227,11 @@ define KernelPackage/ipv6 SUBMENU:=$(NETWORK_SUPPORT_MENU) TITLE:=IPv6 support - KCONFIG:=CONFIG_IPV6 + KCONFIG:= \ + CONFIG_IPV6 \ + CONFIG_IPV6_PRIVACY=y \ + CONFIG_IPV6_MULTIPLE_TABLES=y \ + CONFIG_IPV6_SUBTREES=y FILES:=$(LINUX_DIR)/net/ipv6/ipv6.$(LINUX_KMOD_SUFFIX) AUTOLOAD:=$(call AutoLoad,20,ipv6) endef @@ -264,6 +268,24 @@ $(eval $(call KernelPackage,sit)) +define KernelPackage/ip6-tunnel + SUBMENU:=$(NETWORK_SUPPORT_MENU) + TITLE:=IP-in-IPv6 tunnelling + DEPENDS:= @LINUX_2_6 +kmod-ipv6 +kmod-iptunnel6 + KCONFIG:= CONFIG_IPV6_TUNNEL + FILES:= $(foreach mod,ip6_tunnel, \ + $(LINUX_DIR)/net/ipv6/$(mod).$(LINUX_KMOD_SUFFIX) \ + ) + AUTOLOAD:=$(call AutoLoad,32,ip6_tunnel) +endef + +define KernelPackage/ip6-tunnel/description + Kernel modules for IPv6-in-IPv6 and IPv4-in-IPv6 tunnelling +endef + +$(eval $(call KernelPackage,ip6-tunnel)) + + define KernelPackage/gre SUBMENU:=$(NETWORK_SUPPORT_MENU) TITLE:=GRE support -- Super-Acktion nur in der GMX Spieleflat: 10 Tage für 1 Euro. Über 180 Spiele downloaden und spiele: http://flat.games.gmx.de Index: package/kernel/modules/network.mk === --- package/kernel/modules/network.mk (Revision 11232) +++ package/kernel/modules/network.mk (Arbeitskopie) @@ -208,7 +208,7 @@ define KernelPackage/iptunnel6 SUBMENU:=$(NETWORK_SUPPORT_MENU) TITLE:=IPv6 tunneling - DEPENDS:= @LINUX_2_6 + DEPENDS:= @LINUX_2_6 +kmod-ipv6 KCONFIG:= \ CONFIG_INET6_TUNNEL FILES:= $(foreach mod,tunnel6, \ @@ -227,7 +227,11 @@ define KernelPackage/ipv6 SUBMENU:=$(NETWORK_SUPPORT_MENU) TITLE:=IPv6 support - KCONFIG:=CONFIG_IPV6 + KCONFIG:= \ + CONFIG_IPV6 \ + CONFIG_IPV6_PRIVACY=y \ + CONFIG_IPV6_MULTIPLE_TABLES=y \ + CONFIG_IPV6_SUBTREES=y FILES:=$(LINUX_DIR)/net/ipv6/ipv6.$(LINUX_KMOD_SUFFIX) AUTOLOAD:=$(call AutoLoad,20,ipv6) endef @@ -264,6 +268,24 @@ $(eval $(call KernelPackage,sit)) +define KernelPackage/ip6-tunnel + SUBMENU:=$(NETWORK_SUPPORT_MENU) + TITLE:=IP-in-IPv6 tunnelling + DEPENDS:= @LINUX_2_6 +kmod-ipv6 +kmod-iptunnel6 + KCONFIG:= CONFIG_IPV6_TUNNEL + FILES:= $(foreach mod,ip6_tunnel, \ + $(LINUX_DIR)/net/ipv6/$(mod).$(LINUX_KMOD_SUFFIX) \ + ) + AUTOLOAD:=$(call AutoLoad,32,ip6_tunnel) +endef + +define KernelPackage/ip6-tunnel/description + Kernel modules for IPv6-in-IPv6 and IPv4-in-IPv6 tunnelling +endef + +$(eval $(call KernelPackage,ip6-tunnel)) + + define KernelPackage/gre SUBMENU:=$(NETWORK_SUPPORT_MENU) TITLE:=GRE support ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Git repository for Linux kernel mainline merges
Gregers Petersen wrote: My comment was also a way towards: Ok if this should be done, then it needs to be done in an unconfusing manner - with a bit of thought and planning towards how such a git repository is to be integrated into what is already there ;-) I totally agree, using git without defining a good workflow is certain disaster :) - Axel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Git repository for Linux kernel mainline merges
Hey Imre, Le Friday 23 May 2008 16:13:59 Imre Kaloz, vous avez écrit : I share Gregers' view, too.. Also, one central git is a chaotic mess for this, every target would need it's own branch.. Think ddwrt's repo :P John and I had a short discussion about that on irc. Basically, the idea behind having git.openwrt.org is to have the following layout : - patches-upstream.git which contains the patches against generic (or quite) generic parts of the kernel - ar7.git, adm5120.git, ifxmips.git ... for every target that is either already merged mainline I do not think this would confuse people, because we do not need to mention such repositories to the end user. This would definitively ease the work to maintain custom drivers and archictecture code and ask mainline maintainers to just pull those repository as a branch. Do you like it better explained that way ? -- Best regards, Florian Fainelli Email : [EMAIL PROTECTED] http://openwrt.org --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Generic Gpio Support Status
Hi Mark, There are quite some targets which implement either a GPIO lib or Generic GPIO compatible API. You can enable the GPIO device driver for these targets, even though it is not done automatically. Le Friday 23 May 2008 16:43:49 Mark Kelly, vous avez écrit : what is the status of the new generic gpio support? In the current trunk build, I am not seeing the /dev/gpio node being built when the settings are enabled at least not on IXP4XX (Avila gw2345). I know this was working in my 2.6.23 builds, but I'm unsure if I've missed a setting in the new 2.6.25.x kernel? -- Best regards, Florian Fainelli Email : [EMAIL PROTECTED] http://openwrt.org --- signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Git repository for Linux kernel mainline merges
Axel Gembe wrote: Imre Kaloz wrote: I share Gregers' view, too.. Also, one central git is a chaotic mess for this, every target would need it's own branch.. Think ddwrt's repo :P I dunno how the current situation differs because every target effectively *IS* a branch from the generic kernel which is a branch from upstream. IMHO its only logical to create every target as a branch. I rather think it would be a chaotic mess to not use seperate branches. Personally I'd love to see an OpenWRT git repository. Even if it just auto-imports the patch series from OpenWRT (although I'd favor the other way around) The kernel git repositories should only be used for sharing changes with upstream. Maintaining the OpenWrt kernel code in one git repository or branch for every single target would only make things more complex, as it removes all the transparency around our custom maintained patches and the updates that we do to them. It boils down to the difference between maintaining patch sets of the trees vs. maintaining forks of the trees. Maintaining patch sets is not particularly well supported in regular git without additions like stgit or guilt (which would basically result in exactly the same storage format that we use now, as generated mostly by quilt). - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
