Re: [OpenWrt-Devel] [PATCH] ramips: rename rt3352 usb platform devices
Hi All,
I tested this patch and it works.
Now I can detect USB device normally.
Thanks Daniel.
BR.
Hans
2012/8/7 Daniel Golle dgo...@allnet.de:
In order to get OHCI/EHCI working on the Rt3352, the platform device must be
named so rt3883-?hci will recognize it.
Maybe we should rename the whole story to be rt3xxx-?hci for both, Rt3883 and
Rt3352...?
Signed-off-by: Daniel Golle dgo...@allnet.de
diff --git a/target/linux/ramips/files/arch/mips/ralink/rt305x/devices.c
b/target/linux/ramips/files/arch/mips/ralink/rt305x/devices.c
index bebab81..2e884c3 100644
--- a/target/linux/ramips/files/arch/mips/ralink/rt305x/devices.c
+++ b/target/linux/ramips/files/arch/mips/ralink/rt305x/devices.c
@@ -352,7 +352,7 @@ static struct resource rt3352_ehci_resources[] = {
static u64 rt3352_ehci_dmamask = DMA_BIT_MASK(32);
static struct platform_device rt3352_ehci_device = {
- .name = rt3352-ehci,
+ .name = rt3883-ehci,
.id = -1,
.resource = rt3352_ehci_resources,
.num_resources = ARRAY_SIZE(rt3352_ehci_resources),
@@ -382,7 +382,7 @@ static struct rt3883_ohci_platform_data rt3352_ohci_data
= {
static u64 rt3352_ohci_dmamask = DMA_BIT_MASK(32);
static struct platform_device rt3352_ohci_device = {
- .name = rt3352-ohci,
+ .name = rt3883-ohci,
.id = -1,
.resource = rt3352_ohci_resources,
.num_resources = ARRAY_SIZE(rt3352_ohci_resources),
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] buildroot-ng
On 12 September 2011 11:53, Florian Fainelli flor...@openwrt.org wrote: Hello, On Friday 09 September 2011 16:53:15 Roman Yeryomin wrote: On 6 September 2011 18:37, Roman Yeryomin leroi.li...@gmail.com wrote: Did anyone think of separating buildroot-ng from the content (packages and targets) into a separate project (under OpenWrt name of cause)? Then one can do something like `make content' and depending on what is configured get either openwrt or something else. Really noone? Well then how about not thinking but actually doing it? I already use it like that and thought that community could benefit from such approach too. This looks like a good idea, I am not sure about how many OpenWrt-specific stuff are folded into our build system, but if you have any patches to decouple OpenWrt-specificities from buildroot, feel free to get them posted. -- Actually build system and it's content can be very easily separated with minor changes in the structure and additional makefile. I'm using this approach for about a year already. I took fairly recent git clone of OpenWrt trunk and made two branches there: bng (separated buildroot-ng) and bng-content-owrt (separated content) and put that into github: https://github.com/yeryomin/openwrt-bng/tree/bng Of cause there is a lot of space for improvement but this can be used as start point. Maybe then sometime buildroot-ng will be able to support non linux targets also (e.g. nuttx realtime os). Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] peervpn package Makefile
On Tuesday 22 May 2012 10:56:15 Dan VerWeire wrote: PeerVPN (http://www.peervpn.net/), by Tobias Volk, is software that builds virtual ethernet networks between multiple computers. A virtual network built by PeerVPN uses a full mesh topology. All nodes talk directly to each other, there is no need for a central server. If one node goes down, the rest of the network is unaffected. Configuring PeerVPN is easy. You just need to configure an encryption key, network name and the contact information (IP address and port) of some other PeerVPN nodes. Adding a new node to an existing network doesn't require the existing nodes to alter their configuration, because its IP address is automatically distributed across the whole virtual network. Signed-off-by: Dan VerWeire dverwe...@gmail.com Applied in r33060, thanks! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [packages] Kamailio3 - replacement for old kamailio package (RESENT)
On Saturday 28 July 2012 16:52:31 Jiri Slachta wrote: Hello, I am resending last version of kamailio3 package. It's a replacement for old kamailio package (Network/Telephony, version 1.5.2). I didn't know, if I should replace old kamailio package, or make it standalone, so I created a new package kamailio3 instead of updating old kamailio. All requested changes has been made (mentioned here http://patchwork.midlink.org/patch/2061/). Official kamailio 3.0 was released on January 11, 2010. It includes an astonishing number of improvements and new features. Kamailio v3.3.0 was released on June 18, 2012. This patch contains last version of Kamailio. Compared to previous version of kamailio3 package (sent http://patchwork.openwrt.org/patch/2284/ ) there is no patch for curl.h line removal from and also a few modules were added. If you will accept this patch, could you close patches 2284 and 2061 on patchwork? Thank you. Signed-off-by: Jiri Slachta j...@slachta.eu Applied in r33061, thanks! There is one issue to fix for 64-bits host, because modules get installed in /usr/lib64 instead of /usr/lib, will fix this. -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] WA7510N signal stregth-led support
Am 08.08.2012 17:52, schrieb Stefan Helmert: Hello, now I want to add support for the signal strength leds on the tpl-link WA7510N. I looked for some code for the ubnt nanostation but there are some open questions: How does openwrt know that the led does show what it should show? Is it adressed by the .name in the structure? The .gpio member seams to be the pin-number on the chip. To try out where the led is connected, how to activate the gpios by cli? Is there a special driver which mounts all gpios in /dev? So I can test: echo 1 gpio0815? Is there somewhere a driver or option to activate, which reads the signalstrength and passes the value to the leds? Is there a config file which defines the treshold for each led? Thanks ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel So, now I found out, the LEDs are connected to the AR9280 wlan chip. It has GPIOs. How to access the GPIOs of the AR9280? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] iperf: add minimal init.d script
Starts iperf in server mode as a daemon, with IPv4 + IPv6 support enabled (-V)
Signed-off-by: Gui Iribarren g...@altermundi.net
Index: net/iperf/files/iperf
===
--- net/iperf/files/iperf (revision 0)
+++ net/iperf/files/iperf (revision 0)
@@ -0,0 +1,12 @@
+#!/bin/sh /etc/rc.common
+# Copyright (C) 2006-2012 OpenWrt.org
+
+START=98
+
+start () {
+ service_start /usr/bin/iperf -s -D -V
+}
+
+stop() {
+ killall iperf
+}
Property changes on: net/iperf/files/iperf
___
Added: svn:executable
+ *
Index: net/iperf/Makefile
===
--- net/iperf/Makefile (revision 32789)
+++ net/iperf/Makefile (working copy)
@@ -9,7 +9,7 @@
PKG_NAME:=iperf
PKG_VERSION:=2.0.5
-PKG_RELEASE:=1
+PKG_RELEASE:=2
PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION)
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
@@ -77,6 +77,8 @@
define Package/iperf/install
$(INSTALL_DIR) $(1)/usr/bin
$(INSTALL_BIN) $(PKG_BUILD_DIR)/src/iperf $(1)/usr/bin/iperf
+ $(INSTALL_DIR) $(1)/etc/init.d
+ $(INSTALL_BIN) ./files/iperf $(1)/etc/init.d/iperf
endef
Package/iperf-mt/install = $(Package/iperf/install)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
