On 25.09.2019 16:51, Rafał Miłecki wrote:
From: Rafał Miłecki
This new ubus method provides more properly-formatted details about
firmware file. Use it to check if uploaded image is valid.
The old "sysupgrade --test" method is left for now to provide stderr
output.
Signed-off-by: Rafał
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 ---
‐‐‐ Original Message ‐‐‐
On 25/09/2019, Maxnet Support wrote:
> I have attached iw phy phy0 info output. It shows only 2 antennas. Is this
> wrong? Qca9994 has 4 chains.
>
> On 25 Sep 2019, 22:51, at 22:51, supp...@maxnet.al wrote:
>>Hi,
>>
>>
>>
>>
>>
>>
>>In the beginning i was using 2 dishes on each side. They are
Hi,
In the beginning i was using 2 dishes on each side. They are ubiquiti 2x2 dual
polarized dishes and i connected the chains of station in the same way as AP
and i still had issues. After that i thought the problem might be because this
card uses mimo multipath and AP ch0 should talk
This is meant for 19.07, as it's already in master. I just now
realized it was missing from the subject line. Sorry about that.
Eneas
On Wed, Sep 25, 2019 at 2:03 PM Eneas U de Queiroz
wrote:
>
> This adds the CRYPTO_ALG_KERN_DRIVER_ONLY flag to Qualcomm crypto engine
> driver algorithms, so
This adds the CRYPTO_ALG_KERN_DRIVER_ONLY flag to Qualcomm crypto engine
driver algorithms, so that openssl devcrypto can recognize them as
hardware-accelerated.
Signed-off-by: Eneas U de Queiroz
diff --git
On 25.09.19 17:14, supp...@maxnet.al wrote:
This is long distance, 5km with 4 dishes on each side. They are all
vertical and all chains have signal range -60 to -65.
I don't have omni antennas. Is there a problem that i am using dishes?
I run dozens of long-range devices, and I'm seeing 2
From: Rafał Miłecki
Some firmware images may not support preserving backup. In such cases
display a warning and disable relevant checkbox.
---
.../resources/view/system/flash.js| 23 +--
1 file changed, 16 insertions(+), 7 deletions(-)
diff --git
On 9/25/19 8:14 AM, supp...@maxnet.al wrote:
This is long distance, 5km with 4 dishes on each side. They are all vertical
and all chains have signal range -60 to -65.
I don't have omni antennas. Is there a problem that i am using dishes?
I have no idea, but at the very least, you should
The following symbols, selected by the qce driver were removed:
CONFIG_CRYPTO_CBC
CONFIG_CRYPTO_CTR
CONFIG_CRYPTO_DES
CONFIG_CRYPTO_DEV_QCE
CONFIG_CRYPTO_ECB
CONFIG_CRYPTO_NULL
CONFIG_CRYPTO_SEQIV
CONFIG_CRYPTO_XTS
This is long distance, 5km with 4 dishes on each side. They are all vertical
and all chains have signal range -60 to -65.
I don't have omni antennas. Is there a problem that i am using dishes?
On Wed, Sep 25, 2019 at 5:11 PM +0200, "Ben Greear"
wrote:
Is this short distance
Is this short distance or long?
Please try short distance with omni antenna first to make sure you are not
hitting the delayed-ack issue
or problems with your antenna.
Change your antenna orientation so that they point in different directions.
Thanks,
Ben
On 9/25/19 6:49 AM,
From: Rafał Miłecki
Some validation errors may be critical enough to prevent sysupgrade.
Check the "forceable" property and disallow forcing sysupgrade if
applicable. It would fail anyway at the "sysupgrade" call.
Signed-off-by: Rafał Miłecki
---
From: Rafał Miłecki
This new ubus method provides more properly-formatted details about
firmware file. Use it to check if uploaded image is valid.
The old "sysupgrade --test" method is left for now to provide stderr
output.
Signed-off-by: Rafał Miłecki
---
.../resources/view/system/flash.js
It is informative especially when using multiple device pairs.
Signed-off-by: Ali MJ Al-Nasrawy
---
package/kernel/trelay/src/trelay.c | 8
1 file changed, 8 insertions(+)
diff --git a/package/kernel/trelay/src/trelay.c
b/package/kernel/trelay/src/trelay.c
index
Upon writing to "remove" file, debugfs_remove_recursive() blocks while
holding rtnl_lock. This is because debugfs' file_ops callbacks are
executed in debugfs_use_file_*() context which prevents file removal.
Fix this by only flagging the device for removal and then do the cleanup
in
Since v3.11, netdevice notification data are of type
"struct netdev_notifier_info". Handle it as such!
This should fix a critical bug in which devices are unable get released
because trelay does not release resources in response to UNREGISTER
event spamming the log with something like:
Hello,
Today i managed to connect the station wds at 80MHz channel. Signal is -56 and
i have very low datarates. I have attached a photo.
When station was ddwrt and AP openwrt the datarates were 866/433. TX won't do
more than VHT-NSS 1 although RX it's not good either because it's a 4 chain
It would be nice to have watch file for mariadb and domoticz ?
Little off-topic question, is there any plan to create uscan page for
19.07 ?
J.P.
Dne 19. 09. 19 v 2:32 Stephen Walker napsal(a):
> No, they've always just been sitting in a local source tree. Do you
> have any specific packages in
Spelling of Zbtlink varies across image definitions and DTS files.
This patch uses Zbtlink consistently and also updates the model
in DTS files to contain the vendor in all cases.
This patch is cosmetical, as there should be no dependencies on
device model name in ramips anymore.
Signed-off-by:
20 matches
Mail list logo
