So wonderful to see matter begin to matter!
https://forum.openwrt.org/t/cerowrt-ii-would-anyone-care/110554
regrettably I am mostly retired from openwrt now and do not understand
the workflow.
On Thu, Jul 27, 2023 at 2:14 PM Karsten Sperling via openwrt-devel
wrote:
>
> The sender domain has a
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hello,
I’m part of an effort by
From: Tomasz Maciej Nowak
- refresh patches
- adjust kernel config, with main change enabling VIDEO_TEGRA_VDE,
necessary for driving power domain responsible for clean reboot
- adjust LED patch to changes in LED drivers
Signed-off-by: Tomasz Maciej Nowak
---
From: Tomasz Maciej Nowak
Testing results were all good, so move target to newer kernel by default.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/tegra/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/tegra/Makefile b/target/linux/tegra/Makefile
From: Tomasz Maciej Nowak
Prepare for addition of kernel 6.1 support.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/tegra/config-6.1 | 504 ++
...interrupts-due-to-tegra2-silicon-bug.patch | 77 +++
...enable-front-panel-leds-in-TrimSlice.patch | 46 ++
From: Tomasz Maciej Nowak
Straightforward update and small generic config modification.
Tomasz Maciej Nowak (4):
kernel: 6.1: move NO_ARRAY_BOUNDS to generic
tegra: copy patches and config for kernel 6.1
tegra: initial kernel 6.1 support
tegra: switch to 6.1 kernel
From: Tomasz Maciej Nowak
Array bounds are disabled for GCC 11 or later. It's better to track it in
global (generic) config.
Signed-off-by: Tomasz Maciej Nowak
---
target/linux/bcm27xx/bcm2708/config-6.1 | 2 --
target/linux/bcm27xx/bcm2709/config-6.1 | 2 --
Hi Martin,
On 27.07.23 13:23, Martin Schiller wrote:
When preparing the kernel sources to build the kernel headers, currently
only the patches from the generic folder are applied, but not from the
actual selected target.
This is basically understandable if one assumes that one wants to use a
From: Tomasz Maciej Nowak
Alter booting command in U-Boot on first boot after upgrade to workaround
the kernel size limitation. The kernel size read from flash will be 8MiB,
which should suffice for forseable future. As precaution a warning
interupting upgrade is emited, explaining what to do.
From: Tomasz Maciej Nowak
'bootipq' command on some devices, with kernel on NOR flash chip, read
kernel partition size from Qualcomm proprietary partition table, which
seems to be stored in MIBIB partition. The partition table can be read
by 'smeminfo' command in U-Boot command line interface.
From: Tomasz Maciej Nowak
Some of devices having kernel on NOR flash could reach limit of kernel
partition size at 4MiB and soft-brick them. Unfortunately we don't know
if all of them are affected, thus kernel size limit is added to all of
remaining ones. Later commit allows for some devices to
From: Tomasz Maciej Nowak
Devices allowing to boot LZMA or GZIP compressed kernel didn't hit yet
the 4MiB boundary for kernel size, thus allowing to prepare workaround
for the issue, without need for serial console attachment.
The workaround is modifying 'bootcmd' variable in U-Boot environment
When preparing the kernel sources to build the kernel headers, currently
only the patches from the generic folder are applied, but not from the
actual selected target.
This is basically understandable if one assumes that one wants to use a
toolchain for different targets with the same
13 matches
Mail list logo
