Hi,
> It seems to be like that script does things even if the tarballs are
> already existing locally.
the main problem I see is that you moved the download method detection
from inline make code into the external Python script ... this will
cause a lot of overhead as during the metadata
Hi Yousong,
this change seems to introduce serious runtime regressions, see
https://bugs.openwrt.org/index.php?do=details_id=1621
It seems to be like that script does things even if the tarballs are
already existing locally.
On a slightly related note, I find the name to be too generic. It
TP-Link RE450 v2 is a dual band router/range-extender
based on Qualcomm/Atheros QCA9563 + QCA9880.
Specification:
- 775 MHz CPU
- 64 MB of RAM (DDR2)
- 8 MB of FLASH (SPI NOR)
- 3T3R 2.4 GHz
- 3T3R 5 GHz
- 1x 10/100/1000 Mbps Ethernet (AR8033 PHY)
- 7x LED, 4x button
- UART header on PCB (needs
Hi Hans,
pls don't commit them.
I've forgot the SOB line, but also would like to add a GPG signature to
it, after you've reviewed them.
Best,
lynxis
pgpjV8BknClhD.pgp
Description: OpenPGP digital signature
___
openwrt-devel mailing list
Previous netifd would only apply `ip rule`s while config phase.
If the iprule is depending on an interface (iif or oif), the rule
will fail if the interface is not up.
Allow iprules to track interfaces and their devices by using
the interface events.
Fixes: FS#1571
---
iprule.c | 179
"create" will be called before the proto handlers initialised.
---
interface-event.c | 1 +
interface.c | 1 +
interface.h | 2 ++
3 files changed, 4 insertions(+)
diff --git a/interface-event.c b/interface-event.c
index 86e8f5488da8..a40f6dc883d3 100644
--- a/interface-event.c
+++
The SSID will be UTF-8 encoded when set through LuCI. If otherwise set to a
non UTF-8 encoded value, use utf8_ssid=0 to tell hostapd so.
Signed-off-by: Jouke Witteveen
---
package/network/services/hostapd/files/hostapd.sh | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Thanks a lot for the patch.
Due to today's changes you most likely need to rebase your patch. Find
more comments inline.
Mathias
2018-06-28 19:30 GMT+02:00 Peter Lundkvist :
TP-Link RE450 v2 is a dual band router/range-extender
based on Qualcomm/Atheros QCA9563 + QCA9880.
Specification:
-
On Fri, Jun 15, 2018 at 9:25 PM wrote:
> > On 06/14/2018 05:35 AM, Linus Walleij wrote:
> > Probably as good as it can get given the information you have access to.
> > Maybe the guys at Mircochip could help, adding them.
>
> Microchip have completed the acquisition of Microsemi last months. It
A company recently sponsored the work to rebase my 1000 or so ath10k-ct wave-2 firmware on a more recent upstream QCA firmware release. I now believe it is
stable enough for wider testing, so I invite any of you using ath10k-ct wave-2 firmware on the 9984 chipset to grab the latest beta from our
TP-Link RE450 v2 is a dual band router/range-extender
based on Qualcomm/Atheros QCA9563 + QCA9880.
Specification:
- 775 MHz CPU
- 64 MB of RAM (DDR2)
- 8 MB of FLASH (SPI NOR)
- 3T3R 2.4 GHz
- 3T3R 5 GHz
- 1x 10/100/1000 Mbps Ethernet (AR8033 PHY)
- 7x LED, 4x button
- UART header on PCB (needs
Hi John & all,
after increasing the rootfs_data size from 2 to 16MB in our device, I realized
the
'delayed jffs2 overlay mount' feature which I was not aware before and which in
our setup is causing trouble.
Before, jffs2 was always ready after the wait for failsafe key-press and the
mount_root
On Wed, Jun 27, 2018 at 11:15 PM wrote:
>
> From: Joe Holden
>
> This adds an array that contains the link modes advertised by the other
> device and also
> indicates whether auto negotiation is true or false.
>
> link-partner may or may not be populated depending on hardware, driver and/or
>
> -Original Message-
> From: Kevin Darbyshire-Bryant [mailto:ke...@darbyshire-bryant.me.uk]
> Sent: Donnerstag, 28. Juni 2018 10:07
> To: m...@adrianschmutzler.de
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] Archer C7 v2 with Target System "Atheros
> ATH79 (DTS)" or
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
automatically by the mailing list software.--- Begin Message ---
> On 28 Jun 2018, at 08:26,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Lucian Cristian
> Sent: Donnerstag, 28. Juni 2018 00:03
> To: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] Archer C7 v2 with Target System "Atheros
> ATH79 (DTS)" or
16 matches
Mail list logo
