> > MVEBU devices are not supported in kernel 5.10 based OpenWrt22.03.3 due to
> > a bug.
> > The fix is already in 5.15, but seems to intrusive to backport.
> > Current snapshot builds are on kernel 5.15 already and the issue does not
> > exist anymore.
> > So the easy ways forward are:
>
> Le 4 févr. 2023 à 09:57, Mark Thurston a écrit :
>
>>> MVEBU devices are not supported in kernel 5.10 based OpenWrt22.03.3 due to
>>> a bug.
>>> The fix is already in 5.15, but seems to intrusive to backport.
>>> Current snapshot builds are on kernel 5.15 already and the issue does not
>>>
Hi,
it seems to me that the buildbot's worker amounts are not in balance with the
commit frequency and actual workload of the various branches.
The phase1 images buildbot has only 3 active workers for master (which has
regularly new commits), while the stable 22.03 has 8 workers.
The same i
Hi,
There is ongoing work to address these points for phase1 at least, see
https://gitlab.com/openwrt/buildbot/-/commits/phase1-monomaster
Furthermore with the level of CI that is now being applied, a case could be
made that we do not need to continuously build master as is currently done.
Che
Am 02.02.23 um 11:54 schrieb Robert Marko:
On Tue, 31 Jan 2023 at 23:52, Jan Hoffmann wrote:
Hi Robert,
On 2023-01-30 at 00:08, Robert Marko wrote:
Shouldn't it be possible for the modem driver itself to be fixed
instead of faking
the PCI details?
This hack is definitely far from ideal,
Pstore ramoops support is useful even when there isn't an explicit
panic/crash. We can log all kernel messages via a "console", and then
retrieve them in the event of some non-kernel-panic reset (e.g.,
watchdog).
Since the buffer memory is already reserved, there isn't much overhead
to doing this.
Chromium devices (like Google WiFi) have ramoops memory reserved by the
bootloader. Let's enable the ramoops kernel module by default, so we get
better crash logging.
Signed-off-by: Brian Norris
---
target/linux/ipq40xx/image/chromium.mk | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-
Chromium devices (like OnHub) have ramoops memory reserved by the
bootloader. Let's enable the ramoops kernel module by default, so we get
better crash logging.
Signed-off-by: Brian Norris
---
target/linux/ipq806x/image/chromium.mk | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
dif
