[OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz feiner Strich von unten über die Pins. Bei mehr raucht der Router sofort ab. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
manche sind eben nicht mit allen wassern gewaschen.. Am 12. September 2013 08:55 schrieb Alina Friedrichsen x-al...@gmx.net: Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz feiner Strich von unten über die Pins. Bei mehr raucht der Router sofort ab. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- -- Dipl.-Ing. Ulf Kypke-Burchardi Köpenicker Strasse 159 10997 Berlin, Germany +49 - (0) 177 - 3405152 -- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
* Alina Friedrichsen x-al...@gmx.net [12.09.2013 09:14]: Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz feiner Strich von unten über die Pins. Bei mehr raucht der Router sofort ab. Yes, will do this. For the non-germans here: Be extremely careful when soldering a serial console on TP-Link TL-WDR4900 - the design of the PCB is somehow not suited and important connection/parts are near the soldering points. We have now 3 Routers which are dead, just because we used too much soldering-water... bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] base-files: uci-defaults Actually generate a working ipv6 configuration by default.
On Mon, 26 Aug 2013 16:46:46 -0700
ebied...@xmission.com (Eric W. Biederman) wrote:
By default generate the configuaration:
config interface 'lan'
option ifname 'eth0.1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '64'
config interface 'wan'
option ifname 'eth1'
option proto 'dhcp'
config alias 'wan6'
option interface 'wan'
option proto 'dhcpv6'
option reqprefix 60
Critically this uses the config alias syntax when generating wan6
allowing wan6 to actually work.
As both a sample and because it is the proper location move the
request for a /60 from the lan to the wan interface, and use the
proper directive reqprefix.
On the lan interface only assign a /64. Anything else is over kill or
breaks slack depending on how it is implemented.
This configuration was tested and works for my native ipv6 at home
with comcast cable.
Signed-off-by: Eric W. Biederman ebied...@xmission.com
---
.../base-files/files/lib/functions/uci-defaults.sh |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/package/base-files/files/lib/functions/uci-defaults.sh
b/package/base-files/files/lib/functions/uci-defaults.sh index
bf6fe1e..f284c24 100644 ---
a/package/base-files/files/lib/functions/uci-defaults.sh +++
b/package/base-files/files/lib/functions/uci-defaults.sh @@ -176,7
+176,7 @@ set network.lan.type='bridge' set network.lan.proto='static'
set network.lan.ipaddr='192.168.1.1'
set network.lan.netmask='255.255.255.0'
-set network.lan.ip6assign='60'
+set network.lan.ip6assign='64'
EOF
}
@@ -187,9 +187,10 @@ ucidef_set_interface_wan() {
set network.wan='interface'
set network.wan.ifname='$ifname'
set network.wan.proto='dhcp'
-set network.wan6='interface'
-set network.wan6.ifname='@wan'
+set network.wan6='alias'
+set network.wan6.interface='wan'
set network.wan6.proto='dhcpv6'
+set network.wan6.reqprefix='60'
EOF
}
I can confirm this works nicely with Comcast cable (native IPV6 was just
enabled recently). Thanks!
--
Nathan
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
On Thu, 12 Sep 2013 09:45:59 +0200, Joerg Dorchain jo...@dorchain.net wrote: On Thu, Sep 12, 2013 at 08:55:29AM +0200, Alina Friedrichsen wrote: Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz feiner Strich von unten über die Pins. Bei mehr raucht der Router sofort ab. Loetwasser? Auf Elektronik?! Nicht gut(tm). Loetwasser nimmt man fuer starkt verdreckte und korrodierte Metallteile beim Klempnern (Kupferleitung in Omas feuchtem Keller). Feineres Material reagiert auf die Mischung aus Zinkoxid, Salzsaere und Salmiak mit Aufloesung. Man moechte bitte Elektroniklot mit Flussmittelkern verwenden (frueher Kolophonium), das reicht fuer Staub und Reste von Fingerabdruecken. KEIN LOETWASSER. Evtl. waere ein Hinweis auf einen Loetkurs angebracht. (z.B. http://www.kemo-electronic.de/de/loetkurs.php) This is an international list, please stick to english. Imre ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
Στις Πεμ 12 Σεπτ 2013 09:34:34 Bastian Bittorf έγραψε: * Alina Friedrichsen x-al...@gmx.net [12.09.2013 09:14]: Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz feiner Strich von unten über die Pins. Bei mehr raucht der Router sofort ab. Yes, will do this. For the non-germans here: Be extremely careful when soldering a serial console on TP-Link TL-WDR4900 - the design of the PCB is somehow not suited and important connection/parts are near the soldering points. We have now 3 Routers which are dead, just because we used too much soldering-water... bye, bastian Thanks signature.asc Description: This is a digitally signed message part. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] plans to update hostapd
hello are there any plans to update hostapd to current git? it has ACS support, IMHO ACS support should be enabled by default best regads ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] base-files: uci-defaults Actually generate a working ipv6 configuration by default.
NACK to this patch, comments below. -set network.lan.ip6assign='60' +set network.lan.ip6assign='64' Cosmetical change, not needed. If less than a /60 is available, it will use less. -set network.wan6='interface' -set network.wan6.ifname='@wan' +set network.wan6='alias' +set network.wan6.interface='wan' Those are exactly equivalent, in fact you're replacing the current alias notation with the deprecated one. +set network.wan6.reqprefix='60' That's probably the only actual required change, please retest with only this. ~ Jow signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12.09.2013 09:34, Bastian Bittorf wrote: * Alina Friedrichsen x-al...@gmx.net [12.09.2013 09:14]: Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz feiner Strich von unten über die Pins. Bei mehr raucht der Router sofort ab. Yes, will do this. For the non-germans here: Be extremely careful when soldering a serial console on TP-Link TL-WDR4900 - the design of the PCB is somehow not suited and important connection/parts are near the soldering points. We have now 3 Routers which are dead, just because we used too much soldering-water... Thank you for the translation, but 3 doesn't correlate with 'dutzende', or you have another, undisclosed source for your information? But the more literal translation 'Several dozen' routers seems wired too. I would trust anyone to stop after very few units, regardless of their individual price. Loosing one or two should be enough pain to change soldering tactics. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlIxkAcACgkQ31DJeiZFuHcL5gCg3T42NrOgCEbY5WxbS6awO35g fXsAnRKimskBOl35NOc6epLnok6jLa5o =niC5 -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
* Steffen Hoffmann hoff...@web.de [12.09.2013 12:29]: Thank you for the translation, but 3 doesn't correlate with 'dutzende', or you have another, undisclosed source for your information? 8-) i'am involved in this special case, so i know the real situation. (somebody tends to hype here) this is a very funny thread, especially for the non-germans i think 8-) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
On 12/09/13 12:32, Bastian Bittorf wrote: * Steffen Hoffmannhoff...@web.de [12.09.2013 12:29]: Thank you for the translation, but 3 doesn't correlate with 'dutzende', or you have another, undisclosed source for your information? 8-) i'am involved in this special case, so i know the real situation. (somebody tends to hype here) this is a very funny thread, especially for the non-germans i think 8-) bye, bastian i can recommend this stuff - http://www.reichelt.de/Flussmittel-Loetpasten/FL-88/3//index.html?ACTION=3GROUPID=4132ARTICLE=7809SHOW=1START=0OFFSET=16; ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Corrupted packets with bgmac on BCM5357* devices
Network on BCM5357* devices isn't working since ever. It seems there is some problem with bgmac I don't understand. First of all, when using interface without VLAN enabled and without bridging it - no packets appear. That can be easily workarounded with ifconfig eth0 promisc. Then I can see packets appearing, however they don't have a valid MAC addresses in src/dest fields. I decided to dump packets in bgmac driver, that allow me to include Broadcom's extra RX header. Does it give any hint for anyone? Do you have any idea what can be wrong? -- Rafał ### Some BCM5357 device ### 01 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2930 31 32 33 34 35 36 37 38 39 40 41 42 43 44 len flags rest alignmentMAC dest MAC srctype payload # swconfig dev eth0 set enable_vlan 1 # swconfig dev eth0 set apply [ 58.032000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:1388A 00 08 00 6E 77 72 74 2E 70 6F 6F 6C 2E 6E 74 70 2E 6F 72 67 00 2D 70 00 32 2E 6F 70 65E0 00 1F C2 1E 00 00 05 00 40 10 08 1C E2 B0 E4 11 B1 01 04 00 08 00 59 27 66 36 57 36 7D F6 65 C7 6F 06 00 A [ 58.264000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:238EE 00 08 00 77 65 64 2B 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 00 60 00 00 00 01 00E0 00 18 C3 1E 00 08 04 0D 40 1F 0D 18 E0 B0 E1 29 32 00 00 07 00 00 60 12 03 41 60 15 06 61 30 13 03 11 60 3 [ 59.164000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:1388A 00 08 00 00 00 00 00 E4 A9 0D 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00E0 00 18 C3 1E 00 08 04 05 40 1F 0D 18 E0 B0 E1 19 B3 00 08 00 00 00 50 25 67 35 50 3E 72 F4 67 C5 66 0C 00 3 [ 59.844000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:221DD 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00E0 00 1F C2 1E 00 00 05 00 40 10 37 1C E2 B0 E4 11 0F 03 04 00 0D 00 61 10 02 46 61 10 06 66 31 10 01 13 61 0 [ 61.296000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:217D9 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00E0 00 18 C3 1E 00 08 04 09 40 1F 3D 18 E0 B0 E1 19 5F 00 08 00 01 00 50 25 67 35 50 3E 72 F4 67 C5 66 0C 00 3 [ 88.108000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:11775 00 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00FF FF 18 C3 1E 00 08 04 00 40 10 8B 18 C0 F1 80 0A CF A1 05 18 00 60 00 D5 44 6F 44 E3 44 52 44 66 44 48 44 0 [ 88.14] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:1086C 00 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00FF FF 18 C3 1E 00 08 04 08 40 10 AB 18 C0 F1 80 0A 8E A1 05 18 00 E0 00 D5 44 6F 44 E3 44 52 44 66 44 48 44 0 # swconfig dev eth0 set enable_vlan 0 # swconfig dev eth0 set apply [ 1422.584000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:13789 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00E0 00 1F C2 8E 40 50 00 F4 D1 80 01 0E 1B 9E 31 0B 80 00 00 00 00 55 72 56 03 E5 23 47 7F 56 6C C6 00 10 00 2 [ 1423.252000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:219DB 00 08 00 55 55 55 55 55 55 55 55 55 55 55 55 55 55 15 55 55 51 75 15 55 55 55 55 55 55E0 00 18 C3 8E 40 32 00 F0 D1 80 00 00 1F 94 F0 0F 80 00 00 00 00 21 30 15 06 51 60 16 06 31 30 11 06 01 30 0 [ 1425.728000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:215D7 00 08 00 55 55 55 55 55 55 55 55 57 55 55 55 55 15 55 55 55 55 55 55 55 55 55 55 55 55E0 00 1F C2 8E 40 90 00 F4 D1 83 01 0E 1B 9E F1 05 80 00 10 00 00 55 72 56 03 E5 23 47 7F 56 6C C6 00 10 00 2 [ 1426.428000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:219DB 00 08 00 55 55 55 55 15 55 57 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55E0 00 18 C3 8E 40 32 00 F0 D1 80 00 00 1F 94 F0 0F 80 00 00 00 00 21 30 15 06 51 60 16 06 31 30 11 06 01 30 0 [ 1473.124000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:236EC 00 08 00 55 55 55 55 15 15 55 55 55 55 55 55 55 55 51 51 55 55 55 55 55 55 51 55 55 55E0 00 1F C2 8E 40 D0 00 F4 D1 80 01 0E 1B 9E 22 03 00 70 00 00 00 26 31 10 04 56 61 10 06 33 31 10 01 06 31 9 [ 1473.824000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:219DB 00 08 00 55 55 55 55 35 55 55 55 55 74 55 55 55 55 55 55 55 55 55 55 55 55 55 51 71 51E0 00 1F C2 8E 40 30 00 F4 D1 83 01 0E 1B 9E F1 00 80 00 00 00 00 26 31 10 04 56 61 10 06 33 31 10 01 06 31 0 [ 1476.956000]
Re: [OpenWrt-Devel] Corrupted packets with bgmac on BCM5357* devices
On 09/12/2013 01:23 PM, Rafał Miłecki wrote:
Network on BCM5357* devices isn't working since ever. It seems there
is some problem with bgmac I don't understand.
First of all, when using interface without VLAN enabled and without
bridging it - no packets appear. That can be easily workarounded with
ifconfig eth0 promisc. Then I can see packets appearing, however
they don't have a valid MAC addresses in src/dest fields.
I decided to dump packets in bgmac driver, that allow me to include
Broadcom's extra RX header.
Does it give any hint for anyone? Do you have any idea what can be wrong?
Hi,
the switch in the BCM5357 needs a special configuration. Does your SoC
have the chipid 0x5356? Then the robo core rev is 3.
This is part of the robo switch driver:
if (robo-corerev 3) {
val32 |= ((1 20) | /* valid write */
((vid 4) 12)); /* vlan id bit[11:4] */
} else {
val32 |= ((1 24) | /* valid write */
(vid 12)); /* vlan id bit[11:4] */
}
Could you try the attached patch on your device.
Hauke
diff --git a/target/linux/generic/files/drivers/net/phy/b53/b53_common.c b/target/linux/generic/files/drivers/net/phy/b53/b53_common.c
index 7ff4624..001acfa 100644
--- a/target/linux/generic/files/drivers/net/phy/b53/b53_common.c
+++ b/target/linux/generic/files/drivers/net/phy/b53/b53_common.c
@@ -189,7 +189,7 @@ static void b53_set_vlan_entry(struct b53_device *dev, u16 vid, u16 members,
u32 entry = 0;
if (members)
- entry = (untag VA_UNTAG_S) | members | VA_VALID_25;
+ entry = (untag VA_UNTAG_S) | members | VA_VALID_25_R4;
b53_write32(dev, B53_VLAN_PAGE, B53_VLAN_WRITE_25, entry);
b53_write16(dev, B53_VLAN_PAGE, B53_VLAN_TABLE_ACCESS_25, vid |
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Corrupted packets with bgmac on BCM5357* devices
2013/9/12 Hauke Mehrtens ha...@hauke-m.de: On 09/12/2013 01:23 PM, Rafał Miłecki wrote: Network on BCM5357* devices isn't working since ever. It seems there is some problem with bgmac I don't understand. First of all, when using interface without VLAN enabled and without bridging it - no packets appear. That can be easily workarounded with ifconfig eth0 promisc. Then I can see packets appearing, however they don't have a valid MAC addresses in src/dest fields. I decided to dump packets in bgmac driver, that allow me to include Broadcom's extra RX header. Does it give any hint for anyone? Do you have any idea what can be wrong? Hi, the switch in the BCM5357 needs a special configuration. Does your SoC have the chipid 0x5356? Then the robo core rev is 3. Not exactly a 0x5356 E900: [ 0.00] bcma: bus0: Found chip with id 0xD144, rev 0x01 and package 0x08 [ 4.06] b53_common: found switch: BCM5325, rev 0 [ 4.064000] (unregistered net_device): attached PHY driver [Broadcom B53 (2)] (mii_bus:phy_addr=bgmac-0-0:1e) No-name board: [ 0.00] bcma: bus0: Found chip with id 0x5357, rev 0x01 and package 0x08 [ 4.608000] b53_common: found switch: BCM5325, rev 0 [ 4.616000] (unregistered net_device): attached PHY driver [Broadcom B53 (2)] (mii_bus:phy_addr=bgmac-0-0:1e) I forgot you mention one important fact. As you already noticed, enabling switch doesn't add VLAN tags to the packets. Another story is that with the default b53 I don't get any RX interrupts (and packets). I has to hack b53 to don't set VC5_DROP_VTABLE_MISS. Hauke: I'll try your patch, but it seems to be for some higher BCM5325 rev, isn't it? Secondly, you're patching b53. As I said, even without switch enabled I get corrupted packets too :( -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: add support for TL-MR3040 v2
This patch adds support for building firmware images for the TP-Link TL-MR3040 v2. Tested and working on v2.1 hardware. Signed-off-by: Mads Hansen d...@taba.se Index: trunk/target/linux/ar71xx/image/Makefile === --- trunk/target/linux/ar71xx/image/Makefile(revision 37950) +++ trunk/target/linux/ar71xx/image/Makefile(working copy) @@ -912,7 +912,8 @@ $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV1,tl-mr11u-v1,TL-MR11U,ttyATH0,115200,0x00110101,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV2,tl-mr11u-v2,TL-MR11U,ttyATH0,115200,0x00110102,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3020,tl-mr3020-v1,TL-MR3020,ttyATH0,115200,0x3021,1,4Mlzma)) -$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3040,tl-mr3040-v1,TL-MR3040,ttyATH0,115200,0x3041,1,4Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3040V1,tl-mr3040-v1,TL-MR3040,ttyATH0,115200,0x3041,1,4Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3040V2,tl-mr3040-v2,TL-MR3040,ttyATH0,115200,0x3042,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3220V2,tl-mr3220-v2,TL-MR3220-v2,ttyATH0,115200,0x3222,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3420V2,tl-mr3420-v2,TL-MR3420-v2,ttyS0,115200,0x3422,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLWR703,tl-wr703n-v1,TL-WR703N,ttyATH0,115200,0x07030101,1,4Mlzma)) @@ -971,6 +972,7 @@ $(eval $(call MultiProfile,OPENMESH,OM2P MR600)) $(eval $(call MultiProfile,TEW652BRP,TEW652BRP_FW TEW652BRP_RECOVERY)) $(eval $(call MultiProfile,TLMR11U,TLMR11UV1 TLMR11UV2)) +$(eval $(call MultiProfile,TLMR3040,TLMR3040V1 TLMR3040V2)) $(eval $(call MultiProfile,TLMR3220,TLMR3220V1 TLMR3220V2)) $(eval $(call MultiProfile,TLMR3420,TLMR3420V1 TLMR3420V2)) $(eval $(call MultiProfile,TLWA801,TLWA801NV1)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Corrupted packets with bgmac on BCM5357* devices
Some example with Wireshark output visible too. Wireshark running on notebook running dhcpd-test eth0. bgmac with debugging running on Linksys E900 What bgmac received doesn't really look like what was sent (registered by Wireshark). ff ff ff ff ff ff e8 11 32 cd e2 be 08 00 45 10 2.E. 0010 01 5c 00 00 40 00 40 11 39 82 00 00 00 00 ff ff .\..@.@.9... 0020 ff ff 00 44 00 43 01 48 77 e4 01 01 06 00 bd 1c ...D.C.Hw... 0030 91 23 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .#.. 0040 00 00 00 00 00 00 e8 11 32 cd e2 be 00 00 00 00 2... 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0110 00 00 00 00 00 00 63 82 53 63 35 01 01 3d 07 01 ..c.Sc5..=.. 0120 e8 11 32 cd e2 be 3c 0c 64 68 63 70 63 64 20 33 ..2dhcpcd 3 0130 2e 32 2e 33 51 1a 01 00 00 6c 69 6e 75 78 2d 73 .2.3Qlinux-s 0140 61 6d 73 75 6e 67 37 30 30 67 37 61 2e 6c 61 6e amsung700g7a.lan 0150 37 17 3a 3b 01 1c 79 21 03 0c 77 0f 06 28 29 2a 7.:;..y!..w..()* 0160 1a 11 78 09 07 2c 2d 2e 2f ff..x..,-./. 01 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2930 31 32 33 34 35 36 37 38 39 40 41 42 43 44 len flags rest alignmentMAC dest MAC srctype payload [ 293.572000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:14894 00 09 00 15 55 55 57 75 55 57 11 55 51 75 15 55 71 55 77 55 55 55 55 55 1D 55 75 55 15FF FF 1F C2 1E 00 00 15 00 40 10 89 00 F0 FF 40 10 78 1E 06 1B 03 00 00 00 00 00 00 00 E0 D1 B2 00 00 00 00 0 ff ff ff ff ff ff e8 11 32 cd e2 be 08 00 45 10 2.E. 0010 01 5c 00 00 40 00 40 11 39 82 00 00 00 00 ff ff .\..@.@.9... 0020 ff ff 00 44 00 43 01 48 77 e1 01 01 06 00 bd 1c ...D.C.Hw... 0030 91 23 00 03 00 00 00 00 00 00 00 00 00 00 00 00 .#.. 0040 00 00 00 00 00 00 e8 11 32 cd e2 be 00 00 00 00 2... 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0110 00 00 00 00 00 00 63 82 53 63 35 01 01 3d 07 01 ..c.Sc5..=.. 0120 e8 11 32 cd e2 be 3c 0c 64 68 63 70 63 64 20 33 ..2dhcpcd 3 0130 2e 32 2e 33 51 1a 01 00 00 6c 69 6e 75 78 2d 73 .2.3Qlinux-s 0140 61 6d 73 75 6e 67 37 30 30 67 37 61 2e 6c 61 6e amsung700g7a.lan 0150 37 17 3a 3b 01 1c 79 21 03 0c 77 0f 06 28 29 2a 7.:;..y!..w..()* 0160 1a 11 78 09 07 2c 2d 2e 2f ff..x..,-./. 01 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2930 31 32 33 34 35 36 37 38 39 40 41 42 43 44 len flags rest alignmentMAC dest MAC srctype payload [ 296.572000] bgmac: [DBG][bgmac_dma_rx_read:328] [RX] len:14894 00 09 00 55 55 15 11 53 55 5D 75 15 55 55 55 55 55 57 51 55 11 55 55 55 55 55 55 55 D5FF FF 18 C3 1E 00 08 14 0C 40
Re: [OpenWrt-Devel] Corrupted packets with bgmac on BCM5357* devices
I want to test bcm5357 openwrt with my RT-N10U too. Which device should i choose to compile the OpenWrt, is there related patches need to use. Thank you Jiapeng 2013/9/12 Rafał Miłecki zaj...@gmail.com Some example with Wireshark output visible too. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Corrupted packets with bgmac on BCM5357* devices
2013/9/12 Jiapeng Li gaplee...@gmail.com: I want to test bcm5357 openwrt with my RT-N10U too. Which device should i choose to compile the OpenWrt, is there related patches need to use. First of all, don't top post please. I've no idea what are you asking for. You can compile OpenWrt *on* almost any architecture host. *For* what architecture you can compile OpenWrt? bcm47xx, bcm63xx, ar71xx... Just Google. If you have other questions not related to the BCM5357* and network/DMA problems, please post them in separated thread. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 00/10] Rename imx23 target to mxs and add support for I2SE's Duckbill series
Hi Zoltan, do you have had already some time to look over this series? Any objections or wishes that I could/should address? Please let me know your opinion. Thnx, Michael PS: The series is also avaiable at https://github.com/mhei/openwrt/tree/mxs Am Mittwoch, 28. August 2013, 13:08:21 schrieb Michael Heimpold: Changes from v1: - merged patches as suggested by Luka Perkov - fixed first-time network configuration for Olinuxino boards - use the green LED on Olinuxino boards as status indicator - dropped patches already applied or obsolete Michael Heimpold (10): Rename target imx23 to mxs mxs: various small fixes for packages elftosb: support static linking mxs: enable device tree support in /proc mxs: whitespace fix mxs: add basic board runtime detection support mxs: add support for I2SE's Duckbill devices mxs: add/improve image generation support uboot-envtools: add support for mxs target mxs: remove static default network configuration in image package/boot/imx-bootlets/Makefile |2 +- package/boot/uboot-envtools/Makefile |6 +- package/boot/uboot-envtools/files/mxs | 26 + package/boot/uboot-imx23/Makefile |2 +- target/linux/imx23/Makefile| 26 - target/linux/imx23/base-files/etc/inittab |3 - target/linux/imx23/config-default | 285 -- target/linux/imx23/image/Makefile | 45 - target/linux/imx23/modules.mk | 132 - .../imx23/patches/100-soc-audio-support.patch | 2842 target/linux/imx23/patches/101-soc-audio-dts.patch | 39 - target/linux/imx23/patches/105-imx23-dcp.patch | 957 --- target/linux/imx23/patches/106-add-dcp-dts.patch | 25 - target/linux/imx23/patches/110-lradc-dts.patch | 14 - target/linux/imx23/profiles/01-olinuxino.mk| 19 - target/linux/mxs/Makefile | 26 + target/linux/mxs/base-files.mk |3 + target/linux/mxs/base-files/etc/diag.sh| 35 + target/linux/mxs/base-files/etc/inittab|3 + .../mxs/base-files/etc/uci-defaults/02_network | 23 + target/linux/mxs/base-files/lib/mxs.sh | 42 + .../base-files/lib/preinit/03_preinit_do_mxs.sh|9 + target/linux/mxs/config-default| 286 ++ .../mxs/files/arch/arm/boot/dts/imx28-duckbill.dts | 118 + target/linux/mxs/image/Makefile| 69 + target/linux/mxs/modules.mk| 131 + .../linux/mxs/patches/100-soc-audio-support.patch | 2842 target/linux/mxs/patches/101-soc-audio-dts.patch | 39 + target/linux/mxs/patches/105-imx23-dcp.patch | 957 +++ target/linux/mxs/patches/106-add-dcp-dts.patch | 25 + target/linux/mxs/patches/110-lradc-dts.patch | 14 + target/linux/mxs/patches/200-duckbill.patch| 57 + target/linux/mxs/profiles/01-olinuxino.mk | 20 + target/linux/mxs/profiles/02-duckbill.mk | 20 + tools/Makefile |2 +- tools/elftosb/Makefile | 11 +- tools/elftosb/patches/003-use-ldflags.patch| 26 + 37 files changed, 4782 insertions(+), 4399 deletions(-) create mode 100644 package/boot/uboot-envtools/files/mxs delete mode 100644 target/linux/imx23/Makefile delete mode 100644 target/linux/imx23/base-files/etc/inittab delete mode 100644 target/linux/imx23/config-default delete mode 100644 target/linux/imx23/image/Makefile delete mode 100644 target/linux/imx23/modules.mk delete mode 100644 target/linux/imx23/patches/100-soc-audio-support.patch delete mode 100644 target/linux/imx23/patches/101-soc-audio-dts.patch delete mode 100644 target/linux/imx23/patches/105-imx23-dcp.patch delete mode 100644 target/linux/imx23/patches/106-add-dcp-dts.patch delete mode 100644 target/linux/imx23/patches/110-lradc-dts.patch delete mode 100644 target/linux/imx23/profiles/01-olinuxino.mk create mode 100644 target/linux/mxs/Makefile create mode 100644 target/linux/mxs/base-files.mk create mode 100644 target/linux/mxs/base-files/etc/diag.sh create mode 100644 target/linux/mxs/base-files/etc/inittab create mode 100644 target/linux/mxs/base-files/etc/uci-defaults/02_network create mode 100644 target/linux/mxs/base-files/lib/mxs.sh create mode 100644 target/linux/mxs/base-files/lib/preinit/03_preinit_do_mxs.sh create mode 100644 target/linux/mxs/config-default create mode 100644 target/linux/mxs/files/arch/arm/boot/dts/imx28-duckbill.dts create mode 100644 target/linux/mxs/image/Makefile create mode 100644 target/linux/mxs/modules.mk create mode 100644 target/linux/mxs/patches/100-soc-audio-support.patch create mode 100644 target/linux/mxs/patches/101-soc-audio-dts.patch
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
* Gui Iribarren g...@altermundi.net [12.09.2013 18:51]: in that case, you can even build a dumb cable (just pins on each side, no serial-to-usb circuit) and use it to connect two routers (i.e. one bricked, and one alive with package 'screen') , GND - GND / TX - RX / RX - TX i already thought about this and already tried it, but it didnt work. now if you write this, i will try again - had made a mistake maybe. can you add this to http://wiki.openwrt.org/doc/hardware/port.serial thank you! bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ar71xx: add support for TL-MR3040 v2 (correction)
Changed two instances of TL-MR3040 to TL-MR3040-v1 and TL-MR3040-v2, respectively. Signed-off-by: Mads Hansen d...@taba.se Index: trunk/target/linux/ar71xx/image/Makefile === --- trunk/target/linux/ar71xx/image/Makefile(revision 37950) +++ trunk/target/linux/ar71xx/image/Makefile(working copy) @@ -912,7 +912,8 @@ $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV1,tl-mr11u-v1,TL-MR11U,ttyATH0,115200,0x00110101,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR11UV2,tl-mr11u-v2,TL-MR11U,ttyATH0,115200,0x00110102,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3020,tl-mr3020-v1,TL-MR3020,ttyATH0,115200,0x3021,1,4Mlzma)) -$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3040,tl-mr3040-v1,TL-MR3040,ttyATH0,115200,0x3041,1,4Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3040V1,tl-mr3040-v1,TL-MR3040-v1,ttyATH0,115200,0x3041,1,4Mlzma)) +$(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3040V2,tl-mr3040-v2,TL-MR3040-v2,ttyATH0,115200,0x3042,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3220V2,tl-mr3220-v2,TL-MR3220-v2,ttyATH0,115200,0x3222,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLMR3420V2,tl-mr3420-v2,TL-MR3420-v2,ttyS0,115200,0x3422,1,4Mlzma)) $(eval $(call SingleProfile,TPLINK-LZMA,64kraw,TLWR703,tl-wr703n-v1,TL-WR703N,ttyATH0,115200,0x07030101,1,4Mlzma)) @@ -971,6 +972,7 @@ $(eval $(call MultiProfile,OPENMESH,OM2P MR600)) $(eval $(call MultiProfile,TEW652BRP,TEW652BRP_FW TEW652BRP_RECOVERY)) $(eval $(call MultiProfile,TLMR11U,TLMR11UV1 TLMR11UV2)) +$(eval $(call MultiProfile,TLMR3040,TLMR3040V1 TLMR3040V2)) $(eval $(call MultiProfile,TLMR3220,TLMR3220V1 TLMR3220V2)) $(eval $(call MultiProfile,TLMR3420,TLMR3420V1 TLMR3420V2)) $(eval $(call MultiProfile,TLWA801,TLWA801NV1)) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Warnung vor Lötwasser beim TL-WDR4900
On 09/12/2013 07:39 AM, John Crispin wrote: On 12/09/13 12:32, Bastian Bittorf wrote: * Steffen Hoffmannhoff...@web.de [12.09.2013 12:29]: Thank you for the translation, but 3 doesn't correlate with 'dutzende', or you have another, undisclosed source for your information? 8-) i'am involved in this special case, so i know the real situation. (somebody tends to hype here) this is a very funny thread, especially for the non-germans i think 8-) bye, bastian i can recommend this stuff - i'd simply recommend not soldering at all; you can build your serial cable with pins at the end (the same square metal pins you've been soldering all this time) and insert them into the holes on the PCB. that gets very interesting when you have more than a couple of routers. in that case, you can even build a dumb cable (just pins on each side, no serial-to-usb circuit) and use it to connect two routers (i.e. one bricked, and one alive with package 'screen') , GND - GND / TX - RX / RX - TX and then you don't even need the serial-to-USB converter, you can see the console using screen /dev/ttyS0 115200 for example (you might have to remove an /etc/inittab line to prevent the ash --login command taking control of the serial) Cheers! gui ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Developing own packages with CMake
Hi, I want to develop my own package for OpenWRT. I'm a Buildroot user though and AFAIK OpenWRT uses it heavily too. Buildroot provides a very efficient CMake integration. It provides a toolchainfile.cmake, that will be used to compile existing CMake based packages, but it can be easily used to compile the packages outside BR. I've tried to find such a file in OpenWRT, but failed. Does OpenWRT (Attitude Adjustment 12.09.1) provide such functionality? Another useful feature is The source directory override mechanism as described here: http://free-electrons.com/blog/buildroot-2011-11/ Is it planned to integrate such a feature? I've found following HOWTO for own package development and will try to adapt to CMake http://hype-free.blogspot.de/2009/04/compiling-software-for-openwrt-and.html Best regards, Yegor ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Corrupted packets with bgmac on BCM5357* devices
Hi Rafał, Thank you for your reply, but i have no idea about top post. If i do that truly, i am sorry. It will be appreciated, if you would like to tell me about how to avoid to top post Thanks again. Jiapeng 2013/9/13 Rafał Miłecki zaj...@gmail.com 2013/9/12 Jiapeng Li gaplee...@gmail.com: I want to test bcm5357 openwrt with my RT-N10U too. Which device should i choose to compile the OpenWrt, is there related patches need to use. First of all, don't top post please. I've no idea what are you asking for. You can compile OpenWrt *on* almost any architecture host. *For* what architecture you can compile OpenWrt? bcm47xx, bcm63xx, ar71xx... Just Google. If you have other questions not related to the BCM5357* and network/DMA problems, please post them in separated thread. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
