The P2812HNU-F3 doesn't have usb leds. Only the P2812HNU-F1 has those
leds.
Reported-by: Sylwester Petela
Signed-off-by: Mathias Kresin
---
Hi John,
I received the report yesterday and till now, I didn't had the time to
send a v3 "switch to devicename:colour:function namin
The P2812HNU-F3 doesn't have usb leds. Only the P2812HNU-F1 has those
leds.
Reported-by: Sylwester Petela
Signed-off-by: Mathias Kresin
---
Changes in v2:
- change the leds device prefix as well
target/linux/lantiq/dts/P2812HNUF1.dts | 18 ++
target/linux/lanti
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/dts/TDW8980.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/lantiq/dts/TDW8980.dts
b/target/linux/lantiq/dts/TDW8980.dts
index 0bcca6e..8a07a5c 100644
--- a/target/linux/lantiq/dts/TDW8980.dts
+++ b
nally, even
experienced users are not aware that they have to remove the annex
option to get their VDSL2 line working and as shown by this patch it
doesn't need to be that "complicated".
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/files/dsl_control | 16
Commit r47934 removed the comment about G.992.4 support, but enabled
G.992.4 Annex I without mention it (bit 6 of XTSE octet 5 [ITU-T
G.997.1 (06/2012) - section 7.3.1.1.1].
To my knowledge Annex I is not supported by the firmware.
Signed-off-by: Mathias Kresin
---
package/network/config/ltq
This way we can drop the call to sed.
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/files/dsl_control | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/package/network/config/ltq-vdsl-app/files/dsl_control
b/package/network/config/ltq-vdsl
tone_adsl_av and tone_vdsl_av with the old
lowlevel settings.
Signed-off-by: Mathias Kresin
---
I've done some tests to see in which situations the tone setting is
required. In cases no tone is specified, the tone is used according to
the loaded firmware or set by the loaded firmware.
Using a d
r47933 revealed that the driver/app in combination with the chosen
firmware does a good job in selecting a working xtse.
Use this probing mode if no annex is specified.
Signed-off-by: Mathias Kresin
---
Since a predefined annex isn't required, what about using 'auto' when
creat
993.5 line working using a custom xDSL firmware.
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/files/dsl_control | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/package/network/config/ltq-vdsl-app/files/dsl_control
b/package/network/config/ltq
Signed-off-by: Mathias Kresin
---
.../lantiq/base-files/lib/functions/lantiq_dsl.sh | 30 ++
1 file changed, 30 insertions(+)
diff --git a/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh
b/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh
index 60ace44
Signed-off-by: Mathias Kresin
---
.../lantiq/base-files/lib/functions/lantiq_dsl.sh | 67 ++
1 file changed, 67 insertions(+)
diff --git a/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh
b/target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh
index ec035df
Signed-off-by: Mathias Kresin
---
target/linux/lantiq/base-files/etc/board.d/02_network | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/target/linux/lantiq/base-files/etc/board.d/02_network
b/target/linux/lantiq/base-files/etc/board.d/02_network
index 8fc0835..15b1f8c
Am 29.12.2015 um 22:34 schrieb Hauke Mehrtens:
Hi,
On 12/29/2015 09:56 PM, Mathias Kresin wrote:
Commit r47934 removed the comment about G.992.4 support, but enabled
G.992.4 Annex I without mention it (bit 6 of XTSE octet 5 [ITU-T
G.997.1 (06/2012) - section 7.3.1.1.1].
You are unsettling
nally, even
experienced users are not aware that they have to remove the annex
option to get their VDSL2 line working and as shown by this patch it
doesn't need to be that "complicated".
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/files/dsl_control | 19 ++
This way we can drop the call to sed.
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/files/dsl_control | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/package/network/config/ltq-vdsl-app/files/dsl_control
b/package/network/config/ltq-vdsl
r47933 revealed that the driver/app in combination with the chosen
firmware does a good job in selecting a working xtse.
Use this probing mode if no annex is specified.
Signed-off-by: Mathias Kresin
---
Since a predefined annex isn't required, what about using 'auto' when
creat
Changes in v2:
- dropped "ltq-vdsl-app: disable Annex I" patch, this one was wrong
Mathias Kresin (5):
ltq-vdsl-app: use the final xtse format
ltq-vdsl-app: add/enable missing G.993.2 XTSE bits
ltq-vdsl-app: let the driver/app probe the xtse on missing annex
ltq-vdsl-app: enab
993.5 line working using a custom xDSL firmware.
Signed-off-by: Mathias Kresin
---
package/network/config/ltq-vdsl-app/files/dsl_control | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/package/network/config/ltq-vdsl-app/files/dsl_control
b/package/network/config/ltq
tone_adsl_av and tone_vdsl_av with the old
lowlevel settings.
Signed-off-by: Mathias Kresin
---
I've done some tests to see in which situations the tone setting is
required. In cases no tone is specified, the tone is used according to
the loaded firmware or set by the loaded firmware.
Using a d
Am 31.12.2015 um 10:01 schrieb John Crispin:
On 30/12/2015 21:59, Mathias Kresin wrote:
According to ITU-T G.997.1 Amendment 2 (04/2013) section 2.1, bit 3 of
XTSE octet 8 either allow or denies the initialization of G.993.5.
Even if the current redistributable xDSL firmware doesn't in
Am 31.12.2015 um 08:12 schrieb John Crispin:
Hi
On 31/12/2015 01:10, Martin Blumenstingl wrote:
+
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4,2,0)
+#include
+#else
#include
+#endif
please just drop the old code. there is no need to be compatible to old
kernels.
John
I guess we
en checking the history of the files that I relicense, there are
three more people that should be added to the CC-list (INAGAKI
Hiroshi, Mathias Kresin and Petr Štetiar). I have done so now, thanks
for spotting this and the mistake was of course not intentional.
BR,
Kristian
I'm fine with re
Hey Petr,
find some comments inline.
10/08/2019 11:58, Petr Štetiar:
Hi,
one of the topics discussed during recent Hamburg meeting was "Review base
packages"[1], where we simply talked about:
* lack of formal definition for a base package
* transfer of base packages which don't fit formal
02/08/2019 11:57, Birger Koblitz:
lantiq: use gpio_hog instead of gpio-export
The `gpio-export` functionality is a hack for
missing kernel functionality, which was rejected in upstream kernel long
time
ago, for details see this email
http://lists.infradead.org/pipermail/openwrt-devel/2019-Februa
02/08/2019 11:58, Birger Koblitz:
ramips: use gpio_hog instead of gpio-export
The `gpio-export` functionality is a hack for
missing kernel functionality, which was rejected in upstream kernel long
time
ago, for details see this email
http://lists.infradead.org/pipermail/openwrt-devel/2019-Februa
10.08.2018 23:24, Christian Lamparter:
This patch copies over the MAC patching helper functions from lantiq's
target/linux/lantiq/base-files/etc/hotplug.d/firmware/12-ath9k-eeprom
file.
Not all vendors bothered to write the correct MAC addresses for the
ath9k wifi into the calibration data. And
13.08.2018 08:23, John Crispin:
Hi
this following chunk need to be annotated and sent upstream. also using
initvals might not be the best option. please also check if there is a
binding doc and add this new property.
You might want to name the property "lines-initial-states" as defined
for
2018-08-13 18:28 GMT+02:00 Dmitry Tunin :
> Add support for the ar71xx supported Tp_link MR-3040 v2 to ath79.
>
> Signed-off-by: Dmitry Tunin
> ---
> .../linux/ath79/base-files/etc/board.d/02_network | 1 +
> .../linux/ath79/dts/ar9331_tplink_tl-mr3040-v2.dts | 161
> +
>
one board.
Fixes: FS#1664
Signed-off-by: Mathias Kresin
---
.../linux/generic/files/drivers/net/phy/ar8327.c | 42 +-
.../linux/generic/files/drivers/net/phy/ar8327.h | 21 ---
2 files changed, 1 insertion(+), 62 deletions(-)
diff --git a/target/linux/generic/fil
Hey Christian,
I found something to nitpick about. Find my comments inline.
Mathias
17.08.2018 14:06, Christian Lamparter:
This patch ports over support for the device from ar71xx.
SOC:AR7370 (Wasp - AR9344 rev2 0001974c)
RAM:Winbond W9725G6KB-25 32MiB
FLASH: Winbond 25Q64FVSIG 8MiB
17.08.2018 18:36, Christian Lamparter:
TP-Link Archer C7 v1 is a dual band router
based on Qualcomm/Atheros QCA9558 + QCA9880.
Specification:
- 720 MHz CPU
- 128 MB of RAM (Various chips)
- 8 MB of FLASH (Various chips)
- SoC QCA9558 integrated 3T3R 2.4 GHz Wi-Fi
- minipcie slot with
08/17/2018 09:45 PM, Martin Blumenstingl:
On Thu, Aug 16, 2018 at 5:06 AM Chuanhong Guo wrote:
Signed-off-by: Chuanhong Guo
---
RFC:
Previous discussion about this patch can be found on GitHub PR#1271.
This patch applies correct interface mode to MII0/1_CNTL register at 0x1807/
0x18070004
19.08.2018 09:02, Chuanhong Guo:
Signed-off-by: Chuanhong Guo
Please add a commit message. I'm sure you explained the issue and your
fix somewhere. Not sure if I saw it in the forum or somewhere on github.
Good commit messages serve at least three important purposes:
- To speed up the rev
18.08.2018 14:01, David Bauer:
Sysupgrading to ath79 from ar71xx currently fails because of mismatching
supported_devices. ar71xx is expecting "tl-mr3020" which is missing in
the ath79 image. Upgrading from ath79 is unaffected, as the image
contains the old string for ar71xx and the new one comin
2018-08-19 14:52 GMT+02:00 Chuanhong Guo :
> I've just noticed that Image metadata isn't required on ar71xx so at
> least fot TP-LINK devices ar71xx accept factory firmware.
Yes it isn't required (enforced) for ar71xx. But if present, the
metadata is validated. And all ath9 images should have imag
2018-08-19 15:47 GMT+02:00 Chuanhong Guo :
> These lines are coming from ar71xx to allow using sysupgrade to
> switch from ar71xx to ath79. But a sysupgrade with config preserved
> won't work since some of the config files are incompatible.
To be honest, I don't see that your patch really fixes th
hat
the contributor considers the way to go is.
I wanted to make this RFC on mailing list but then I
think this discussion will end up nowhere :(
So...This patch can be dropped as it improved nothing...
Marked as rejected
Mathias
Dmitry Tunin 于2018年8月19日周日 下午11:40写道：
вс, 19 авг. 2018
27.08.2018 22:22, Hartmut Knaack:
Mathias Kresin would have been the one to CC, as he contributed that code.
I just added him now.
Please don't top post! It's a pain to follow the conversation this way.
Thanks a lot for fixing my mess. The patch is applied to master and the
18.
27.08.2018 14:26, wellnw:
This patch adds supports for GL-X1200.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
- USB: 1x USB 2.0 port
- Button: 1x reset button
- LED: 8x LEDS
Hey Kyson Lok,
find some comments inline.
Mathias
04.09.2018 13:55, Kyson Lok:
Add support the ar71xx supported GL.iNet GL-MIFI to ath79.
Signed-off-by: Kyson Lok
---
target/linux/ath79/base-files/etc/board.d/01_leds | 5 +
.../linux/ath79/base-files/etc/board.d/02_network | 3 +-
Hey Daniel,
12.09.2018 04:24, Daniel F. Dickinson:
Hi,
I'm having trouble finding a concise summary of what is the policy for
using multiple leds for boot/failsafe, etc status (in this case updating
CAP324 to use both colours of the 'power' led, now that such logic in in
ath79 tree).
There
10/11/2018 03:10 AM, Luochongjun:
this patch adds supports for GL-X750.
Specification:
- SOC: QCA9531 (650MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 10/100: 1xLAN + 10/100: 1xWAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
- USB: 1x USB 2.0 port
- Button: 1x reset button
- LED
Hey Russell,
thanks for your patch. Find my remarks inline.
Mathias
26/11/2018 13:54, Russell Senior:
Indoor low-power router with 2.4 GHz radio
CPU:Atheros AR7241 rev 1
RAM:32 MB
Flash: 8 MB NOR SPI
Switch: Atheros AR7240
Ports: 1x WAN, 4x LAN 10/100 Ethernet
WLAN: Atheros AR928
29/11/2018 14:25, Florian Eckert:
Enable mtd led trigger for lantiq devices by default to show MTD
activity
Signed-off-by: Florian Eckert
---
target/linux/lantiq/config-4.14 | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/lantiq/config-4.14 b/target/linux/lantiq/config-4.14
29/11/2018 14:25, Florian Eckert:
Sync target config changes with the following command
make kernel_menuconfig=target
It works slightly different.
The final kernel config is generated by merging
target/linux/generic/config-4.14 + target/linux/lantiq/config-4.14 +
target/linux/lantiq//config-
were most likely added at a time the board had
distinct partitions for kernel and rootfs.
Signed-off-by: Mathias Kresin
---
target/linux/ramips/image/rt305x-legacy.mk | 33 --
target/linux/ramips/image/rt305x.mk| 16 +
tools/firmware-utils/Makefile
Now that we got rid of all legacy images, we can enforce image metadata
verification.
Signed-off-by: Mathias Kresin
---
target/linux/ramips/base-files/lib/upgrade/platform.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh
b/target
Due to the enforced image metadata we ensure that the correct image is
uploaded. Checks based on a magic arn't required any more.
Signed-off-by: Mathias Kresin
---
.../ramips/base-files/lib/upgrade/platform.sh | 330 +-
1 file changed, 1 insertion(+), 329 deletions(-)
image works as all.
Signed-off-by: Mathias Kresin
---
package/boot/uboot-envtools/files/ramips | 1 -
.../ramips/base-files/etc/board.d/02_network | 1 -
target/linux/ramips/base-files/lib/ramips.sh | 6 -
.../ramips/base-files/lib/upgrade/platform.sh | 2 -
target/linux/ramip
29/11/2018 10:36, Petr Štetiar:
Checking metadata in image before flashing is nice for a good user
experience and bricking protection as well, so enable it by default for
all boards but the four legacy ones.
Cc: Mathias Kresin
Signed-off-by: Petr Štetiar
---
target/linux/ramips/base-files
Hey all,
I would like to start to reject patches for adding boards with only 32
MByte of RAM and 4 MByte of flash [0]. These boards barely work with
todays OpenWrt default builds and require quite some modifications to be
useful at all [1].
IMHO it doesn't make much sense to waste resources
05/12/2018 09:56, Mathias Kresin:
Hey all,
I would like to start to reject patches for adding boards with only 32
MByte of RAM and 4 MByte of flash [0]. These boards barely work with
todays OpenWrt default builds and require quite some modifications to be
useful at all [1].
IMHO it doesn&#
herwise there would need to be a vote for other things discussed and
not always that is something ends well. Let's see how this thread goes
before considering it.
Regards
Fernando
On 05/12/2018 06:56, Mathias Kresin wrote:
Hey all,
I would like to start to reject patches for adding boar
28/10/2018 17:39, Christian Lamparter:
Ben Greear reported in his patch:
|Subject: netgear r7800: Fix mac address of radios.
|
|Reloading the driver causes the phyX to change, and that
|caused the MAC address to change.
This is because all ODM/OEMs except QCA bothered to write
the correct MAC ad
ks as
expected.
Register the GPIO chip with the ath9k device as parent only for OF
targets to find a trade-off between the needs of driver developers and
the broken LEDs and buttons seen by users.
Signed-off-by: Mathias Kresin
---
.../ath/548-ath9k_enable_gpio_chip.patch
10/12/2018 02:44, David Bauer:
The initialization for the two ethernet PHYs causes the hardware
wathchdog of devolo WiFi pro boards to trigger reset. Linking the
watchdog drivers before the PHY driver fixes this issue.
Signed-off-by: David Bauer
---
.../431-link-phy-after-watchdog.patch
10/12/2018 23:46, Petr Štetiar:
Currently there is no LED signalization for various system states
implemented in diag.sh, so this patch adds support for it.
Tested-by: Joe Ayers
Signed-off-by: Petr Štetiar
---
target/linux/ath79/dts/ar9342_ubnt_xw.dtsi | 13 ++---
1 file changed, 10
Hey Petr,
find my comments inline.
Mathias
10/12/2018 23:46, Petr Štetiar:
Most of the M/XW platform settings can be shared so move those common
DTS bits into include file.
Tested-by: Joe Ayers
Signed-off-by: Petr Štetiar
---
target/linux/ath79/dts/ar9342_ubnt_bullet-m-xw.dts | 11 +++
10/12/2018 23:46, Petr Štetiar:
In ar71xx/mach-ubnt-xm.c there's following code:
static void __init ubnt_xw_init(void) {
...
ath79_setup_ar934x_eth_cfg(AR934X_ETH_CFG_MII_GMAC0 |
AR934X_ETH_CFG_MII_GMAC0_SLAVE);
...
}
But I couldn't find a way how to set it up via DTS.
Hey Petr,
more comments inline.
Mathias
10/12/2018 23:46, Petr Štetiar:
CPU: AR9342 SoC
RAM: 64 MB DDR2
Flash: 8 MB NOR SPI
Ports: 2x100 MBit (24V PoE in, 24V PoE out), AR8236 switch
WLAN: 2.4/5 GHz
UART: 1 UART
LEDs:Power, 2x Ethernet, 4x RSSI LEDs (orange, red, 2x gre
12/12/2018 13:46, Petr Štetiar:
Mathias Kresin [2018-12-12 13:22:08]:
--- a/target/linux/ath79/dts/ar9342_ubnt_xw.dtsi
+++ b/target/linux/ath79/dts/ar9342_ubnt_xw.dtsi
@@ -9,15 +9,22 @@
compatible = "ubnt,xw", "qca,ar9342";
model = "Ubiquiti Networks X
09/12/2018 21:44, W. Michael Petullo:
Changes in the last year or so have left me a little confused with the
OpenWrt support for the Mikrotik RB493G. I generally compile my kernels
and root disk images myself, namely by running "make menuconfig" and
"make" in an OpenWrt source tree. I then go on
13/12/2018 17:16, Rafał Miłecki:
From: Rafał Miłecki
It results in calling the right MTD parser directly instead of trying
them one by one.
Signed-off-by: Rafał Miłecki
---
I'm not sure about the AR670W.dts. It seems to be using WRG according to
the image generating code:
IMAGE/factory.bin :=
17/12/2018 19:05, Christian Lamparter:
On Saturday, December 15, 2018 9:10:39 PM CET Christian Lamparter wrote:
On Wednesday, November 14, 2018 8:39:22 PM CET Ben Greear wrote:
On 11/01/2018 03:18 AM, Felix Fietkau wrote:
On 2018-10-28 17:39, Christian Lamparter wrote:
Ben Greear reported in
Hey Robinson,
find my comments inline.
Mathias
05/12/2018 06:25, robinson:
This commit adds support for the ZhuoTK JS76x8 development board,
The device has the following specifications:
- SOC:MT7628AN/NN or MT7688AN (580MHz)
- RAM:64/128/256 MB (DDR2)
- FLASH:8/16/32 MB (SPI NOR)
- 3x 10/100
Hey Christoph,
find my comments inline.
Mathias
30/12/2018 10:53, Christoph Krapp:
This patch adds supports for GL-AR750S.
Specification:
- SOC: QCA9563 (775MHz)
- Flash: 16 MiB (W25Q128FVSG)
- RAM: 128 MiB DDR2
- Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN
- Wireless: 2.4GHz (bgn) and 5GHz (ac)
-
30/12/2018 12:35, Tom Psyborg:
On 30/12/2018, Christoph Krapp via openwrt-devel
wrote:
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automati
Hey,
I stumbled of some more stuff. Comments inline.
Am So., 30. Dez. 2018 um 13:27 Uhr schrieb Christoph Krapp via
openwrt-devel :
>
> The sender domain has a DMARC Reject/Quarantine policy which disallows
> sending mailing list messages using the original "From" header.
>
> To mitigate this pro
30/12/2018 14:51, Tom Psyborg:
On 30/12/2018, Mathias Kresin wrote:
30/12/2018 12:35, Tom Psyborg:
On 30/12/2018, Christoph Krapp via openwrt-devel
wrote:
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From&qu
30/12/2018 15:15, Tom Psyborg:
On 30/12/2018, Piotr Dymacz wrote:
Hi Tom,
On 30.12.2018 15:03, Tom Psyborg wrote:
[...]
If it's possible to update from the stock firmware via a webinterface,
it's fine. If not, the way via u-boot works as well.
Mathias
Aren't you embarrassed being such a
01/01/2019 18:23, Christian Lamparter:
The "Device/glinet_ar750s" change to "Device/glinet_gl-ar750s" will likely
break sysupgrade from existing "glinet_ar750s" images. This is because the
now deprecated glinet_ar750s identifier was not added to the
SUPPORTED_DEVICES variable. Other than that, it
17/01/2019 05:38, Rosen Penev:
On Sun, Jan 13, 2019 at 12:28 PM Tomasz Maciej Nowak wrote:
When using Image Builder and building image for Cortex A53 or
A72 subtargets, it'll fail with following message:
Collected errors:
* opkg_install_cmd: Cannot install package mwlwifi-firmware-88w8864.
21/01/2019 00:21, Jeff Klesky:
On 1/16/19 9:03 PM, Petr Štetiar wrote:
Jeff Klesky [2019-01-16 21:48:11]:
Hi,
subject could be just `ath79: Add support for GL.iNet AR-300M-Lite`,
since
you've already added that information about eth0 in the commit
message, and
that's the place where it be
30/01/2019 11:38, Petr Cvek:
Hello,
I discovered the lantiq xrx200 lacks support for interrupts on secondary
VPE, and I've managed to add this functionality to the kernel, the
second icu controller lives on base address 0x1f880300 and works in the
same way as first. Tested with 4.14.93 kernel, u
12/02/2019 20:49, Daniel Golle:
The patch was copied to a bunch of platforms and seems to be a quite
useful feature for various things. Move it to generic to avoid code
duplication.
Follow up to the discussion in
https://github.com/openwrt/openwrt/pull/1814#issuecomment-462942022.
We should
13/02/2019 07:14, Petr Štetiar:
Mathias Kresin [2019-02-12 23:19:24]:
12/02/2019 20:49, Daniel Golle:
The patch was copied to a bunch of platforms and seems to be a quite
useful feature for various things. Move it to generic to avoid code
duplication.
Follow up to the discussion in
https
08/02/2019 09:23, Petr Cvek:
Hello,
There is a wrong code in 0025-NET-MIPS-lantiq-adds-xrx200-net.patch [1], the
original code:
+ link->rx_flow = !!(xrx200sw_read_x(XRX200_MAC_CTRL_0_FCON, port) &&
0x0010);
+ link->tx_flow = !!(xrx200sw_read_x(XRX200_MAC_CTRL_0_FCON, port) &&
0x0
05.10.2016 06:36, Matthew McClintock:
On Sun, Sep 11, 2016 at 1:02 AM, Cezary Jackiewicz
wrote:
Dnia 2016-09-11, o godz. 00:05:18
Matthew McClintock napisał(a):
On Sat, Dec 12, 2015 at 1:53 AM, Cezary Jackiewicz
wrote:
Add support for TRENDnet TEW-823DRU:
- cpu: QCA9558 @720MHz
- flash: 16
2016-11-10 16:41 GMT+01:00 Jo-Philipp Wich :
> Hi Karl,
>
> I think there is not much speaking against making the led init script
> run earlier. I think it would make sense to have it START=11, right
> after /etc/init.d/boot.
I've a TDW-8980 here, where the ath9k driver acts as GPIO controller
for
2016-11-15 18:17 GMT+01:00 alberto fuentes :
> Should i open a bug?
>
> tun0 interface created and ip assigned by openvpn
>
> root@router:~# ifconfig tun0
> tun0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> inet addr:10.19.3.33 P-t-P:10.19.3.1 Mask:
2017-01-13 18:35 GMT+01:00 Martin Blumenstingl
:
> On Fri, Jan 13, 2017 at 6:30 PM, Mauro M. wrote:
>> Hello,
>>
>> Is OpenWRT going to backport support for BtHomeHub5 from LEDE?
>> This router is very well supported in LEDE, whilst support is only basic in
>> OpenWrt,
>> LEDE implemented some bro
10.07.2017 22:07, Damian Kaczkowski:
Hello Sylwester.
On 10 July 2017 at 20:10, Sylwester Petela wrote:
I used the following pictures for visualising and flowing the traces.
The pictures are in the gimp format and have multiple layers:
TD-W8980 - Annex A:
https://www.dropbox.com/s/j6qoeoy1a47
22.10.2017 22:56, Hauke Mehrtens:
On 10/22/2017 10:28 PM, Zoltan HERPAI wrote:
Hi,
Zoltan HERPAI wrote:
Hi Hauke,
On Sun, 22 Oct 2017, Hauke Mehrtens wrote:
I am working on merging the missing commits from the OpenWrt git
repository into the LEDE repository.
Here is a list of all non merge
22.10.2017 22:21, Zoltan HERPAI:
This is pretty much the same as the ALL0256N-8M but with different LED settings.
Based on Matt Jenkins' patch, with additional reworks.
https://github.com/openwrt/openwrt/pull/491
Signed-off-by: Zoltan HERPAI
Hey Zoltan,
I'm not sure how proceed with the pat
2017-10-24 16:59 GMT+02:00 Zoltan HERPAI :
> Hi Jo,
>
> On Tue, 24 Oct 2017, Jo-Philipp Wich wrote:
>
>> Hi,
>>
>> comments inline.
>>
>>> Signed-off-by: Imre Kaloz
>>
>>
>> Given the fact that we explicitely wanted to avoid @openwrt.org mails
>> and that this was one of the discussion points lead
11.11.2017 11:53, Anton Ivanov:
Resend (apologies, tried to send it to -users by mistake initially).
Hi all,
I am observing an interesting issue with the OpenWRT build process when
building on an up-to-date stretch host. It no longer works on NFS on
debian (it used to work).
If I run make with
10.01.2018 11:15, Thomas Hebb:
Currently, we solve the problem of different IPQ4019 boards needing
different sets of Wi-Fi calibration data (board-2.bin) by using an
ipq-wifi-* package to overwrite board-2.bin in the filesystem. This
presents a problem when we need the same image to support multi
Hey Thomas,
I only had a brief look at the patch. Might be there is more stuff to
change. Find my comments inline.
10.01.2018 11:15, Thomas Hebb:
This patch adds support for the Netgear EX6100v2 and EX6150v2 Wi-Fi
range extenders.
Hardware:
SoC:Qualcomm IPQ4018
RAM:256 MiB
FLASH: 1
11.01.2018 07:23, Mathias Kresin:
10.01.2018 11:15, Thomas Hebb:
Currently, we solve the problem of different IPQ4019 boards needing
different sets of Wi-Fi calibration data (board-2.bin) by using an
ipq-wifi-* package to overwrite board-2.bin in the filesystem. This
presents a problem when we
2018-05-25 6:43 GMT+03:00 Rosen Penev :
> This is a port of an old commit from mkresin's tree:
>
> 09260cdf3e9332978c2a474a58e93a6f2b55f4a8
>
> This has the potential to break sysupgrade but it should be fine as
> there is no stable release of LEDE or OpenWrt that support these devices.
>
> Signed-
2018-05-25 12:48 GMT+03:00 Jaap Buurman :
> Dear Martin, Mathias and the rest,
>
> Please scratch my previous message. It seems like the flash was not
> successful, and hence I was still running the old firmware. However, I
> have tried flashing 3 different times now, without any luck. The
> router
2018-05-27 19:21 GMT+03:00 Rosen Penev :
> Signed-off-by: Rosen Penev
> ---
> package/firmware/ath10k-firmware/Makefile | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/package/firmware/ath10k-firmware/Makefile
> b/package/firmware/ath10k-firmware/Makefile
> index 2c024905bb..35f6013947
2018-05-28 15:49 GMT+03:00 Mauro Mozzarelli :
> Hello,
>
>
> I reported https://bugs.openwrt.org/index.php?do=details&task_id=1567
Another user reported on IRC it is related to the kernel bump to 4.14.
He is aware of the issue since a few weeks (at the time k4.14 was
optional), but didn't created
08.06.2018 20:45, Kevin Darbyshire-Bryant:
Define USB port power as set on by bootloader (which it is) The power
gets cycled at kernel boot, but by defining as 'regulator-boot-on'
reduces the power off to power on at driver initial load & setup from
around 5 seconds to around 2 seconds.
Signed-
13.06.2018 10:51, Zoltan HERPAI:
Certain Netgear devices use BE squashfs for the kernel image. As
squashfs4 only supports creating LE images, add squashfs (v3) into
the tools to be built for ath79.
Trying to use an LE squashfs (thus trying to use squashfs4 only for
building the image) for the ke
12.06.2018 22:54, Alex Maclean:
Readd SoC compatible strings and correct model names mangled in
a51078f7354fac9e31f6956cbddc77aaef02c67b, cleanup dts to remove
duplication, rename dtsi for clarity, use correct GPIO for TL-MR10U
USB power.
Tested only on TL-WR703N due to lack of a TL-MR10U.
Sign
14.06.2018 22:38, Zoltan HERPAI:
Felix Fietkau wrote:
How about this instead:
tools-$(CONFIG_TARGET_ar71xx)$(CONFIG_TARGET_ath79) += squashfs
- Felix
I'm happy with either, whichever you guys fancy.
Thanks,
-w-
I like felix proposed solution more than what I had and committed it
instead.
21.06.2018 17:08, wong.syr...@gmail.com:
From: Syrone Wong
Signed-off-by: Syrone Wong
---
package/network/config/firewall/Makefile | 2 +-
package/system/procd/Makefile| 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/network/config/firewall/Makefile
21.06.2018 21:18, Jaap Buurman:
Dear Kevin,
Some very good points you are giving. Is there anyone able and willing
to cherry-pick these 3 commits to the 18.06 branch before the RC1
release is tagged tomorrow?
At least I'll not do so.
I would like to see this change a bit more tested in maste
2018-06-25 15:56 GMT+02:00 Mikael Bak :
>
> Build dependency: Please install GNU 'time' or BusyBox 'time'
>
> Prerequisite check failed. Use FORCE=1 to override.
> make[1]: *** [Makefile:76: staging_dir/host/.prereq-build] Error 1
> make: *** [Makefile:175: image] Error 2
> [mikael@mikael-pc
> open
101 - 200 of 266 matches
Mail list logo
