Re: [OpenWrt-Devel] Getting in touch with Felix

Hi, Even jow@openwrt and blogic@openwrt do not exist anymore as of now. Recipient address rejected: User unknown in virtual mailbox table While for example juhosg@openwrt still exists. I just hope this will not become another "ffmpeg vs libav"... Cheers, Vittorio On 05/05/2016 02:00:29

Re: [OpenWrt-Devel] [PATCH v2] firewall3: Fix multicast ICMPv6 replies not being sent by default anymore.

Hi, On 02/05/2016 21:54:06 CEST, Baptiste Jonglez wrote: On Mon, May 02, 2016 at 09:37:07PM +0200, Baptiste Jonglez wrote: On Mon, May 02, 2016 at 08:17:48PM +0200, Vittorio Gambaletta (VittGam) wrote: > Since drop_invalid has been turned on by default, ICMPv6 echo requests > to well-known

Re: [OpenWrt-Devel] [PATCH] Chaos Calmer - ramips: Fix IPv6 neighbor discovery on RT5350

On 02/05/2016 10:06:49 CEST, John Crispin wrote: On 02/05/2016 09:55, Vittorio G (VittGam) wrote: Actually there's a problem with this patch: the tabs have been converted to spaces by your mailer, so it does not apply directly... The patch on GitHub is fine by the way. Cheers, Vittorio you

Re: [OpenWrt-Devel] [PATCH] Chaos Calmer - ramips: Fix IPv6 neighbor discovery on RT5350

Actually there's a problem with this patch: the tabs have been converted to spaces by your mailer, so it does not apply directly... The patch on GitHub is fine by the way. Cheers, Vittorio On 01/05/2016 23:59:27 CEST, Vittorio G (VittGam) wrote: On 01/05/2016 23:36:05 CEST, Saverio Proto

Re: [OpenWrt-Devel] [PATCH] Chaos Calmer - ramips: Fix IPv6 neighbor discovery on RT5350

On 01/05/2016 23:36:05 CEST, Saverio Proto wrote: This patch is also available here: https://github.com/zioproto/openwrt15051-batman/commit/0281382bcaa139f0d1d3b589797af4c434747f3e commit 0281382bcaa139f0d1d3b589797af4c434747f3e Author: Saverio Proto Date: Sun May 1

Re: [OpenWrt-Devel] [PATCH 2/2] lantiq: Fix status LED on TDW89X0 after boot is completed.

On 25/04/2016 23:10:22 CEST, Martin Blumenstingl wrote: maybe you could document this in the wiki: [0] Most people check the wiki when they are looking for configuration hints like this Done: https://wiki.openwrt.org/toh/tp-link/td-w8970#leds Cheers, Vittorio

[OpenWrt-Devel] Buildbot not building all images for Lantiq XRX200

Hello, I've seen that Lantiq XRX200 trunk images are only being built for the VG3503J. Is this intended, or a mistake? Thank you. Cheers, Vittorio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] [PATCH 2/2] lantiq: Fix status LED on TDW89X0 after boot is completed.

On 25/04/2016 15:14:31 CEST, John Crispin wrote: i understand the problem, but the WPS led is for WPS and should be left free for the WPS feature eventually. so nack on this one i am afraid. Ok, thank you anyway. For the record, if anyone wants the old behaviour they just need to put this in

Re: [OpenWrt-Devel] [PATCH 2/2] lantiq: Fix status LED on TDW89X0 after boot is completed.

On 22/04/2016 08:34:41 CEST, Mathias Kresin wrote: Am 21.04.2016 um 23:43 schrieb Vittorio Gambaletta (VittGam): After recent patches, the status LED on this router would stay switched off after boot is completed. A switched off status LED often indicates a boot failure (eg. kernel panic), so

Re: [OpenWrt-Devel] [PATCH] [v3] ar71xx: Support for Ubiquiti UniFi AP AC LITE

Hi P.Wassi, The code itself does not seem to be broken. But the whitespace on the beginning of every line is missing. It is possible that your email client has mangled it. So the patch cannot be applied with the "patch" tool, since that whitespace is essential in diff files. Also, on your site

Re: [OpenWrt-Devel] [PATCH] [v3] ar71xx: Support for Ubiquiti UniFi AP AC LITE

Hello, It seems that whitespace is broken in this patch. Can you resend it, please? Thank you, Vittorio G On 20/01/2016 10:05:20 CET, p.wa...@gmx.at wrote: From: P.Wassi Add support for the Ubiquiti UniFi AP AC LITE Signed-off-by: P.Wassi --- This patch adds: * New machine type * Code for

