Hi all,
I just found the following comment in the DTS file for RT-AC58U:
* TODO: change to label = "ubi" once we drop 4.14.
* also drop the bootargs-append and all the
* userspace CI_UBIPART="UBI_DEV" remains.
We _have_ dropped 4.14 now.
I'm just telling i
This fixes a regression after a kernel change in 5.4.69 [1] that
led to build failure on oxnas/ox820:
drivers/ata/sata_oxnas.c:2238:13: error: initialization of
'enum ata_completion_errors (*)(struct ata_queued_cmd *)'
from incompatible pointer type
'void (*)(struct ata_queued_cmd *)' [-We
On Fri, 9 Oct 2020 at 14:22, Adrian Schmutzler wrote:
>
> Hi all,
>
> in master, we currently support kernels 5.4 and 4.19.
>
> All targets build with 5.4 by default, so 4.19 is just there and can
> theoretically be used for regression testing (if it still works).
> However, since our last releas
On 2020-10-09 14:33, abnoeh wrote:
20. 10. 9. 오후 8:29에 Bas Mevissen 이(가) 쓴 글:
So I think it is reasonably safe to do the initial setup over HTTP
(without the "S") at the first boot if there are no certificates
available from a previous OpenWRT install. Then the user can setup the
WAN side if nee
On 2020-10-09 14:19, Adrian Schmutzler wrote:
Hi all,
in master, we currently support kernels 5.4 and 4.19.
All targets build with 5.4 by default,
In other words: 4.19 is no longer required.
so 4.19 is just there and can
theoretically be used for regression testing
In that case, one can r
20. 10. 9. 오후 8:29에 Bas Mevissen 이(가) 쓴 글:
So I think it is reasonably safe to do the initial setup over HTTP
(without the "S") at the first boot if there are no certificates
available from a previous OpenWRT install. Then the user can setup the
WAN side if needed and upload (from local PC), gen
Hi all,
in master, we currently support kernels 5.4 and 4.19.
All targets build with 5.4 by default, so 4.19 is just there and can
theoretically be used for regression testing (if it still works).
However, since our last release used 4.14, 4.19 effectively is just an interim
step that has never
On 09/10/2020 08:29, Bas Mevissen wrote:
On 2020-10-04 15:48, abnoeh wrote:
.
So I think it is reasonably safe to do the initial setup over HTTP
(without the "S") at the first boot if there are no certificates
available from a previous OpenWRT install. Then the user can setup the
WAN side if
On 2020-10-04 15:48, abnoeh wrote:
Few months ago there was some debate for how we handle certificate for
luci page: make user to click though certificate warning is not that
great for security so here is a proposal for autometically assign a
worldwide unique subdomain and how to make valid cert
Op 6 okt. 2020, om 19:20 heeft Alberto Bursi het
volgende geschreven:
> ...
> Just add screenshots in the first install tutorial and/or something to the
> documentation that explains how to do that in case someone really is very new
> and has never needed to accept a self-signed certificate.
A
On Mon, Oct 05, 2020 at 12:34:14PM -0400, Michael Richardson wrote:
> Stefan Lippers-Hollmann wrote:
>> On 2020-10-04, abnoeh wrote:
>>> Few months ago there was some debate for how we handle certificate
>>> for luci page: make user to click though certificate warning is not
>>> that great for sec
On Thu, Oct 08, 2020 at 12:10:17AM +0200, Alberto Bursi wrote:
> On 07/10/20 15:34, abnoeh wrote:
>>> However, I think you are assuming a RA/DHCP-based WAN connection.
>>> For PPPoE (which is still a thing in a lot of places, including
>>> developing world, where last mile is often wifi), this won'
Hi Hans,
I have the confirmation, this change fixed my problem.
Given the fact that my commit fixes an obvious programming error, I
don't think I need to put a detailed explanation in the commit
description.
BR,
Alin
On Thu, Oct 8, 2020 at 2:35 PM Alin Năstac wrote:
>
> Hi Hans,
>
> The issue
13 matches
Mail list logo
