Attempting to use the hAP ac lite model RB952Ui-5ac2nD with the 5GHz
radio0 802.11ac seems to be unstable and consume available memory.
This is only enabling radio0 with no other changes and bringing wifi
up/down to reproduce. Am I doing something silly, or should I submit
a bug?
root@OpenWrt:/t
Hi Thomas,
On Fri, Nov 22, 2019 at 10:55:38AM +0100, Thomas Petazzoni wrote:
> Signed-off-by: Thomas Petazzoni
> ---
> include/image.mk | 15 ++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/include/image.mk b/include/image.mk
> index 8592c19b99..86b3edeb87 100
The wrapper calls pkgconf with multiple arguments. meson wants to call
it with a single --version argument. To keep compatibility with
pkg-config, revert the upstream version change.
This fixes projects that use meson and pkg-config to find packages.
Signed-off-by: Rosen Penev
---
...me-modvers
pkgconf is a newer, actively maintained implementation of pkg-config that
supports more aspects of the pkg-config file specification and provides a
library interface that applications can use to incorporate intelligent
handling of pkg-config files into themselves (such as build file
generators, IDE
Mainly quoting fixes.
Separated parameters by \ for easier readability.
Signed-off-by: Rosen Penev
---
v2: Removed calling by dirname.
tools/pkgconf/files/pkg-config | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/pkgconf/files/pkg-config b/tools/pkgconf/files/pkg
Fixes warnings:
warning: passing argument 2 of 'execv' from incompatible pointer type
[-Wincompatible-pointer-types]
254 | execv(usign_argv[0], usign_argv)
Signed-off-by: Rosen Penev
---
usign-exec.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/usign-
On 28/11/19 22:02, Paul Spooren wrote:
I know nothing about sunix, but the other three targets appear mostly
space "indipendent".
Sunxi target is basically a bunch of Raspberry Pi clones using different
SoC.
You usually have a SDcard to store the OS image.
-Alberto
_
> From: Hauke Mehrtens [mailto:ha...@hauke-m.de]
> Sent: Donnerstag, 28. November 2019 19:42
> To: Adrian Schmutzler ; 'OpenWrt Development List'
>
> Cc: 'Koen Vandeputte'
> Subject: Re: [OpenWrt-Devel] Kernel version for OpenWrt 20.X
>
> On 11/28/19 7:11 PM, Adrian Schmutzler wrote:
>> Hi Hau
Hi Hauke,
On 28.11.2019 19:41, Hauke Mehrtens wrote:
On 11/28/19 7:11 PM, Adrian Schmutzler wrote:
Hi Hauke,
The following are still on kernel 4.9:
* ar7
* ixp4xx
* orion
There are patches (actually from you, May 2019) on the list which claim to bump
ar7 and orion to 4.14:
https://patc
On 11/28/19 7:11 PM, Adrian Schmutzler wrote:
> Hi Hauke,
>
>> The following are still on kernel 4.9:
>> * ar7
>> * ixp4xx
>> * orion
>
> There are patches (actually from you, May 2019) on the list which claim to
> bump ar7 and orion to 4.14:
>
> https://patchwork.ozlabs.org/project/openwrt/
Hi Hauke,
> The following are still on kernel 4.9:
> * ar7
> * ixp4xx
> * orion
There are patches (actually from you, May 2019) on the list which claim to bump
ar7 and orion to 4.14:
https://patchwork.ozlabs.org/project/openwrt/list/?series=107337
https://patchwork.ozlabs.org/project/openwrt
Hi,
[...]
> -*wandboard)
> +*wandboard |\
> +*tx6u-8033)
> ucidef_set_interface_wan 'eth0'
> ;;
Please do not use wildcard characters for the board name. This makes it really
ugly to change anything later, as you cannot grep for a particular device.
Despite, I do not see any reason
On Fri, 29 Nov 2019 at 00:32, Paul Spooren wrote:
>
> Hi Yousong,
>
> > A few months ago, I started working on bringing up k3s on OpenWrt. I
> > managed to have a small k8s cluster with nodes running centos and
> > openwrt. Likely other linux distros will also do, but I didn't test
> > combinati
From: Linus Lüssing
This adds support for the Ka-Ro MB7 board with a TX6U-8033 module.
Specification, according to Linux DTS commit:
TX6U-8033:
ProcessorFreescale i.MX 6 Dual Lite, 800MHz
RAM 1GiB DDR3 SDRAM
ROM 4GiB eMMC
Power supply Single 3.1V to 5.5
Hi Yousong,
A few months ago, I started working on bringing up k3s on OpenWrt. I
managed to have a small k8s cluster with nodes running centos and
openwrt. Likely other linux distros will also do, but I didn't test
combination of different architectures yet.
Cool! That looks like an interestin
Adrian Schmutzler [2019-11-28 15:40:32]:
> have mixed kernel releases again
This is not an option, is it?
> or would have to throw out a lot of targets for each of the stable branches
> (which might be always the same set of less-cared targets)?
If the target is obsolete and/or orphaned, what
Hi,
> I think, that it would make more sense to make a releasing process clear, make
> it predictable. So perhaps rather start voting about that? So we could came to
> some conclusion, release rules? That way we don't need to argue about this
> anymore, it would be set in the stone, unless changed
Rosen Penev [2019-11-27 16:18:10]:
> > Switched to calling by dirname so that it can be called from any
> > directory.
I can see that already from the source code, but I would rather see a answer
to "Why?" In other words, whats the problem with current state, why is this
change needed?
> AGH. T
Hello Jan,
On Thu, 28 Nov 2019 13:25:24 +0100
Jan Pavlinec wrote:
> I think that maintainers of openwrt/openwrt repo are more active on the
> mailing list but openwrt/packages maintainers prefer GitHub. But that is
> just my personal feeling.
Thanks for the suggestion. I just opened a Github pu
I think that maintainers of openwrt/openwrt repo are more active on the
mailing list but openwrt/packages maintainers prefer GitHub. But that is
just my personal feeling.
J.P.
Dne 28. 11. 19 v 13:01 Thomas Petazzoni napsal(a):
> Hello Jan,
>
> On Thu, 28 Nov 2019 12:35:36 +0100
> Jan Pavlinec wr
Hauke Mehrtens [2019-11-28 00:42:53]:
Hi,
> planned to do the next release in January 2020 which is soon. This 20.x
> release is planned to use kernel 4.19 only.
that's my understanding as well.
> Based on these numbers it could be already hard to get everything to
> 4.19 till beginning of Jan
Hello Jan,
On Thu, 28 Nov 2019 12:35:36 +0100
Jan Pavlinec wrote:
> I really like the idea of SELinux support in OpenWrt, but I think that
> if you send these patches directly to
> https://github.com/openwrt/packages/ they will receive more attention
> than here in mailing list.
Thanks a lot fo
Hi,
I really like the idea of SELinux support in OpenWrt, but I think that
if you send these patches directly to
https://github.com/openwrt/packages/ they will receive more attention
than here in mailing list.
J.P.
Dne 22. 11. 19 v 10:55 Thomas Petazzoni napsal(a):
> Hello,
>
> This patch series
23 matches
Mail list logo