Re: [OpenWrt-Devel] [PATCH v4 1/4] [CC] ramips: Fix whitespace in the rt3052 switch driver.

56 CET, John Crispin wrote: Hi, the patch/series does not apply to CC John On 01/01/2016 00:00, Vittorio G (VittGam) wrote: Signed-off-by: Vittorio Gambaletta <open...@vittgam.net> --- --- a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c +++ b/target/linux/ra

[OpenWrt-Devel] [PATCH v4 1/4] [CC] [RESEND] ramips: Fix whitespace in the rt3052 switch driver.

Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c +++ b/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c @@ -1417,19 +1417,19 @@ static int esw_probe(struct platform_device *pdev) }

[OpenWrt-Devel] [PATCH v4 2/4] [CC] ramips: Fix comment in rt3052 ethernet switch driver.

Line 461 is actually enabling all switch ports by setting the disable bits to 0. This needs to be done because the bootloader sets all ports to disabled by default (which is the case for at least one router based on RT5350). So, this patch fixes the comment in line 460. Signed-off-by: Vittorio

[OpenWrt-Devel] [PATCH v4 3/4] ramips: Get rt3050 ethernet ports to be disabled from the device tree.

This patch allows configuring ports to be disabled in the device tree; this saves power, since disabling ports here actually disables power to ethernet PHYs. Line 443 enables all ethernet ports, so line 486 is getting zero ports to be disabled, except for port 5 in SoCs where this is not

[OpenWrt-Devel] [PATCH v4 4/4] [CC] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/dts/HT-TM02.dts +++ b/target/linux/ramips/dts/HT-TM02.dts @@ -57,6 +57,7 @@ esw@1011 {

[OpenWrt-Devel] [PATCH v4 3/4] [CC] ramips: Get rt3052 ethernet ports to be disabled from the device tree.

This patch allows configuring ports to be disabled in the device tree; this saves power, since disabling ports here actually disables power to ethernet PHYs. Line 461 enables all ethernet ports, so line 508 is getting zero ports to be disabled, except for port 5 in SoCs where this is not

[OpenWrt-Devel] [PATCH v4 2/4] ramips: Fix comment in rt3050 ethernet switch driver.

Line 443 is actually enabling all switch ports by setting the disable bits to 0. This needs to be done because the bootloader sets all ports to disabled by default (which is the case for at least one router based on RT5350). So, this patch fixes the comment in line 442. Signed-off-by: Vittorio

[OpenWrt-Devel] [PATCH v4 1/4] [CC] ramips: Fix whitespace in the rt3052 switch driver.

Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c +++ b/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c @@ -1417,19 +1417,19 @@ static int esw_probe(struct platform_device *pdev) }

