I just realized now that my reply went to Hauke only, so I'm sending
it again to the mailing list, as it may be useful for more people.
On Fri, Sep 20, 2019 at 5:43 PM Hauke Mehrtens wrote:
>
> On 9/19/19 4:18 AM, Eneas U de Queiroz wrote:
> > WolfSSL added a wolfSSL_X509_check_host function to
On Fri, Sep 20, 2019 at 1:35 PM Christian Lamparter
wrote:
> Hello,
>
> On Tuesday, September 17, 2019 6:59:28 AM CEST Russell Senior wrote:
> > On Meraki MR24, the BLOCKSIZE variable is used to allocate space for the
> > kernel blob. The LEB size on MR24 is 15.5k (15872 bytes). In the
> >
The switch port naming in LuCI does not fit the physical numbers
on the front of this device. Since this is confusing, fix it.
Signed-off-by: Michael Heimpold
---
target/linux/brcm47xx/base-files/etc/board.d/01_network | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Hi Ben,
When do you think you can port those changes to your firmware?
Thank you for your support.
Klevis.
On Fri, Sep 20, 2019 at 10:01 PM +0200, "Ben Greear"
wrote:
On 9/20/19 12:55 PM, Vincent Wiemann wrote:
> Hi Klevis,
>
> have you tried it with a short distance?
>
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
--
It was reported to me at the forum:
On 9/19/19 4:18 AM, Eneas U de Queiroz wrote:
> WolfSSL added a wolfSSL_X509_check_host function to perform CN
> validation in v3.10.4, depending on the build-time configure options:
> --enable-nginx enables it for all supported versions;
> --enable-opensslextra, since v3.14.2.
>
> If the
Hello,
On Tuesday, September 17, 2019 6:59:28 AM CEST Russell Senior wrote:
> On Meraki MR24, the BLOCKSIZE variable is used to allocate space for the
> kernel blob. The LEB size on MR24 is 15.5k (15872 bytes). In the
> particular instance observed, it was found that reducing blocksize to
> 512
Hi Vincent,
I have tried short distance with ddwrt and i get 1733/1733 datarates and about
1Gbps real traffic using iperf. Ubiquiti and MikroTik have 80MHz outdoor radios
and they work good. I don't want to use 160MHz which is very wide and there are
lot of 20MHz channels within that will
On 9/20/19 12:55 PM, Vincent Wiemann wrote:
Hi Klevis,
have you tried it with a short distance?
If you did you should better ask Ben Greear directly.
I asked him to post publicly so that others can help answer and that my own
answers might
help someone else.
I have some patches that should
Hi Klevis,
have you tried it with a short distance?
If you did you should better ask Ben Greear directly.
By the way ath10k gen 2 chipsets don't work very well with long distance links
without a
special feature which implementation is only available to companies like
Ubiquiti and very few
On 9/2/19 11:27 PM, Rosen Penev wrote:
> On Mon, Sep 2, 2019 at 1:29 PM Hauke Mehrtens wrote:
>>
>> This fixes some resources leaks mostly in error patches.
>>
>> Coverity: #1330236, #1330237, #1330238
>> Signed-off-by: Hauke Mehrtens
>> ---
>> main.c | 12 ++--
>> 1 file changed, 10
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: [OpenWrt-Devel] build: fix make kernel_menuconfig
- http://patchwork.ozlabs.org/patch/1163120/
- for: OpenWrt development
was: Under Review
now: Rejected
This email is a notification only
Thomas Albers via openwrt-devel [2019-09-16
17:55:42]:
Hi,
[...]
> Use system pkg-config instead of toolchain pkg-config when the kernel
> config scripts are compiled (see FS#2423)
[...]
> diff --git a/tools/pkg-config/files/pkg-config
> b/tools/pkg-config/files/pkg-config
> index
On Fri, 20 Sep 2019 15:37:08 +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> Hardware or firmware instability may result in unusable wiphy. In such
> cases usually a hardware reset is needed. To allow a full recovery
> kernel has to indicate problem to the user space.
>
> This new nl80211
Hello everyone,
I am trying to setup a custom made outdoor link with Apu2d2 board devices and
QCA9994 cards from compex. After i installed openwrt and ath10k ct driver, kmod
ath10k and board-2.bin the device can run a 80MHz channel in WDS AP. The
problem is that it won't run as station or
On Fri, Sep 20, 2019 at 03:37:08PM +0200, Rafał Miłecki wrote:
> Hardware or firmware instability may result in unusable wiphy. In such
> cases usually a hardware reset is needed. To allow a full recovery
> kernel has to indicate problem to the user space.
Why? Shouldn't the driver be able to
From: Rafał Miłecki
Hardware or firmware instability may result in unusable wiphy. In such
cases usually a hardware reset is needed. To allow a full recovery
kernel has to indicate problem to the user space.
This new nl80211 command lets user space known wiphy has crashed and has
been just
I tried to compile the package libmraa as single and have some problems with
the dependencies:
Followed this: https://openwrt.org/docs/guide-developer/single.package
First i searched for all dependencies:
root@OpenWrt:/# opkg info libmraa
Package: libmraa
Version: 2.0.0-2
Depends: libc,
This replaces deprecated backticks by more versatile $(...) syntax.
While at it, remove some useless cat commands and deprecated
egrep commands.
Signed-off-by: Adrian Schmutzler
---
v3: rebase
---
target/linux/ramips/base-files/etc/board.d/02_network | 6 +++---
This is the result of grepping/searching for several common
whitespace issues like double empty lines, leading spaces, etc.
This patch fixes them for the ramips target.
Signed-off-by: Adrian Schmutzler
---
v2: rebase, added fixes for EnGenius ESR600, AsiaRF AP7621 DTSI
---
This converts all remaining devices to use interrupt-driven
gpio-keys compatible instead of gpio-keys-polled.
The poll-interval is removed.
While at it, add/remove newlines in keys and leds node where
necessary.
Signed-off-by: Adrian Schmutzler
---
v2: rebase
---
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: [OpenWrt-Devel] build: fix make kernel_menuconfig
- http://patchwork.ozlabs.org/patch/1163120/
- for: OpenWrt development
was: New
now: Under Review
This email is a notification only - you
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Petr Štetiar
> Sent: Freitag, 20. September 2019 09:56
> To: Kristian Evensen
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 1/2] ramips: Update ZBT
Hi,
> -Original Message-
> From: Petr Štetiar [mailto:yn...@true.cz]
> Sent: Freitag, 20. September 2019 08:45
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 1/3] ramips/mt762x: convert devices to
> interrupt-driven gpio-keys
>
>
On 17.09.19 00:25, Jonas Gorski wrote:
On Sun, 15 Sep 2019 at 12:49, Paul Spooren wrote:
What you suggest is about what we have right now. This kind of creates a misleading situation where
for some targets subtargets are present, while for others paths and image names are
"fixed" in several
Kristian Evensen [2019-09-20 10:13:31]:
> I will do it during or right over the weekend. Btw, can I consider
> this your ACK of the licensing change as well?
Acked-by: Petr Štetiar
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi Petr,
On Fri, Sep 20, 2019 at 9:56 AM Petr Štetiar wrote:
> could you please rebase to series to the current state of the tree? I would
> like to apply it, thanks!
>
> BTW don't forget to include the license change ACKs.
I will do it during or right over the weekend. Btw, can I consider
this
Kristian Evensen [2019-06-23 11:24:47]:
Hi,
> This commit makes the following changes to the WE1026 DTS-files:
could you please rebase to series to the current state of the tree? I would
like to apply it, thanks!
BTW don't forget to include the license change ACKs.
> Signed-off-by: Kristian
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: [OpenWrt-Devel] ramips: add support to JS7628 development board
- http://patchwork.ozlabs.org/patch/1134527/
- for: OpenWrt development
was: New
now: Superseded
This email is a
Adrian Schmutzler [2019-09-17 14:22:23]:
Hi,
> So far, for the ZBT-WE826-E the leds pulled from the DTSI are deleted and
> then redefined. The config in the DTSI is then used in two other DTSes for
> the ZBT-WE826 flash variants.
>
> Since the block is effectively only used for two devices,
Adrian Schmutzler [2019-09-17 14:22:21]:
Hi,
> This converts all remaining devices to use interrupt-driven
> gpio-keys compatible instead of gpio-keys-polled.
> The poll-interval is removed.
[...]
> 161 files changed, 197 insertions(+), 314 deletions(-)
I'm just wondering what makes you so
31 matches
Mail list logo
