Currently custom firmware version number values can only be provided if these
are text based. However, some device firmwares expect structured binary version
info, and do not support the plain text format.
The first patch implements a more flexible soft-version override system.
The second patch
Starting with v3 of the vendor firmware for the TP-Link EAP235-Wall v1,
downgrades to firmware versions below v3 as not allowed. Since OpenWrt
uses version 0.0.0 as a default, this causes the factory install to fail
on devices with a recent firmware. This failure is associated by the
following
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 09.09.2021 23:26, Hauke
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 09.09.2021 22:52, Hauke
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 09.09.2021 23:17, Hauke
Some devices using the safeloader firmware format require a minimum or
specific version to be set in the soft-version metadata partition.
Currently only custom text values can be provided, but not all device
firmware support this format.
Modify the device info struct to allow for more
From: Rafał Miłecki
Linksys uses an extra 0x100 bytes long tail for BCM4908 images.
Signed-off-by: Rafał Miłecki
---
package/utils/bcm4908img/Makefile | 2 +-
package/utils/bcm4908img/src/bcm4908img.c | 22 ++
2 files changed, 23 insertions(+), 1 deletion(-)
diff
From: Rafał Miłecki
This simplifies some operations as it doesn't have to be caculated over
and over. It will also allow adding support for more vendor formats.
Signed-off-by: Rafał Miłecki
---
package/utils/bcm4908img/Makefile | 2 +-
package/utils/bcm4908img/src/bcm4908img.c | 23
Hi, i'm having some compilation error where it seems the buildroot
is using my host bin to compress the ramfs or img image. How can
I backtrack this error? I currently get this error if I change the compression
algo. Could there be a problem in detecting missing tools and
building them?
I'm 100%
On 9/9/21 19:53, Florian Eckert wrote:
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this should also apply to `/usr/lib/os-release`.
Is there any other reason than consistency to change this?
Yes, I have to elaborate on that.
I have a small script that
Build cortexa7 subtarget with DSA driver for MDIO-connected Broadcom
BCM53xxx switches. This is needed for the Lamobo R1 aka. BananaPi
BPi-R1 board which comes with such a switch IC.
Remove old swconfig driver from target kernel config as the only board
using it is now supported by the DSA
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this should also apply to `/usr/lib/os-release`.
Is there any other reason than consistency to change this?
Yes, I have to elaborate on that.
I have a small script that boots the system into a called it
12 matches
Mail list logo
