Re: [OpenWrt-Devel] Buying router SOC CPUs
Yes, Indeed Broadcom is difficult to work with. So is Atheros since they were bought out by Qualcom. You should mention your goal price and how many units you want to manufacture and that can help me figure out what hardware you should use. You could always use a general SOC from a chinese vendor and use a usb wifi module since those cost about 10 rmb. Ingenic is pretty open and provides their software and schematics online without a NDA. For me I will use any SDRAM module that is compatible. Normally ISSI or Etrontech. I would like to source 64MB Modules too, but that is more tricky since they build less of that and its more expensive. Maybe I can buy them second hand and build a memtest86 machine to test second hand memory modules for 64MB Ram. I also have the Idea of building programming jigs for the routers. My theory is to cut down the time it takes to use the iqflex. On the USB based routers It can take over a minute to fully boot. The iqflex process can take less than a minute. So my idea is to use flashrom with ftdi 2232 to program a special quick booting image for the iqflex calibration. Put the router back into the jig, extract the calibration info. Use a barcode reader to read a barcode that contains the mac and serial number. Then generate a new image with the unique mac and calibration info. Then spi flash that unique image back to the router. Best Regards, Jason On Fri, Jan 20, 2012 at 8:39 PM, jonsm...@gmail.com wrote: > On Fri, Jan 20, 2012 at 3:22 AM, jason duhamell > wrote: > > I have never used I2S before. Could you use an add-on Chip via the PCI > port > > on RT3052 by chance? > > There are lots of ways we can add it, but the cost of adding it ruins > the cost advantage of the using the router chip. Broadcom BCM4717 has > i2s, but that's another vendor that won't talk to us. I need to see a > datasheet to know if it is usable. > > Which SDRAM chips are in those BOMs? What is the pricing? > > -- > Jon Smirl > jonsm...@gmail.com > ___ > 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] More on G300HN LEDs
On the G300NH (v1), the router LED is turned on at boot completion to indicate it's running. Or at least, that's the intent of the "done" script. But the led script which sets up the mappings has START=96, but the done script is 95. So it never gets turned on. I fixed that in my setup by moving the led script to 94. For reference, on the G300NH2, the router LED isn't available until the WiFi drivers are loaded, due to the connection via PCI, so the diag light is used instead. Locally, in my rc.local, I turn that off after boot and then turn on the wireless LED. This is definitely a work around. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] DSL support and luci integration
I'd sure like to see netlink being used to communicate speed/carrier changes up into userspace. On 1/20/12 12:20 AM, Lee Essen wrote: > > On 19 Jan 2012, at 22:17, John Crispin wrote: > >> >>> >>> Anyway ... just a few ideas, interested in thoughts, I can post the >>> current patches if there's interest, or happy to explore other ideas if >>> I'm way off the mark. >> >> sure, show us your patch please ;) >> ___ > > Ok, these aren't in the right format for a couple of reasons (namely that I > haven't got a LuCI tree checked out yet, and that I'm still working on the > main script and haven't put it back into the main tree), but hopefully this > will give you a feel for what I'm talking about…. > > Firstly the main dsl_control script (/etc/init.d/dsl_control) … used to > stop/start and provide hardware specific stats, this is still work in > progress, I'll tidy it up and add more functionality (and error checking) > over the next couple of days, and build a proper patch... > [snip] ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] Add mostly complete support for Sitecom WL-341 v3 and other Sercomm IP1006RRv2 based boards
This patch adds support for the Sitecom WL-341 v3 and other Sercomm
IP1006RRv2 based boards for sysupgrade support and for the initial
flash through pushbutton initiated recovery mode with the special
partition table and fixes for the quirks and things required by the
modified bootloader.
There are two known bugs:
1. The LED configuration is broken -- only one led is working, an
amber led, as I found no way to know which GPIOs were used for those.
The board has 6 unlabeled leds, of which 1 is blue only and 5 are
amber/blue. If I understand which GPIOs go to which leds I'll submit a
patch later.
2. Wi-Fi is not working on my board probably because of the lack of
RAM (the board only has 16MiB ram, but there is an empty slot for
another ram chip,) but I don't know for sure. The driver loads but
hostapd fails to load so I think it's not related to the specific
device except for the lack of RAM.
Signed-off-by: Marco Antonio Mauro
---
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig
===
--- target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig (revision 29835)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/Kconfig (working copy)
@@ -36,6 +36,11 @@
select RALINK_DEV_GPIO_BUTTONS
select RALINK_DEV_GPIO_LEDS
+config RT305X_MACH_WL341V3
+ bool "Sitecom WL-341 v3 board support"
+ select RALINK_DEV_GPIO_BUTTONS
+ select RALINK_DEV_GPIO_LEDS
+
config RT305X_MACH_ESR_9753
bool "EnGenius ESR-9753 support"
select RALINK_DEV_GPIO_BUTTONS
Index: target/linux/ramips/files/arch/mips/ralink/rt305x/mach-wl341v3.c
===
--- target/linux/ramips/files/arch/mips/ralink/rt305x/mach-wl341v3.c
(revision
0)
+++ target/linux/ramips/files/arch/mips/ralink/rt305x/mach-wl341v3.c
(revision
0)
@@ -0,0 +1,134 @@
+/*
+ * Sitecom WL341v3 board support
+ *
+ * Copyright (C) 2012 Marco Antonio Mauro
+ *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 as published
+ * by the Free Software Foundation.
+ */
+
+#include
+#include
+#include
+#include
+#include
+
+#include
+#include
+#include
+#include
+#include
+
+#include "devices.h"
+
+#define WL341V3_GPIO_LED_STATUS_AMBER 8
+#define WL341V3_GPIO_LED_STATUS_GREEN 9
+#define WL341V3_GPIO_LED_WPS 13
+
+#define WL341V3_GPIO_BUTTON_WPS5 /* active low */
+#define WL341V3_GPIO_BUTTON_RESET 7 /* active low */
+
+#define WL341V3_BUTTONS_POLL_INTERVAL 20
+
+#ifdef CONFIG_MTD_PARTITIONS
+static struct mtd_partition wl341v3_partitions[] = {
+ {
+ .name = "u-boot",
+ .offset = 0,
+ .size = 0x02,
+ .mask_flags = MTD_WRITEABLE,
+ }, {
+ .name = "board-nvram",
+ .offset = 0x02,
+ .size = 0x01,
+ .mask_flags = MTD_WRITEABLE,
+ }, {
+ .name = "u-boot-env",
+ .offset = 0x03,
+ .size = 0x01,
+ .mask_flags = MTD_WRITEABLE,
+ }, {
+ .name = "kernel",
+ .offset = 0x04,
+ .size = 0x0d,
+ }, {
+ .name = "rootfs",
+ .offset = 0x11,
+ .size = 0x2e,
+ }, {
+ .name = "signature-eRcOmM",
+ .offset = 0x3f,
+ .size = 0x01,
+ }, {
+ .name = "firmware",
+ .offset = 0x04,
+ .size = 0x3b,
+ }, {
+ .name = "fullflash",
+ .offset = 0x00,
+ .size = 0x40,
+ }
+};
+#endif /* CONFIG_MTD_PARTITIONS */
+
+static struct physmap_flash_data wl341v3_flash_data = {
+#ifdef CONFIG_MTD_PARTITIONS
+ .nr_parts = ARRAY_SIZE(wl341v3_partitions),
+ .parts = wl341v3_partitions,
+#endif
+};
+
+static struct gpio_led wl341v3_leds_gpio[] __initdata = {
+ {
+ .name = "wl341v3:amber:status",
+ .gpio = WL341V3_GPIO_LED_STATUS_AMBER,
+ .active_low = 1,
+ }, {
+ .name = "wl341v3:blue:status",
+ .gpio = WL341V3_GPIO_LED_STATUS_GREEN,
+ .active_low = 1,
+ }, {
+ .name = "wl341v3:blue:wps",
+ .gpio = WL341V3_GPIO_LED_WPS,
+ .active_low = 1,
+ }
+};
+
+static struct gpio_button wl341v3_gpio_buttons[] __initdata = {
+ {
+ .desc = "reset",
+ .type = EV_KEY,
+ .code = KEY_RESTART,
+ .threshold = 3,
+ .gpio = WL341V3_GPIO_BUTTON_R
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
On 01/20/2012 06:15 PM, Mark Deneen wrote: I suppose that it's worth noting that the STM32F2/4 MCU lines also have this USB macrocell. Those micros are nommu, so it would only be applicable to uClinux. My point is that this driver may be useful across more than one platform / arch. Everyone who wants to get involved into mainlining this driver should read this: http://permalink.gmane.org/gmane.linux.usb.general/53913 Trying to push the driver as-is, even with "cleanups", is probably not going to work. However, creating a basic driver out of it for one or more platforms (maybe only supporting host or device), and moving along from there seems to be the best way of getting it accepted Regards, Ithamar Adema Team Embedded VOF ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
On Fri, Jan 20, 2012 at 8:10 AM, Alexander Gordeev wrote: > I think the real goal is to have this driver in the mainline kernel and > then it will be in openwrt automatically. Ok, it would be cool to merge > at least those several implementations inside openwrt (octeon, > ramips, etc). But there are others too so I think this attempt should > not be bound to Openwrt or any other project or we will always find > different drivers all other the net. I suppose that it's worth noting that the STM32F2/4 MCU lines also have this USB macrocell. Those micros are nommu, so it would only be applicable to uClinux. My point is that this driver may be useful across more than one platform / arch. -M ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] New package: dstat
Dstat is a versatile replacement for vmstat, iostat, netstat and ifstat written in python and with a very good plugin system. Signed-off-by: Roberto Riggio --- Index: utils/dstat/Makefile === --- utils/dstat/Makefile(revision 0) +++ utils/dstat/Makefile(revision 0) @@ -0,0 +1,47 @@ +# +# Copyright (C) 2012 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +include $(TOPDIR)/rules.mk + +PKG_NAME:=dstat +PKG_VERSION:=0.7.2 +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2 +PKG_SOURCE_URL:=http://dag.wieers.com/home-made/dstat/ +PKG_MD5SUM:=bfea4dc8037a0b18fc40a4dfc104dcc8 + +include $(INCLUDE_DIR)/package.mk + +define Package/dstat + SECTION:=utils + CATEGORY:=Utilities + TITLE:=Versatile resource statistics tool + URL:=http://dag.wieers.com/home-made/dstat/ + DEPENDS:=+python +endef + +define Package/dstat/description + Dstat is a versatile replacement for vmstat, iostat, netstat + and ifstat. Dstat overcomes some of their limitations and + adds some extra features, more counters and flexibility. + Dstat is handy for monitoring systems during performance + tuning tests, benchmarks or troubleshooting. +endef + +define Build/Compile +endef + +define Package/dstat/install + $(INSTALL_DIR) $(1)/usr/share/dstat + $(INSTALL_BIN) $(PKG_BUILD_DIR)/dstat $(1)/usr/share/dstat/dstat.py + $(INSTALL_DATA) $(PKG_BUILD_DIR)/plugins/dstat_*.py $(1)/usr/share/dstat/ + $(INSTALL_DIR) $(1)/usr/bin + $(LN) -sf ../share/dstat/dstat.py $(1)/usr/bin/dstat +endef + +$(eval $(call BuildPackage,dstat)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
20.01.2012 17:10, Alexander Gordeev: [...] However, there were at least several attempts to push dwc-otg to mainline through linuxppc-dev list. This is what I meant. Ah, ok. AFAICS the thing on linuxppc-dev failed totally, and I can see good reasons why. (It was based on an outdated version, only targeted very limited set of devices and one single platform, lacked devel history, mixed driver code with some ppc platform stuff, etc etc) However, maybe I'll try to examine it too (if time permits) The only excuse I'd see for creating yet another repository is if it appears too hard (or too long) to get stuff accepted to openwrt (AFAICS openwrt maintainers are somewhat overburdened already, but no idea how much really) I think the real goal is to have this driver in the mainline kernel and Yes. then it will be in openwrt automatically. Ok, it would be cool to merge at least those several implementations inside openwrt (octeon, ramips, etc). But there are others too so I think this attempt should not be bound to Openwrt or any other project or we will always find different drivers all other the net. Well, openwrt targets many different devices and tries to keep close to mainline. It is even no problem generally to borrow some driver from openwrt tree for a platform which openwrt does not immediately target yet (and that's what I do right now actually). There might be some more complications with preparing and submitting patches in such case though. But still, I think it'd be a step towards mainline. Thank you. Nikolai ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
Hello Conor, 20.01.2012 14:09, Conor O'Gorman: I would suggest gathering all the available versions into a repository. Not merged, just gathered together, organised by version and source. That would be a step towards comparing versions, and also gaining the attention of the relevant people. Yes, that would make sense probably. I'll think about it. Thank you. Nikolai So this would be a possible the directory structure: 2.40a - octeon 2.60a - ppp4xx 1.05 - ipmate 2.70 2.72a - dd-wrt - fonosfera Those versions found with a google for "defineDWC_DRIVER_VERSION" This discussion is one of the more extensive I have seen. And the people involved appear to have experience with the driver: http://patchwork.ozlabs.org/patch/57332/ Conor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
В Fri, 20 Jan 2012 17:03:01 +0400 Nikolai Zhubr пишет: > Hello Alexander, > > 20.01.2012 13:01, Alexander Gordeev: > [trim] > > > > IMO a separate repository (or adoption into staging) would be better > > because there are too many interested parties and also the main dwc-otg > > development happens not in openwrt. > > > > Where does it happen? > > I've actually got a feeling that in fact no real development is now > happening, but rather some manufacturers and interested users make their > copies (of basically the same thing), reformat tabs and whitespace all > over 200k lines of code as they feel cool, then in some cases introduce > several random 3-line additions/fixes in order to make their specific > device just do what they need at the moment... and finally (sometimes) > publish this as "new shining" version. Now this is NOT a development, > IMHO. I'd be happy if you prove me wrong however. You are right, no need to argue. :) However, there were at least several attempts to push dwc-otg to mainline through linuxppc-dev list. This is what I meant. > The only excuse I'd see for creating yet another repository is if it > appears too hard (or too long) to get stuff accepted to openwrt (AFAICS > openwrt maintainers are somewhat overburdened already, but no idea how > much really) I think the real goal is to have this driver in the mainline kernel and then it will be in openwrt automatically. Ok, it would be cool to merge at least those several implementations inside openwrt (octeon, ramips, etc). But there are others too so I think this attempt should not be bound to Openwrt or any other project or we will always find different drivers all other the net. -- Alexander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
Hello Alexander, 20.01.2012 13:01, Alexander Gordeev: [trim] IMO a separate repository (or adoption into staging) would be better because there are too many interested parties and also the main dwc-otg development happens not in openwrt. Where does it happen? I've actually got a feeling that in fact no real development is now happening, but rather some manufacturers and interested users make their copies (of basically the same thing), reformat tabs and whitespace all over 200k lines of code as they feel cool, then in some cases introduce several random 3-line additions/fixes in order to make their specific device just do what they need at the moment... and finally (sometimes) publish this as "new shining" version. Now this is NOT a development, IMHO. I'd be happy if you prove me wrong however. The only excuse I'd see for creating yet another repository is if it appears too hard (or too long) to get stuff accepted to openwrt (AFAICS openwrt maintainers are somewhat overburdened already, but no idea how much really) Thank you. Nikolai ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Buying router SOC CPUs
On Fri, Jan 20, 2012 at 3:22 AM, jason duhamell wrote: > I have never used I2S before. Could you use an add-on Chip via the PCI port > on RT3052 by chance? There are lots of ways we can add it, but the cost of adding it ruins the cost advantage of the using the router chip. Broadcom BCM4717 has i2s, but that's another vendor that won't talk to us. I need to see a datasheet to know if it is usable. Which SDRAM chips are in those BOMs? What is the pricing? -- Jon Smirl jonsm...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
I would suggest gathering all the available versions into a repository. Not merged, just gathered together, organised by version and source. That would be a step towards comparing versions, and also gaining the attention of the relevant people. So this would be a possible the directory structure: 2.40a - octeon 2.60a - ppp4xx 1.05 - ipmate 2.70 2.72a - dd-wrt - fonosfera Those versions found with a google for "define DWC_DRIVER_VERSION" This discussion is one of the more extensive I have seen. And the people involved appear to have experience with the driver: http://patchwork.ozlabs.org/patch/57332/ Conor On Fri, 2012-01-20 at 13:01 +0400, Alexander Gordeev wrote: > Hi Nikolai, > > В Thu, 19 Jan 2012 22:39:54 +0400 > Nikolai Zhubr пишет: ... > > Anyway, it would be nice to eventually combine all those various > > versions floating around (targeted for different architectures and > > revisions of controller) into a single unified version. > > > > IMO a separate repository (or adoption into staging) would be better > because there are too many interested parties and also the main dwc-otg > development happens not in openwrt. > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Driver(s) for Synopsys' DesignWare USB OTG
Hi Nikolai, В Thu, 19 Jan 2012 22:39:54 +0400 Nikolai Zhubr пишет: > Hello Conor, > > I'm now trying ver 2.72 basically from openwrt trunk with some tiny > amlogic-specific additions. I think 2.72 is most relevant currently (and > nothing newer exists apparently) but device-mode does not work well for > me yet. And 2.60 was no better for me in this respect. Can't test > host-mode at the moment because it is quite difficult to arrange as long > as USB is the only wired interface physycally available and wifi not > working yet (It's a tablet, ARMv7-based) > > If I manage to get it to work satisfactory at least in device-mode, I'll > certainly share my findings and either try to submit patches to openwrt > (I'd prefer that way) or maybe create a separate repository somewhere > (downside in this case would be yet more scattering of this driver, > which I'd like to avoid). If all goes well then I'll probably test > host-mode a bit later (Not sure when it happens exactly) > > Anyway, it would be nice to eventually combine all those various > versions floating around (targeted for different architectures and > revisions of controller) into a single unified version. > > So I suppose you'll be able to do some testing in host-mode on your > platform, if it happens to be necessary? IMO a separate repository (or adoption into staging) would be better because there are too many interested parties and also the main dwc-otg development happens not in openwrt. -- Alexander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Buying router SOC CPUs
Hi, I have read your message in the thread, and I wonder how far have you come with your development? Do you have any website? Thanks in advance. On Fri, Jan 20, 2012 at 5:11 AM, jason duhamell wrote: > Im going to manufacture Ralink and Realtek routers. The volume prices are > about 2.7 usd for RT3050 and 3.45 usd for RT3052. Realteak > RTL8196c/rtl8188re combo is 2.25 usd. Im focused on Realtek at the moment > since the BOM is about 7 to 8 usd. > > Jason > > > On Fri, Jan 20, 2012 at 8:43 AM, jonsm...@gmail.com wrote: > >> On Thu, Jan 19, 2012 at 7:21 PM, jason duhamell >> wrote: >> > You should try buying the samples off taobao.com >> > >> > Jason >> >> On taobao... >> >> Ralink RT3050 between $2 and $7, quite a spread. >> Ralink RT3052 between $2 and $5 >> >> Finished routers using these chips are between $20 and $30. >> >> So what's the real price for these chips? I've always suspected they >> were in the $5 range. >> >> I stumbled onto the datasheet for the RT3050. >> http://www.tracermcc.ru/foto/bender/RT3050_5x_V2.0_081408_0902.pdf >> >> >> -- >> Jon Smirl >> jonsm...@gmail.com >> ___ >> 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] Buying router SOC CPUs
I have never used I2S before. Could you use an add-on Chip via the PCI port on RT3052 by chance? Best Regards, Jason On Fri, Jan 20, 2012 at 12:42 PM, jonsm...@gmail.com wrote: > On Thu, Jan 19, 2012 at 11:11 PM, jason duhamell > wrote: > > Im going to manufacture Ralink and Realtek routers. The volume prices are > > about 2.7 usd for RT3050 and 3.45 usd for RT3052. Realteak > > RTL8196c/rtl8188re combo is 2.25 usd. Im focused on Realtek at the moment > > since the BOM is about 7 to 8 usd. > > Those are great prices. > > Do you know if any of the router chips have a decent I2S > implementation? RT3050 I2S is only 16b (not 24b inside 32b) and the > internal clock can only do 48Khz. Realtek does not have I2S support. > > I'm looking for one that can do 32b I2S frames with 24b data (all > recent I2S does this). And can generate an accurate 44.1Khz clock. > > > > > > Jason > > > > On Fri, Jan 20, 2012 at 8:43 AM, jonsm...@gmail.com > > wrote: > >> > >> On Thu, Jan 19, 2012 at 7:21 PM, jason duhamell > >> wrote: > >> > You should try buying the samples off taobao.com > >> > > >> > Jason > >> > >> On taobao... > >> > >> Ralink RT3050 between $2 and $7, quite a spread. > >> Ralink RT3052 between $2 and $5 > >> > >> Finished routers using these chips are between $20 and $30. > >> > >> So what's the real price for these chips? I've always suspected they > >> were in the $5 range. > >> > >> I stumbled onto the datasheet for the RT3050. > >> http://www.tracermcc.ru/foto/bender/RT3050_5x_V2.0_081408_0902.pdf > >> > >> > >> -- > >> Jon Smirl > >> jonsm...@gmail.com > >> > >> ___ > >> 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 > > > > > > -- > Jon Smirl > jonsm...@gmail.com > ___ > 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
