Am 09.07.2020 um 08:36 schrieb e9hack:
> Hi,
>
> something in the source definition of package stubby is wrong. The build
> process tries to download
> https://github.com/getdnsapi/stubby/stubby-0.3.0.tar.xz but the real download
> location is https://github.com/getdnsapi/stubby/archive/stubby-
Hi,
something in the source definition of package stubby is wrong. The build
process tries to download
https://github.com/getdnsapi/stubby/stubby-0.3.0.tar.xz but the real download
location is https://github.com/getdnsapi/stubby/archive/stubby-0.3.0.tar.gz. It
fails and it builds its own sourc
On 08.07.2020 21:41, m...@adrianschmutzler.de wrote:
-Original Message-
From: Paul Spooren [mailto:m...@aparcar.org]
Sent: Mittwoch, 8. Juli 2020 21:34
To: Rafał Miłecki ; openwrt-devel@lists.openwrt.org
Cc: Rafał Miłecki ; Adrian Schmutzler
; Petr Štetiar ; Moritz
Warning ; Daniel Golle
On 08.07.2020 21:34, Paul Spooren wrote:
I think there is a policy for new DT devices to use the compatible string as
profile.
Multiple targets contain the following line in the target Makefile, which
automatically adds the profile name as supported device:
SUPPORTED_DEVICES := $(subst _,$(co
> -Original Message-
> From: Paul Spooren [mailto:m...@aparcar.org]
> Sent: Mittwoch, 8. Juli 2020 21:34
> To: Rafał Miłecki ; openwrt-devel@lists.openwrt.org
> Cc: Rafał Miłecki ; Adrian Schmutzler
> ; Petr Štetiar ; Moritz
> Warning ; Daniel Golle
> Subject: Re: [PATCH] build: put DT "co
TL;DR: I think the issue is solved for devices using DT, the problem are
the other targets with custom solutions.
I think there is a policy for new DT devices to use the compatible
string as profile.
Multiple targets contain the following line in the target Makefile,
which automatically adds
What is the storage gain archived by changing this?
On 08.07.20 01:27, Rui Salvaterra wrote:
The Single UNIX Specification, Version 3, came out on the 30th January 2002 [1].
There's nothing in the OpenWrt userspace which needs support for legacy SUSv2
compatibility.
[1] http://www.unix.org/vers
The block-mount swapon implementation doesn't support discard, so make zram-swap
depend only on the default BusyBox implementation or, when unavailable, on the
one present in the swap-utils package.
Signed-off-by: Rui Salvaterra
---
package/system/zram-swap/Makefile | 2 +-
1 file changed, 1 ins
From: Rafał Miłecki
The purpose of "board_name" in JSON is matchine OpenWrt running device
with JSON profile entry. Right now it gets filled for devices using DT.
Other targets will require custom solutions or just speciyfing that
value manually.
Signed-off-by: Rafał Miłecki
---
include/image.
Currently, there appears to be no mtd splitter that works with a
firmware partition starting with an ELF kernel loader. Devices using a
loader must provide manual splits, possibly increasing the maintenance
effort for these devices.
This splitter may for example be used with the TP-Link CPE device
To parse the ELF kernel loader, a minimal ELF parser is used that can
handle both ELF32 or ELF64 class loaders. The splitter assumes that the
kernel is always located before the rootfs, whether it is embedded in
the loader or not. If the kernel is located after the rootfs on the
firmware partition,
WRT610N V2 is not detected by the initial network configuration script.
The switch remains unconfigured and wlan/lan vlans are not created.
This adds the correct setup for the device.
Fixes: FS#1869
Suggested-by: Alessandro Radicati
Signed-off-by: Adrian Schmutzler
---
This is built based on
The device can only hold 3.6 MB, but newer images (since 18.06)
are bigger, so flashing a new version fails.
This disables default build for this device based on the bug report
referenced below.
Fixes: FS#1963
Signed-off-by: Adrian Schmutzler
---
https://bugs.openwrt.org/index.php?do=details&
The Single UNIX Specification, Version 3, came out on the 30th January 2002 [1].
There's nothing in the OpenWrt userspace which needs support for legacy SUSv2
compatibility.
[1] http://www.unix.org/version3/pr.html
Signed-off-by: Rui Salvaterra
---
package/utils/busybox/Config-defaults.in | 2 +
The clock_gettime(CLOCK_MONOTONIC) syscall exists for so long that the first
kernel version to support it is not even specified in the man page [1]. Let's
enable it on BusyBox by default. Otherwise, gettimeofday will be used instead,
which will give wrong results if the date/time is reset (time mov
15 matches
Mail list logo
