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 ---
Hi
[this equally applies to all t
On 30/01/2024 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related to IPQ (ipq80
Create a script for automating kernel version changes. This
generates a pair of commits which cause history to remain attached to
all versioned configuration files.
Crucially this makes `git blame` work without needing
--find-copies-harder, which is too slow for routine use. This also
updates *e
Don't change the name of fw1/firmware in DT. If you change it to fw1
then it will match the cmdline definition and the of_node is copied.
And the uimage splitter will parse it based on compatible match.
What I suggest is keeping everything else as-is, but define
CONFIG_MTD_SPLIT_FIRMWARE=y
I'm
Bjorn I have tested your suggestion too but same result happens, the DTS
in my buildroot is manually edited so partitions are called fw1 and fw2
and not firmware and fw2, but the behaviour is identical
[ 0.337578] spi-nor spi0.0: w25q128 (16384 Kbytes)
[ 0.342531] mtd: Found partition def
Hi Christian,
On Tue, 2024-01-30 at 19:15 +0100, Christian Marangi (Ansuel) wrote:
> I think Robert is a good addition to our team and would massively help
> me (Ansuel) in maintaining each IPQ target and review all the related
> PR on github and patchwork.
> I would like to add Robert to the Open
To me it looks like the uimage-fw parser isn't running at all in the
second case. I assume that is because CONFIG_MTD_SPLIT_FIRMWARE is
unset.
The reason splitting works in the first case is because of
421-drivers-mtd-parsers-add-nvmem-support-to-cmdlinepart.patch
which copies the "firmware" of_n
Digging a bit more into the code I found the culprit
The function mtd_partition_split added by the patch
400-mtd-mtdsplit-support.patch
After finding first partition that is either named rootfs or have
"linux,rootfs" property no matter if it is contained into a "super"
partition named "firm
On Wed, Feb 07, 2024 at 11:53:55AM +0100, Jonas Gorski wrote:
> On Wed, 7 Feb 2024 at 02:48, Elliott Mitchell wrote:
> >
> > Create a script for automating kernel version changes. This
> > generates a pair of commits which cause history to remain attached
> > to all versioned configuration files.
One of two bdf for the device: Ikuai sw8
This one for qcn9074 wifi5 chip (stock fw: qcn9000/bdwlan.ba0).
```
[
{
"board": [
{
"names": [
"bus=pci,qmi-chip-id=0,qmi-board-id=255,variant=Ikuai-SW8"
],
"data"
On Wed, 7 Feb 2024 at 12:58, Felix Baumann via openwrt-devel
wrote:
> Am 7. Februar 2024 11:53:55 MEZ schrieb Jonas Gorski :
> >On Wed, 7 Feb 2024 at 02:48, Elliott Mitchell wrote:
> >>
> >> Create a script for automating kernel version changes. This
> >> generates a pair of commits which cause
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 ---
Am 7. Februar 2024 11:53:55 MEZ sc
On Wed, 7 Feb 2024 at 02:48, Elliott Mitchell wrote:
>
> Create a script for automating kernel version changes. This
> generates a pair of commits which cause history to remain attached
> to all versioned configuration files.
Why is this script needed? What exactly does it do? Does it preserve
b
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 ---
On Tue, Jan 30, 2024 at 7:17 PM Ch
14 matches
Mail list logo