[OpenWrt-Devel] [PATCH v4 4/4] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/dts/HT-TM02.dts +++ b/target/linux/ramips/dts/HT-TM02.dts @@ -63,6 +63,7 @@ esw@1011 {

[OpenWrt-Devel] [PATCH v4 1/4] ramips: Fix documentation for the rt3050 switch driver.

The prefix used in the driver is now "mediatek" instead of "ralink". Signed-off-by: Vittorio Gambaletta --- --- /dev/null +++ b/target/linux/ramips/patches-4.3/0514-Documentation-DT-net-mediatek-fix-documentation-for-.patch @@ -0,0 +1,23 @@ +From: Vittorio Gambaletta

[OpenWrt-Devel] [PATCH] lantiq: Configure LED polarity for TDW8970 and TDW8980.

This patch configures the correct ath9k WLAN LED polarity for the TDW8970, and for the TDW8980 as well. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/lantiq/dts/TDW8970.dts +++ b/target/linux/lantiq/dts/TDW8970.dts @@ -4,8 +4,4 @@ / { model =

Re: [OpenWrt-Devel] [PATCH 5/5] lantiq: Configure LED polarity for TDW8970.

On 16 December 2015 22:12:15 CET, Mathias Kresin wrote: >The TDW8980 2.4 GHz Wireless LED is active high as well and your patch >fixed the inverse lighting. > >Would you please move the definition to the dtsi! Sure, I will update the patches then. Thanks for testing!

Re: [OpenWrt-Devel] [PATCH] lantiq: Add default LED configuration for TDW89X0.

On 16 December 2015 23:13:16 CET, Mathias Kresin wrote: >This look unnecessary to me. > >The default internet led configuration a few lines above, already adds >an internet led with exactly the same values. > >The same applies to the wifi led. I can not yet explain

[OpenWrt-Devel] [PATCH 4/5] lantiq: Configure disabled WLAN bands for TDW89X0.

The TDW8970 has a AR9381, which is the bgn 3x3:3 variant of the AR938x family. The TDW8980 has a AR9287, which is the bgn 2x2:2 variant of the AR928x family. This means that the chip for both routers is 2.4 GHz only. Anyway, the manufacturer didn't disable the 5 GHz band in the EEPROM partition

[OpenWrt-Devel] [PATCH 5/5] lantiq: Configure LED polarity for TDW8970.

This patch configures the correct ath9k WLAN LED polarity for the TDW8970. Signed-off-by: Vittorio Gambaletta --- The TDW8970 LED is active high, but I'm not sure about the TDW8980 as I don't have one. If the TDW8980 LED is active high as well, this can be added to

[OpenWrt-Devel] [PATCH 2/5] ath9k: Allow configuration of LED polarity in platform data.

Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/generic/files/include/linux/ath9k_platform.h +++ b/target/linux/generic/files/include/linux/ath9k_platform.h @@ -36,6 +36,7 @@ struct ath9k_platform_data { bool tx_gain_buffalo; bool disable_2ghz;

[OpenWrt-Devel] [PATCH 3/5] lantiq: Allow configuration of ath9k disabled bands and LED polarity from the device tree.

Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/lantiq/patches-4.1/0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch +++ b/target/linux/lantiq/patches-4.1/0035-owrt-lantiq-wifi-and-ethernet-eeprom-handling.patch @@ -51,13 +51,14 @@ Signed-off-by: John

[OpenWrt-Devel] [PATCH 1/5] ath9k: Pass LED polarity to ath_create_gpio_led when initializing the LEDs.

Signed-off-by: Vittorio Gambaletta --- --- a/package/kernel/mac80211/patches/530-ath9k_extra_leds.patch +++ b/package/kernel/mac80211/patches/530-ath9k_extra_leds.patch @@ -159,7 +159,7 @@ + trigger = ieee80211_get_radio_led_name(sc->hw); -

[OpenWrt-Devel] [PATCH] lantiq: Fix LED handling.

- Use common OpenWrt blink patterns instead of custom ones - Add preinit_regular hook - Handle the TDW89X0 that does not have a configurable power LED Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/lantiq/base-files/etc/diag.sh +++

[OpenWrt-Devel] [PATCH] lantiq: Add default LED configuration for TDW89X0.

Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/lantiq/base-files/etc/board.d/01_leds +++ b/target/linux/lantiq/base-files/etc/board.d/01_leds @@ -38,6 +38,10 @@ BTHOMEHUBV5A) ucidef_set_led_netdev "internet" "internet" "soc:blue:broadband" "pppoa-wan"

[OpenWrt-Devel] [PATCH v3 3/3] [CC] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- This is a backport of the patch for trunk. --- a/target/linux/ramips/dts/HT-TM02.dts +++ b/target/linux/ramips/dts/HT-TM02.dts @@

[OpenWrt-Devel] [PATCH v3 2/3] ramips: Get ethernet ports to be disabled from the device tree.

Line 461 is actually enabling all switch ports, so line 508 is always getting zero ports to be disabled (except for port 5 in SoCs where this is not implemented, as it will be sticky disabled in register POC0). Also, the bootloader on some routers sets all ports to disabled (which is the case

[OpenWrt-Devel] [PATCH v3 1/3] ramips: Fix whitespace in the switch driver.

Signed-off-by: Vittorio Gambaletta --- Please apply to both trunk and CC. --- a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c +++ b/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c @@ -1417,19 +1417,19 @@ static int esw_probe(struct

[OpenWrt-Devel] [PATCH v3 3/3] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- Please apply to trunk only, a backport will follow. --- a/target/linux/ramips/dts/HT-TM02.dts +++

Re: [OpenWrt-Devel] [PATCH 1/3] ramips: Fix whitespace in the switch driver.

Hi, On 11/12/2015 10:32:08 CET, John Crispin wrote: 1) the subject and description dont match. Well, the description is an addition to the subject, but okay. 2) why would we want to intermingle the portmap and register init variables. they are 2 different things. imho that is not correct

Re: [OpenWrt-Devel] [PATCH] ramips: Fix failsafe for HT-TM02.

On 11/12/2015 15:02:43 CET, John Crispin wrote: On 11/12/2015 14:48, Vittorio G (VittGam) wrote: We cannot use board.json data here: this code is called before mounting the rootfs, in the preinit. we can. i just spoke with jow and we will add a codepath to failsafe to probe board.json

Re: [OpenWrt-Devel] [PATCH 3/3] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Hi, On 11/12/2015 12:29:00 CET, John Crispin wrote: On 05/12/2015 12:04, Vittorio G (VittGam) wrote: esw@1011 { ralink,portmap = <0x10>; + ralink,portdisable = <0x2f>; }; i think it makes more sense to derive 0x2f from the

Re: [OpenWrt-Devel] [PATCH] ramips: Fix failsafe for HT-TM02.

Hi, On 11/12/2015 14:32:45 CET, John Crispin wrote: hardcoding the board id here is not a good idea. we should rather use the board.json data to probe if a switch is registered. if not we dont apply the hack. i'll ask jow to tell us how to probe for a switch. We cannot use board.json data

Re: [OpenWrt-Devel] [PATCH 1/3] ramips: Fix whitespace in the switch driver.

Hi, On 11/12/2015 15:12:32 CET, Arjen de Korte wrote: Because there are two __be32's used to fetch data from the device tree; one is used only once for the portmap, while the other is used three times, for the two registers and for the led_polarity. Maybe the name should be tmp instead, but I

Re: [OpenWrt-Devel] [PATCH v2 2/3] ramips: Get ethernet ports to be disabled from the device tree.

On 12/12/2015 08:23:24 CET, John Crispin wrote: tl;dr It does not change current behaviour because all ports get enabled before. if you want this merged you will need to add a port_disabled variable I don't like it this way, but okay I will add that variable.

[OpenWrt-Devel] [PATCH v2 1/3] ramips: Fix whitespace in the switch driver.

Signed-off-by: Vittorio Gambaletta --- At the end, let's leave port_map and reg_init, and in the next patch reuse port_map for port_disable too. Please apply to both trunk and CC. --- a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c +++

[OpenWrt-Devel] [PATCH v2 2/3] ramips: Get ethernet ports to be disabled from the device tree.

Line 461 is actually enabling all switch ports, so line 508 is always getting zero ports to be disabled (except for port 5 in SoCs where this is not implemented, as it will be sticky disabled in register POC0). Also, the bootloader on some routers sets all ports to disabled (which is the case

[OpenWrt-Devel] [PATCH v2 3/3] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/dts/HT-TM02.dts +++ b/target/linux/ramips/dts/HT-TM02.dts @@ -63,6 +63,7 @@ esw@1011 {

[OpenWrt-Devel] [PATCH v2 3/3] [CC] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/dts/HT-TM02.dts +++ b/target/linux/ramips/dts/HT-TM02.dts @@ -57,6 +57,7 @@ esw@1011 {

Re: [OpenWrt-Devel] [PATCH v2 2/3] ramips: Get ethernet ports to be disabled from the device tree.

Hi, On 12/12/2015 07:20:43 CET, John Crispin wrote: On 12/12/2015 07:19, John Crispin wrote: why a semicolon ? i believe a "," needs to be added instead please also remove the superfluous "," while you are at it to make the comment orthographically correct. it seems to be have been copied from

Re: [OpenWrt-Devel] [PATCH v2 3/3] [CC] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Hi, On 12/12/2015 07:16:09 CET, John Crispin wrote: patch 1/3 and 3/3 seem to be missing for this eries Patches 1/3 and 2/3 are the same for trunk and CC, and there is a comment saying that on those patches. Patch 3/3 would not apply cleanly to CC instead, so that's why it's splitted.

Re: [OpenWrt-Devel] [PATCH v6 5/6] ar71xx: scan nand ubi partition for ath9k eeprom files

On 05/12/2015 23:48:07 CET, Christian Lamparter wrote: mtd=$(find_mtd_chardev $part) [ -n "$mtd" ] || \ - ath9k_eeprom_die "no mtd device found for partition $part" + mtd="/dev/$(nand_find_volume $ubidev $part)" + [ -n "$mtd" ] || \ +

[OpenWrt-Devel] [PATCH 1/3] ramips: Fix whitespace in the switch driver.

Also avoid using two variables where one can be used. Signed-off-by: Vittorio Gambaletta --- Please apply to both trunk and CC. --- a/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c +++

[OpenWrt-Devel] [PATCH 3/3] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/dts/HT-TM02.dts +++ b/target/linux/ramips/dts/HT-TM02.dts @@ -63,6 +63,7 @@ esw@1011 {

[OpenWrt-Devel] [PATCH 3/3] [CC] ramips: Disable all ethernet ports except port 4 on HT-TM02.

Port 4 is the only ethernet port on this router, so disable all other PHYs in order to save power. Signed-off-by: Vittorio Gambaletta --- --- a/target/linux/ramips/dts/HT-TM02.dts +++ b/target/linux/ramips/dts/HT-TM02.dts @@ -57,6 +57,7 @@ esw@1011 {

[OpenWrt-Devel] [PATCH] ramips: Fix failsafe for HT-TM02.

The failsafe VLAN workaround is not needed on HT-TM02 (RT5350); it actually breaks failsafe since this router has only one port and it is 4 and not 0. Anyway, it seems that the workaround is still needed for other routers (see https://patchwork.ozlabs.org/patch/424017/ for a previous attempt at

[OpenWrt-Devel] [PATCH 2/3] ramips: Get ethernet ports to be disabled from the device tree.

Line 461 is actually enabling all switch ports, so line 508 is always getting zero ports to be disabled (except for port 5 in SoCs where this is not implemented, as it will be sticky disabled in register POC0). Also, the bootloader on some routers sets all ports to disabled (which is also the

Re: [OpenWrt-Devel] Removing Telnet

Il 08.09.2015 10:15 Steven Barth ha scritto: as of https://dev.openwrt.org/changeset/46809 telnet is no longer part of the base images. As a replacement, it is now possible to login to the root- account via SSH without a password prompt whenever no root password is set, e.g. after a flash

Re: [OpenWrt-Devel] Removing Telnet

Il 08.09.2015 20:34 Vittorio G (VittGam) ha scritto: Maybe it would just be better to set the default root password to 'openwrt' or 'insecure' or 'change_me!'? Maybe along with a preauthentication banner that tells the user about the default password and the fact that it should be changed

Re: [OpenWrt-Devel] Removing Telnet

Il 08.09.2015 21:31 Michael Heimpold ha scritto: I also remember that "long time ago" there were issues because of not enough entropy available on embedded devices. Is this still an issue? Should only delay the time when logging in is possible, right? The dropbearkey key generation will delay

Re: [OpenWrt-Devel] Fwd: Removing Telnet

Il 08.09.2015 18:31 Janusz Dziemidowicz ha scritto: SSH time can be greatly reduced by using ECDSA host key. Dropbear can be compiled with ECDSA support, however: - it is disabled by default in OpenWRT - startup script only generates RSA/DSA host keys, ECDSA host key must be generated manually

Re: [OpenWrt-Devel] Fwd: Removing Telnet

Il 08.09.2015 20:06 Sami Olmari ha scritto: Does Dropbeard support ether? I know OpenSSH does, but default installation does not use that. I just checked the changelog[1] and I remembered wrong about chacha20. But it does support curve25519 indeed; it was added along ECDSA: 2013.61test -

Re: [OpenWrt-Devel] fcc hardware lockdown

Il 03.09.2015 16:59 demos ha scritto: That is a possible list for further coordination of resistance: http://lists.prplfoundation.org/cgi-bin/mailman/listinfo/fcc Here is a wiki page from LibrePlanet that is explaining the problem and its conseguences in depth and tries to coordinate

Re: [OpenWrt-Devel] Huawei 3372 NCM support on CC not working

Hello, Are we talking about E3372h or E3372s? I've got E3372h working by doing this: echo 6000 /sys/class/net/wwan0/cdc_ncm/tx_max echo 0 /sys/class/net/wwan0/cdc_ncm/min_tx_pkt But it seems it didn't help an E3372s owner unfortunately. :/ My stick is a E3372h-153 with firmware

Re: [OpenWrt-Devel] [PATCH] ramips: Fix failsafe switch workaround for RT5350 introduced in r42179.

Il 10.03.2015 20:42 John Crispin ha scritto: we can hook this up with the board detect code. i'll put it on my todo list. might take a bit till i find the time That would be great! By the way, we should test if recent revisions fix the checksum issue so that we can completely remove this

Re: [OpenWrt-Devel] [PATCH] ramips: Fix failsafe switch workaround for RT5350 introduced in r42179.

Il 10.03.2015 14:18 John Crispin ha scritto: hi can you send a version that has the pattern shown below please and 0 1 2 3 4 5 6 is wrong, exclude the wan port from the list please. John The problem is that it's not easy to determine what number the LAN or WAN port(s) is/are. On

[OpenWrt-Devel] [PATCH] ar71xx: Fix board detection for the TP-LINK TL-MR13U.

Signed-off-by: Vittorio Gambaletta open...@vittgam.net diff --git a/target/linux/ar71xx/base-files/lib/ar71xx.sh b/target/linux/ar71xx/base-files/lib/ar71xx.sh index 52acc6b..fb047b4 100755 --- a/target/linux/ar71xx/base-files/lib/ar71xx.sh +++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh @@

[OpenWrt-Devel] [PATCH] ramips: Fix failsafe switch workaround for RT5350 introduced in r42179.

This patch fixes the failsafe switch workaround to avoid soft-bricking routers where the only exposed Ethernet port is not 0 (it is 4 for the HT-TM02 for instance). This is a follow-up of http://patchwork.ozlabs.org/patch/424017/ (sorry for the delay). Signed-off-by: Vittorio Gambaletta

[OpenWrt-Devel] [PATCH] ar71xx: Fix LED polarity for the TP-LINK TL-MR13U.

Please also backport to Barrier Breaker (this same patch applies there too). Signed-off-by: Vittorio Gambaletta open...@vittgam.net diff --git a/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-mr13u.c b/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-mr13u.c index 8b03645..84b6937 100644

[OpenWrt-Devel] [PATCH] [BB] Backport: ar71xx: Fix board detection for the TP-LINK TL-MR13U.

Signed-off-by: Vittorio Gambaletta open...@vittgam.net --- a/target/linux/ar71xx/base-files/lib/ar71xx.sh +++ b/target/linux/ar71xx/base-files/lib/ar71xx.sh @@ -646,7 +646,7 @@ *TL-MR11U) name=tl-mr11u ;; - *TL-MR13U) + *TL-MR13U v1)

Re: [OpenWrt-Devel] [PATCH] ramips: revert failsafe switch workaround for RT5350 introduced in r42179.

Hi, Il 17.01.2015 14:55 John Crispin ha scritto: On 25/12/2014 02:29, Vittorio G (VittGam) wrote: It is not needed anymore as TCP packets get passed correctly now even when VLAN is disabled. are you sure this is the case for all rt3x5x, rt5350 and mt7628 units ? I've tested it on my

Re: [OpenWrt-Devel] [PATCH] ramips: HooToo HT-TM02 factory image generation.

Il 09.01.2015 16:17 Florian Fainelli ha scritto: What about a statically linked binary at least? Of course I've missed the obvious thing here. :) Thanks for the suggestion! I'm going to try this as soon as I've some spare time (in a week or so). Otherwise the code is on my github if you

Re: [OpenWrt-Devel] [PATCH] ramips: HooToo HT-TM02 factory image generation.

Hi, What is the reason has this been rejected? Do I need to change something? Thanks, Vittorio Il 28.12.2014 13:34 Vittorio G (VittGam) ha scritto: The mkhootoofw.sh is a shell script, because official factory images are shell scripts by themselves, and it made more sense to me to just use

Re: [OpenWrt-Devel] Strange LED behavior on ramips

Hi everybody, Is nobody else experiencing this on their ramips/rt5350-based router? Cheers, Vittorio G Il 25.12.2014 02:55 Vittorio G (VittGam) ha scritto: Hi everybody, I've got some HooToo HT-TM02 rt5350-based routers, and I've noticed a quite weird thing with LEDs. It seems that the LED

[OpenWrt-Devel] [PATCH] [RESEND] [v2] base-files: Use 200ms LED timing as before for the new phase preinit_regular.

This restores normal pre-r43715 200ms blink-period for the System LED we're all accustomed to see while our OpenWrt routers are booting. Failsafe possibility will now be signalled with a new 100ms blinking, which is easily recognizable from the normal 200ms booting. So no existing user will be

Re: [OpenWrt-Devel] [PATCH] ramips: HooToo HT-TM02 factory image generation.

Il 09.01.2015 10:48 John Crispin ha scritto: +mkhootoofw.sh $(DL_DIR)/hootoo_mtd_writer $(call sysupname,$(1),$(2)) $(call imgname,$(1),$(2))-factory.bin +endef +BuildFirmware/HooToo8M/initramfs=$(call BuildFirmware/OF/initramfs,$(1),$(2),$(3)) + this bit is really bad. you cannot install

Re: [OpenWrt-Devel] [PATCH] base-files: Enhancements to /etc/profile.

Il 06.01.2015 12:18 Felix Fietkau ha scritto: On 2014-12-25 02:28, Vittorio G (VittGam) wrote: - Update terminal window title with current directory and hostname like on Ubuntu. - Add an optional colored prompt, in case user wants to enable it. - Add ll, an useful alias to ls. Signed-off

Re: [OpenWrt-Devel] [PATCH] base-files: Use the same LED timing as before for preinit_regular.

Il 29.12.2014 09:04 Rafał Miłecki ha scritto: 1) I think that most OpenWrt users, like me, are accustomed to see a led pattern of 200ms. I thought it was a bad flash or something else bad when I've seen that 500ms blinking... Is there any reason for that? Was 200ms ever used or documented by

Re: [OpenWrt-Devel] [PATCH] ramips: Fix HooToo HT-TM02 support.

Hi, Il 25.12.2014 12:37 Paul Fertser ha scritto: Hello, Few comments from a person that doesn't own this device (but owns an MPR-A1 clone). Vittorio G (VittGam) writes: - Remove unneeded VLAN now that the ethernet driver is fixed and TCP packets get passed correctly now. (This router only

Re: [OpenWrt-Devel] [PATCH] ramips: Fix HooToo HT-TM02 support.

Il 25.12.2014 13:26 Paul Fertser ha scritto: On Thu, Dec 25, 2014 at 12:46:20PM +0100, Vittorio G (VittGam) wrote: And LAN port is 4, it can be seen from running: swconfig dev switch0 show. Hm, ok, sure. Sorry for the noise. No problem :) Also this is not exactly an MPR-A1 clone

[OpenWrt-Devel] [PATCH] base-files: Enhancements to /etc/profile.

- Update terminal window title with current directory and hostname like on Ubuntu. - Add an optional colored prompt, in case user wants to enable it. - Add ll, an useful alias to ls. Signed-off-by: Vittorio Gambaletta open...@vittgam.net diff --git a/package/base-files/files/etc/profile

[OpenWrt-Devel] [PATCH] base-files: Use the same LED timing as before for preinit_regular.

Signed-off-by: Vittorio Gambaletta open...@vittgam.net diff --git a/package/base-files/files/lib/functions/leds.sh b/package/base-files/files/lib/functions/leds.sh index 4ac8145..d4d4512 100644 --- a/package/base-files/files/lib/functions/leds.sh +++

[OpenWrt-Devel] [PATCH] ramips: revert failsafe switch workaround for RT5350 introduced in r42179.

It is not needed anymore as TCP packets get passed correctly now even when VLAN is disabled. This piece of code also broke routers where the LAN port is not wired to port 0 of the internal switch. Signed-off-by: Vittorio Gambaletta open...@vittgam.net diff --git

[OpenWrt-Devel] [PATCH] ramips: base-files: Whitespace fixes.

Signed-off-by: Vittorio Gambaletta open...@vittgam.net diff --git a/target/linux/ramips/base-files/etc/board.d/01_leds b/target/linux/ramips/base-files/etc/board.d/01_leds index 9c49c5c..405a6c0 100755 --- a/target/linux/ramips/base-files/etc/board.d/01_leds +++

[OpenWrt-Devel] [PATCH] ramips: Fix HooToo HT-TM02 support.

- Fix LED definitions. - Add mode-switch slider definition (at GPIO 14). - Remove unneeded VLAN now that the ethernet driver is fixed and TCP packets get passed correctly now. (This router only has one port.) - Fix LAN port MAC address, which is defined in the factory partition as WLAN MAC

Re: [OpenWrt-Devel] [PATCH v2 3/3] hostapd: Add uapsd option to netifd.sh

this would be fine? Cheers, Vittorio Il 18.10.2014 21:37 Felix Fietkau ha scritto: On 2014-10-14 20:05, Vittorio G (VittGam) wrote: The uapsd option sets the uapsd_advertisement_enabled flag in hostapd, only if the phy actually supports the option. Signed-off-by: Vittorio Gambaletta

Re: [OpenWrt-Devel] [PATCH v2 1/3] mac80211, hostapd: Fix hostapd_set_bss_options function call in mac80211.sh and its definition in netifd.sh

Hi Felix, Yes, they will not be used again with the to-be-modified http://patchwork.openwrt.org/patch/6468/ [2] patch. I will send the new patch along with the other one. Cheers, Vittorio Il 18.10.2014 21:35 Felix Fietkau ha scritto: On 2014-10-14 20:04, Vittorio G (VittGam) wrote

Re: [OpenWrt-Devel] [PATCH] Add u-APSD and WPA-PSK-file options to hostapd

I'm sorry, I've sent the wrong diff. Actually the code is right, but the diff is based on the root filesystem and not on the source repo. I'm going to send an updated patch (actually, two patches, so it is cleaner :) ). Regards, Vittorio G ___

[OpenWrt-Devel] [PATCH v2 1/3] mac80211, hostapd: Fix hostapd_set_bss_options function call in mac80211.sh and its definition in netifd.sh

- Fix the call to hostapd_set_bss_options in mac80211.sh, since $vif is not defined in the calling context, and $phy was not being passed to the function. - Swap $vif and $phy in hostapd_set_bss_options, to be coherent with the old function with the same name defined in the hostapd-common-old

[OpenWrt-Devel] [PATCH v2 3/3] hostapd: Add uapsd option to netifd.sh

The uapsd option sets the uapsd_advertisement_enabled flag in hostapd, only if the phy actually supports the option. Signed-off-by: Vittorio Gambaletta open...@vittgam.net --- package/network/services/hostapd/files/netifd.sh |9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-)

[OpenWrt-Devel] [PATCH v2 2/3] hostapd: Add wpa_psk_file option to netifd.sh

The wpa_psk_file option offers the possibility to use a different WPA-PSK key for each client. The directive points to a file with the following syntax: mac_address wpa_passphrase_or_hex_key Example: 00:11:22:33:44:55 passphrase_for_client_1 00:11:22:33:44:67 passphrase_for_client_2

[OpenWrt-Devel] [PATCH] Fix LED definitions for the DRAGINO2 board

This patch fixes LED definitions for the DRAGINO2 board. 1. It renames the Router/USB led to System, as it is now marked SYS on the board. 2. It gives control of the LAN and WAN leds and some other GPIOs to Linux. 3. It fixes the active_low property for the LAN and WAN leds. 4. It sets up WLAN,

[OpenWrt-Devel] [PATCH] Add u-APSD and WPA-PSK-file options to hostapd

This patch adds uapsd and wpa_psk_file options to hostapd. It also fixes the hostapd_set_bss_options call in mac80211.sh. The uapsd option sets the uapsd_advertisement_enabled flag in hostapd, only if the adapter actually supports the option. The wpa_psk_file offers the possibility to use a

Re: [OpenWrt-Devel] [PATCH] [authsae] Fix 802.11s authsae support in netifd

P.s.: This would fix ticket #15283. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] hostadp/netifd Full Dynamic VLAN support

Hi Joseph, Thank you for the patch! But there is an error here: On Mar 3, 2014 5:59 PM, Joseph CG Walker joe+open...@chubbypenguin.net wrote: +define Package/hostpad-common/conffiles +/etc/config/hostpad.vlan +endef Hostpad instead of hostapd. ;) Regards, Vittorio G

[OpenWrt-Devel] [PATCH] Fix regression in busybox sysntpd init when specifying more than one ntp server in the config file.

Hi, This patch fixes a regression introduced with r38787. Before patching: /usr/sbin/ntpd -n -l -p server1 server2 server3 server4 After patching: /usr/sbin/ntpd -n -l -p server1 -p server2 -p server3 -p server4 Signed-off-by: Vittorio Gambaletta open...@vittgam.net --- ---

Re: [OpenWrt-Devel] USB instabilities on Atheros AR9344

Hello Kristian, On 29 Nov 2013 16:41, Kristian Evensen kristian.even...@gmail.com wrote: Hello, I am currently working on an embedded project based on the Atheros AR9344 SoC. As a prototype device, we are using the TP-Link TL-WDR4300 router (http://wiki.openwrt.org/toh/tp-link/tl-wdr4300)

Re: [OpenWrt-Devel] USB instabilities on Atheros AR9344

On 29 Nov 2013 18:56, Vittorio G (VittGam) open...@vittgam.net wrote: Also it could be a defective router; I once had a defective TL-MR3020 (AR9330-based) router that crashed on a 3G dongle with many different hubs and power adapters. I bought another router of the same model but more recent

[OpenWrt-Devel] [PATCH] Add require_ht param support to mac80211 uci config

Hi, This patch adds require_ht parameter support to mac80211 uci config. After applying this patch, the require_ht parameter can be used in the wifi-device section like this: config wifi-device 'radio0' option type 'mac80211' option channel '13' option macaddr

[OpenWrt-Devel] [PATCH] Add support for WIFI button on tp-link tl-mr3220v2

Hi, The TP-LINK TL-MR3220 v2 has a button on the left side labeled WIFI. This is GPIO 24. This patch adds the support for this button. Signed-off-by: Vittorio Gambaletta open...@vittgam.net --- --- trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-tl-wr741nd-v4.c 2012-12-19