On Sun, Jul 18, 2021 at 10:30:20PM +0200, Adrian Schmutzler wrote:
> > The last time I tried it was very confusing. When I first read about "new
> > fresh
> > installation", I thought: "install without keeping settings".
> > However, OpenWrt returned an image check failure, even when I did not
>
On Sun, 18 Jul 2021, at 20:45, Rich Brown wrote:
> I have updated the DSA Mini-tutorial in the playground:
> https://openwrt.org/playground/richb/dsa-mini-tutorial
>
> I finished the first section ("Bridging all LAN ports"), and I am going
> to stop editing now, because:
>
> 1) I need someone
Based on the discussion on the mailing list [1], the patch which was
reverted, it reverts only one patch without the subsequent ones.
This leads to the SoC scaling issue not using a CPU parent clock, but
it uses DDR clock. This is done for all variants, and it's wrong because
commits (hacks) that
Tested on ath79/generic, without issues.
Signed-off-by: Rui Salvaterra
---
toolchain/binutils/Config.in | 4 ++
toolchain/binutils/Config.version | 4 ++
toolchain/binutils/Makefile | 4 ++
.../2.37/300-001_ld_makefile_patch.patch | 22
Am 19.07.2021 um 16:24 schrieb Ansuel Smith:
hi,
some dtsi still use the old implementation as they have to be manually
migrated. Does it cause any problem ?
I don't see a problem. I did check the dtsi files of the two routers which I'm
using. One is migrated and the other one was still
JFY, this series of commits broke Gl.Inet mt-1300 beryl(mt7621) - I've
had to revert it in my local build. So basically the problem is that
device cannot read it's mac from partition and every reboot it
generates a new one.
пн, 19 июл. 2021 г. в 17:32, Ansuel Smith :
>
> hi,
> some dtsi still use
Am 19.07.2021 um 16:41 schrieb Ansuel Smith:
The dts has been migrated with a script and we decided to remove the
dtsi that caused some compilation problem.
We still need to take a decision for the device that have dtsi that
declare mtd-mac-address using partition tag declared in user dts
(dtsi
hi,
some dtsi still use the old implementation as they have to be manually
migrated. Does it cause any problem ?
> Hi, it looks like, that qca9558_tplink_archer-c.dtsi is missing in commit
> abc17bf (ath79: convert mtd-mac-address to nvmem implementation). Regards,
> Hartmut
The dts has been migrated with a script and we decided to remove the
dtsi that caused some compilation problem.
We still need to take a decision for the device that have dtsi that
declare mtd-mac-address using partition tag declared in user dts
(dtsi use partition declared in the dts)
> I don't
Hi,
it looks like, that qca9558_tplink_archer-c.dtsi is missing in commit abc17bf
(ath79: convert mtd-mac-address to nvmem implementation).
Regards,
Hartmut
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
This method of configuring the switch would also make it substantially
easier to make a migration script for migrating from swconfig to DSA.
On Wed, Jul 7, 2021 at 11:45 PM Arınç ÜNAL wrote:
>
> This is the proper way of managing the switch ports and VLANs on the
> DSA driver. All of the switch
> I believe what he meant to say was to make another 19.07.x point
> release with an updated sysupgrade mechanism which would improve the
> situation when upgrading to 21.02.x and, for example, allow
> flashing with non-matching DEVICE_COMPAT_VERSION already when
> specifying the '-n' flag to not
> -Original Message-
> From: Daniel Golle [mailto:dan...@makrotopia.org]
> Sent: Montag, 19. Juli 2021 10:13
> To: Adrian Schmutzler
> Cc: 'Luiz Angelo Daros de Luca'; 'Hauke Mehrtens'; 'Rich Brown'; 'OpenWrt
> Development List'; 'Jo-Philipp Wich'; 'Kevin 'ldir' Darbyshire-Bryant'; 'John
>
> It could happen during early boot stages, after FS are mounted, before
> services are started, something similar to uci-defaults, but not in a "run
> once"
> way.
> It would cover both upgrades with confs and restores. We are asking the
> user to upgrade without saving confs but nothing will
On 19/07/21 21:11, Luiz Angelo Daros de Luca wrote:
This is not a migration script but a mitigation. A 21.02 image should
detect during boot if the current network config was for swconfig in a
system using DSA.
It could happen during early boot stages, after FS are mounted, before
services
Hi Hans,
On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
Hi,
In general the 21.02-rc3 looks good, but we still have some problems.
Currently we still have these problem:
- DHCPv6 broken if lease times < 12h chosen
-
Hi Hauke,
On Mon, Jul 19, 2021 at 8:05 PM Hauke Mehrtens wrote:
>
> Hi Hans,
>
> On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
> > Hi,
> >
> > In general the 21.02-rc3 looks good, but we still have some problems.
> >
> > Currently we still have these problem:
>
>
>
> > - DHCPv6 broken if lease
From: Ian Chang
Hardware specification
--
* CN9130 SoC, Quad-core ARMv8 Cortex-72 @ 2200 MHz
* 4 GB DDR
* 4 GB eMMC
* mmcblk0
- mmcblk0p164M kernel_1
- mmcblk0p264M kernel_2
- mmcblk0p3 512M rootfs_1
- mmcblk0p4 512M rootfs_2
- mmcblk0p5 512M Reserved
-
18 matches
Mail list logo
