Hi!
Sorry for the late reply.
On Wed, Jan 29, 2020 at 11:18 PM Piotr Dymacz wrote:
> AFAIK, there wasn't any official or general rule about what should be
> LAN and WAN (in terms of mapping ethX to 'our' LAN/WAN), so it was
> always up to the device support author (personally I preferred to have
On Wed, Jan 29, 2020 at 3:14 PM Rosen Penev wrote:
>
>
>
> Sent from my iPhone
>
> > On Jan 29, 2020, at 8:22 AM, Petr Štetiar wrote:
> >
> > Rosen Penev [2020-01-25 15:04:03]:
> >
> > Hi Bjørn and Rosen,
> >
> >>> On Thu, Jan 23, 2020 at 12:25 AM Bjørn Mork wrote:
> >
> > - if ((r
Hello Adrian,
On 1/29/20 2:57 PM, Adrian Schmutzler wrote:
> Hi,
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
>> Behalf Of David Bauer
>> Sent: Dienstag, 28. Januar 2020 21:05
>> To: drvl...@gmail.com; achte...@googlemail.com; openwrt-
Sent from my iPhone
> On Jan 29, 2020, at 8:22 AM, Petr Štetiar wrote:
>
> Rosen Penev [2020-01-25 15:04:03]:
>
> Hi Bjørn and Rosen,
>
>>> On Thu, Jan 23, 2020 at 12:25 AM Bjørn Mork wrote:
>
> - if ((rt_sysc_r32(SYSC_REG_CHIP_REV_ID) & 0x) == 0x0101) {
> -
From: Michael Yartys
This supports better per-chain noise floor reporting, which in turn allows for
better RSSI reporting in the driver.
Wave-2 fixes a long-standing rate-ctrl problem when connected to xbox (and
probably other devices).
Wave-2 has fix for crash likely related to rekeying.
Wav
From: Michael Yartys
Changes:
ath10k-ct: Support better RSSI measurements.
When used with recent firmware, these changes allow the driver to
query per-chain noise-floor from the radio to better calculate the
per-chain RSSI. The per-chain RSSI is then summed to provide the
'combined RSSI'. This
This moves the various variants of common device definitions for
TP-Link devices to a common Makefile common-tp-link.mk. This
provides the opportunity to reorganize and move parameters between
individual device definitions and the common ones.
While at it, also use the common definitions for previ
Please ignore this one for the moment, it seems to be bugged. Sorry for the
noise.
A quarta, 29/01/2020, 11:50, Rui Salvaterra
escreveu:
> Both fw3_has_table and fw3_has_target do the same thing. Factor out the
> common code into a separate function.
>
> Signed-off-by: Rui Salvaterra
> ---
> u
This moves the various variants of common device definitions for
TP-Link devices to a common Makefile common-tp-link.mk. This
provides the opportunity to reorganize and move parameters between
individual device definitions and the common ones.
While at it, also use the common definitions for previ
On Wed, 29 Jan 2020 17:40:43 +0100
"Roger Pueyo Centelles | Guifi.net via openwrt-devel"
wrote:
> Hi all,
>
> It seems like the NAND flash is read with different endiannesses:
>
> [...]
>
> I wonder, though, which is the "correct" one --or how to change
> ath79's, so that it is coherent with the
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 ---
Hi all,
It seems like the NAND fl
This supports better per-chain noise floor reporting, which in turn allows for
better RSSI reporting in the driver.
Wave-2 fixes a long-standing rate-ctrl problem when connected to xbox (and
probably other devices).
Wave-2 has fix for crash likely related to rekeying.
Wave-1 has some debugging
Rosen Penev [2020-01-25 15:04:03]:
Hi Bjørn and Rosen,
> On Thu, Jan 23, 2020 at 12:25 AM Bjørn Mork wrote:
> > >
> > > - if ((rt_sysc_r32(SYSC_REG_CHIP_REV_ID) & 0x) == 0x0101) {
> > > - /* (GE1, Force 1000M/FD, FC ON, MAX_RX_LENGTH 1536) */
> > > + if ((rt_sysc_r32(SYS
Please see below for commit. New firmware message will follow shortly.
If someone can test and push to openwrt I'd appreciate it.
commit 3e3d0adb3cc6c6cf56a05ff661796948f09c5aa8 (HEAD -> master, origin/master)
Author: Ben Greear
Date: Wed Jan 29 08:14:56 2020 -0800
ath10k-ct: Support b
Hi Adrian,
On 28.01.2020 16:59, Adrian Schmutzler wrote:
Hi,
There is easy way to check GMACx <> ethX assignment order in mach-*.c
files. Just check order of ath79_register_eth() calls:
ath79_register_eth(0);
ath79_register_eth(1);
Will register GMAC0 as eth0, GMAC1 as eth1
ath79_register_e
Hi Adrian,
On 28.01.2020 16:48, Adrian Schmutzler wrote:
Hi Piotr,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
Behalf Of Piotr Dymacz
Sent: Montag, 27. Januar 2020 21:45
To: Adrian Schmutzler
Cc: openwrt-devel@lists.openwrt.org; gch981...
Hi Peter,
On 27.01.2020 22:05, Peter Geis wrote:
On Mon, Jan 27, 2020 at 4:00 PM Piotr Dymacz wrote:
[...]
But it's not a general rule and, at least in case of generic/basic
settings, user shouldn't be worried about upgrading between major
versions with preserving settings. Otherwise, the w
Hi,
> (I should first say that I don't know enough about the ar71xx-ath79 migration
> to know if this idea will work, but I don't recall seeing it mentioned
> before.)
>
> What if we add a migration package for 18.06 that ar71xx users can opt-in and
> install, which (when the user initiates the
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of David Bauer
> Sent: Dienstag, 28. Januar 2020 21:05
> To: drvl...@gmail.com; achte...@googlemail.com; openwrt-devel de...@lists.openwrt.org>
> Subject: [OpenWrt-Devel] Netgear R6
Hi David,
On 1/28/20 5:34 PM, Adrian Schmutzler wrote:
>> The GL.iNet microuter-N300 (internally referred as MT300N-v4) is a
>> pocket-size travel router. It is essentially identical to the VIXMINI
>> (internally referred as MT300N-v3) but with double the RAM and
>> SPI-flash.
thanks for the resp
Both fw3_has_table and fw3_has_target do the same thing. Factor out the
common code into a separate function.
Signed-off-by: Rui Salvaterra
---
utils.c | 42 ++
1 file changed, 14 insertions(+), 28 deletions(-)
diff --git a/utils.c b/utils.c
index da65632
Hi,
thank you for your fast reply.
It is not faster/smaller as the getters are indirections to blobmsg_data
(optimized they should have the same performance).
The problem arises, when you have a `const struct blob_attr *` and want
to get the values: In C++ you cannot pass them to the get-f
Peter Stadler [2020-01-29 09:29:50]:
Hi,
> This allows to get the values instead of calling blobmsg_data.
ok, as you didn't provided this information in the commit message and I'm
wondering, does this changes make libubox faster (by how much?), smaller (by
how much?) or was there perhaps someth
Change the signature of the following get-functions to accept
the `struct blob_attr *attr` as `const`:
- blobmsg_get_u8
- blobmsg_get_bool
- blobmsg_get_u16
- blobmsg_get_u32
- blobmsg_get_u64
- blobmsg_get_double
- blobmsg_get_string
This allows to get the values instead of calling b
24 matches
Mail list logo
