Add the netdev param to the instance_dump function to make it possible
to verify this for an existing instance.
Signed-off-by: Stijn Tintel
---
service/instance.c | 8
1 file changed, 8 insertions(+)
diff --git a/service/instance.c b/service/instance.c
index 8202d65..9863c7d 100644
explains this, but if there is no default route, we silently
override ra_lifetime.
Add a debug message for the latter case, and explicitly mention
overriding ra_lifetime in both cases.
Signed-off-by: Stijn Tintel
---
src/router.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions
, regardless of the interface
having public addresses or not.
Fixes: #11930
Fixes: 83e14f455817 ("router: advertise removed addresses as invalid in 3
consecutive RAs")
Signed-off-by: Stijn Tintel
---
src/router.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff -
, regardless of the interface
having public addresses or not.
Fixes: #11930
Fixes: 83e14f455817 ("router: advertise removed addresses as invalid in 3
consecutive RAs")
Signed-off-by: Stijn Tintel
---
src/router.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff -
explains this, but if there is no default route, we silently
override ra_lifetime.
Add a debug message for the latter case, and explicitly mention
overriding ra_lifetime in both cases.
Signed-off-by: Stijn Tintel
---
src/router.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions
packets should ever have this
status.
Signed-off-by: Stijn Tintel
---
root/usr/share/firewall4/templates/ruleset.uc | 4
1 file changed, 4 deletions(-)
diff --git a/root/usr/share/firewall4/templates/ruleset.uc
b/root/usr/share/firewall4/templates/ruleset.uc
index 9537ba2..f57836e 100644
in Beacon and Probe Response frames of the first
interface.
This depends on driver and client support. Enabling this will result in
all but the first interface not being visible at all for clients that do
not support it.
Signed-off-by: Stijn Tintel
---
package/network/services/hostapd/files
for target 'bpfeb' [-Werror,-Woption-ignored]
Add -fno-stack-protector to BPF_CFLAGS to fix this.
Signed-off-by: Stijn Tintel
---
package/network/utils/xdp-tools/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/network/utils/xdp-tools/Makefile
b/packa
s with the same limitation, so revert to the orginal
behavior for now, until we have a better solution in place.
Fixes: #13156
Signed-off-by: Stijn Tintel
---
.../patches/991-Fix-OpenWrt-13156.patch | 63 +++
1 file changed, 63 insertions(+)
create mode 100644
packa
rade
/tmp/openwrt-realtek-rtl839x-edgecore_ecs4100-12ph-squashfs-sysupgrade.bin
Signed-off-by: Stijn Tintel
---
I took the DTS from the TIP OpenWiFi project. It was introduced in the
initial commit of their Github repo [1]. I added gpio1 and
label-mac-device, and changed rtl838x-soc in the compatib
not working (D-Link DGS-1210-52, Netgear GS750E, TP-Link
SG2452P/T1600G-52PS), use PHYs at a different address (Panasonic
SwitchM48EG PN28480K), or already have the phy-is-integrated property
set on the PHYs at address 48 and 49.
Signed-off-by: Stijn Tintel
---
.../realtek/files-5.15/drivers/net
According to the Realtek SDK code, the RTL8214FC, RTL8218B and RTL8218FB
all have the same chip ID 0x6276. Let's add a constant for it, as we're
using it in more than one location.
Signed-off-by: Stijn Tintel
---
.../linux/realtek/files-5.15/drivers/net/phy/rtl83xx-phy.c | 6
Taken from TIP OpenWiFi:
https://github.com/Telecominfraproject/wlan-ap/raw/88d6633c85acd4143cfcb1f0a4fdcfdc88f35f3e/feeds/ipq807x_v5.4/ath11k-wifi/board-edgecore-eap101.bin.IPQ6018
Signed-off-by: Stijn Tintel
---
board-edgecore_eap101.ipq6018 | Bin 0 -> 65644 bytes
1 file changed
On 7/11/2020 16:17, Daniel Golle wrote:
> Hi all!
>
> A while ago we have added some useful kernel features to !SMALL_FLASH
> devices[1]. To make more use of that by default in a way which will
> make exploiting potential vulnerabilities in OpenWrt's services much
> harder, it'd be great to also ha
other changes, so let's use -fPIC on
arm64 by default.
While comparing the sizes of 141 packages built with -fpic vs -fPIC,
most packages are either equal or smaller in size. Only 9 of the
compared packages turned out slightly larger.
Signed-off-by: Stijn Tintel
---
rules.mk | 2 +-
1
be backported to 19.O7? I cherry-picked it from master locally
here, applies cleanly afaict.
Thanks!
Stijn
diff --git a/package/libs/openssl/Makefile
b/package/libs/openssl/Makefile
index 77c6d41cec..714ce2059a 100644
--- a/package/libs/openssl/Makefile
+++ b/package/libs/openssl/Makefile
c/fw_sys.config gets created.
When I create /etc/fw_sys.config manually then try to set a value
again, it errors:
# fw_setsys bootpartition 0
Cannot parse config file '/etc/fw_sys.config': Invalid argument
Error: environment not initialized
root@OpenWrt:~# ls /etc/fw_sys.config
/etc/
Hi,
Op woensdag 16 december 2020 om 15u14 schreef Bjørn Mork
:
Stijn Segers writes:
I'm giving this a spin (since I have a Realtek switch now :^)
Great! Thanks for testing
). Fw_printenv prints info as expected but fw_printsys comes up
empty. Not sure if this is expected beha
This patch bumps cryptodev-linux to the latest stable release (1.11) and fixes
compilation against the next LTS (and likely OpenWrt) kernel 5.10.
Signed-off-by: Stijn Segers
---
package/kernel/cryptodev-linux/Makefile | 6 +--
...x-module-loading-with-Linux-v5.0-rc5.patch | 50
.bin
# bootm
* Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it:
# sysupgrade
/tmp//tmp/openwrt-realtek-generic-zyxel_gs1900-8hp-squashfs-sysupgrade.bin
Signed-off-by: Stijn Segers
---
.../realtek/base-files/etc/board.d/02_network | 3 +++
.../linux/realtek
uppercase the vendor name like they carry it themselves (ZyXEL)
and like used elsewhere in the OpenWrt tree.
Signed-off-by: Stijn Segers
---
.../realtek/dts/rtl8380_zyxel_gs1900-10hp.dts | 233 +-
.../realtek/dts/rtl8380_zyxel_gs1900.dtsi | 143 +++
target/linux/realtek
As per the manufacturer's specifications, set the GS1900-10HP PoE power
budget to 77W.
Signed-off-by: Stijn Segers
---
target/linux/realtek/base-files/etc/board.d/02_network | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/linux/realtek/base-files/etc/board.d/02_network
b/t
nwrt-realtek-generic-zyxel_gs1900-8hp-initramfs-kernel.bin
# bootm
* Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it:
# sysupgrade
/tmp//tmp/openwrt-realtek-generic-zyxel_gs1900-8hp-squashfs-sysupgrade.bin
Signed-off-by: Stijn Segers
---
.../realtek/base-files/etc/boa
As per the manufacturer's specifications, set the GS1900-10HP PoE power
budget to 77W.
Signed-off-by: Stijn Segers
---
target/linux/realtek/base-files/etc/board.d/02_network | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/linux/realtek/base-files/etc/board.d/02_network
b/t
applicable.
Stijn Segers (3):
realtek: set PoE power budget for ZyXEL GS1900-10HP
realtek: introduce common DTSI for ZyXEL GS1900-10HP and GS1900-8HP.
realtek: add support for ZyXEL GS1900-8HP.
.../realtek/base-files/etc/board.d/02_network | 6 +
.../dts/rtl8380_netgear_gs110tpp-v1.dts
DTSI, when multiple devices belong to a single family),
reflecting upstream practices.
We also uppercase the vendor name like they carry it themselves (ZyXEL)
and like used elsewhere in the OpenWrt tree.
Signed-off-by: Stijn Segers
---
.../dts/rtl8380_netgear_gs110tpp-v1.dts | 5
set as superceded in Patchwork, but
you might already have been looking at it at that point?).
I will use your remarks for a v3 and send that in.
Thanks for the review!
Stijn
We also uppercase the vendor name like they carry it themselves
(ZyXEL)
and like used elsewhere in the OpenWrt
They aren't listed as discontinued on their sit
either, from
what I can tell.
Do you think that they might be similar?
How is the switch function managed? DSA? or?
Realtek is a DSA target on OpenWrt. On my 10HP e.g. I have lan1 through
lan10 and
a bridge interface for the LAN.
Che
Hi,
Op woensdag 6 januari 2021 om 18:23 schreef Michael Richardson
:
Stijn Segers wrote:
> Op woensdag 6 januari 2021 om 11u22 schreef Michael Richardson
> :
>> The 1900-8/8HP are discontinued by ZyXEL, but the GS1900-16
and 24E seem to
>> still be in prod
Hi Adrian,
Op woensdag 6 januari 2021 om 14:22 schreef Adrian Schmutzler
:
Hi,
essentially the same comments as in the 2/3:
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Stijn Segers
Sent: Mittwoch, 6. Januar 2021 01:45
To
Hi Adrian,
Op woensdag 6 januari 2021 om 21u52 schreef Adrian Schmutzler
:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Stijn Segers
Sent: Mittwoch, 6. Januar 2021 19:25
To: Adrian Schmutzler
Cc: openwrt-devel
As per the manufacturer's specifications, set the GS1900-10HP PoE power
budget to 77W.
Signed-off-by: Stijn Segers
---
target/linux/realtek/base-files/etc/board.d/02_network | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/linux/realtek/base-files/etc/board.d/02_network
b/t
.bin
# bootm
* Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it:
# sysupgrade
/tmp//tmp/openwrt-realtek-generic-zyxel_gs1900-8hp-v{1,2}-squashfs-sysupgrade.bin
Signed-off-by: Stijn Segers
---
.../realtek/base-files/etc/board.d/02_network | 6 +
...
The ZyXEL GS1900-8HP v1, v2 and GS1900-10HP are all built on a similar
Realtek RTL8380M platform. Create a common DTSI in preparation for
GS1900-8HP support, and switch to the macros defined in rtl838x.dtsi.
Signed-off-by: Stijn Segers
---
.../realtek/dts/rtl8380_zyxel_gs1900-10hp.dts | 190
ZyXEL spells its own name all uppercase with just the Y lowercase. Adapt
the realtek target to follow this (other OpenWrt targets already do so).
Signed-off-by: Stijn Segers
---
target/linux/realtek/dts/rtl8380_zyxel_gs1900-10hp.dts | 2 +-
target/linux/realtek/image/Makefile
Move the memory out of the rtl838x.dtsi and into the device family DTSI
or device DTS if applicable. This aligns with upstream practice.
Signed-off-by: Stijn Segers
---
target/linux/realtek/dts/rtl8380_netgear_gs110tpp-v1.dts | 6 +-
target/linux/realtek/dts/rtl8380_zyxel_gs1900-10hp.dts
though.
I'd leave you to choose which version (1 or 2 commits) you prefer.
Thanks, single commit it is. v3 is on the way, I think I addressed your
concerns with it, also the minor ones.
Thanks!
Stijn
Best
Adrian
Cheers
Stijn
>
>> the conclusion seemed to be th
.bin
# bootm
* Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it:
# sysupgrade
/tmp//tmp/openwrt-realtek-generic-zyxel_gs1900-8hp-v{1,2}-squashfs-sysupgrade.bin
Signed-off-by: Stijn Segers
---
.../realtek/base-files/etc/board.d/02_network | 6 +
...
Hi Adrian,
Op donderdag 7 januari 2021 om 19:54 schreef Adrian Schmutzler
:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Stijn Segers
Sent: Mittwoch, 6. Januar 2021 22:45
To: openwrt-devel@lists.openwrt.org
Subject
The ZyXEL GS1900-8HP v1, v2 and GS1900-10HP are all built on a similar
Realtek RTL8380M platform. Create a common DTSI in preparation for
GS1900-8HP support, and switch to the macros defined in rtl838x.dtsi.
Signed-off-by: Stijn Segers
---
.../realtek/dts/rtl8380_zyxel_gs1900-10hp.dts | 189
The Ubiquiti EdgeRouter Lite has three network interfaces. Add a
specific match in /etc/board.d/01_network so they all get set up.
Default to eth0 for WAN and an eth1 + eth2 bridge for LAN.
Signed-off-by: Stijn Segers
---
target/linux/octeon/base-files/etc/board.d/01_network | 3 +++
1 file
se break sysupgrade, but since the default network
layout changes, I'm not sure if we want to keep compatibility?
Thanks
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Prefix EdgeRouter Lite board_name value with vendor abbreviation UBNT, as other
Ubiquiti
devices do, and use full name "Ubiquiti EdgeRouter Lite" as model value.
Signed-off-by: Stijn Segers
---
.../octeon/base-files/lib/preinit/01_sysinfo | 10 --
.../octeon/base-files/l
Hi Adrian,
This should be the final round. Run-tested on a GS1900-10HP. It's still
alive :-).
Thank you!
Stijn
Stijn Segers (2):
realtek: introduce shared DTSI for GS1900 series
realtek: add support for ZyXEL GS1900-8HP v1 and v2
.../realtek/base-files/etc/board.d/02_network
The ZyXEL GS1900-8HP v1, v2 and GS1900-10HP are all built on a similar
Realtek RTL8380M platform. Create a common DTSI in preparation for
GS1900-8HP support, and switch to the macros defined in rtl838x.dtsi.
Signed-off-by: Stijn Segers
---
.../realtek/dts/rtl8380_zyxel_gs1900-10hp.dts | 233
.bin
# bootm
* Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it:
# sysupgrade
/tmp//tmp/openwrt-realtek-generic-zyxel_gs1900-8hp-v{1,2}-squashfs-sysupgrade.bin
Signed-off-by: Stijn Segers
---
.../realtek/base-files/etc/board.d/02_network | 6 +
...
Hi,
Op vrijdag 8 januari 2021 om 16u19 schreef Sander Vanheule
:
Hi Stijn,
On Fri, 2021-01-08 at 14:32 +0100, Stijn Segers wrote:
diff --git a/target/linux/realtek/image/Makefile
b/target/linux/realtek/image/Makefile
index 765e516a0a..39b28b6c67 100644
--- a/target/linux/realtek/image
Hi,
Op vrijdag 8 januari 2021 om 13u29 schreef Adrian Schmutzler
:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Stijn Segers
Sent: Freitag, 8. Januar 2021 11:28
To: openwrt-devel@lists.openwrt.org
Subject: [PATCH 1/2
Hi Adrian,
Op vrijdag 8 januari 2021 om 13u30 schreef Adrian Schmutzler
:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Stijn Segers
Sent: Freitag, 8. Januar 2021 11:28
To: openwrt-devel@lists.openwrt.org
Subject
(edgerouter lite).
could we reuse it?
I have no idea if it's possible, but I was thinking about an additional
DTS that overrides the 'compatible' property. Haven't yet found if this
is possible at all though, overriding that value.
Stijn
On Jan 8, 2021, at 10:11 PM, Stijn
Rename EdgeRouter Lite board_name value and prefix it with vendor abbreviation
UBNT, as done for other Ubiquiti devices in the tree. Ensure backward sysupgrade
compatibility as well.
Signed-off-by: Stijn Segers
---
.../octeon/base-files/lib/preinit/01_sysinfo | 2 +-
.../octeon/base-files
mkdir -p "$ETCBACKUP_DIR"
Am I reading this correctly and is this only keeping track of service
status if you tell sysupgrade to save packages? What's the rationale
behind that?
I have a personal build with all packages preinstalled, so I don't need
that. Would like
Hi Sven,
Op zondag 10 januari 2021 om 22u28 schreef Sven Roederer
:
Am Samstag, 9. Januar 2021, 12:28:31 CET schrieb Stijn Segers:
> @@ -228,6 +229,7 @@ do_save_conffiles() {
>
> if [ "$SAVE_INSTALLED_PKGS" -eq 1 ]; then
> echo "${INSTALLE
Hi Alberto,
Alberto Bursi schreef op 11 januari 2021 03:56:23
CET:
>
>
>On 10/01/21 22:50, Stijn Segers wrote:
>> Hi Sven,
>>
>> Op zondag 10 januari 2021 om 22u28 schreef Sven Roederer
>> :
>>> Am Samstag, 9. Januar 2021, 12:28:31 CET schr
Hi,
Have tested this on a few low-RAM devices, among which a TL-WR841N v7
(32 MiB) and a WNDR3700 v2 (64 MiB).
No idea if this is still necessary/wanted but would be nice to see this
end up in master (and trickle down to 21.xx :-D ).
Tested-by: Stijn Segers
econd flash
with ynezz's test build have produced no issues, so I think the boot-
loop is unrelated to the patches.
Tested-by: Sander Vanheule
I've run-tested this with my own builds (latest master) on the following
targets:
- ath79/generic (WNDR3700v1): with sysupgrade -n
- ramips/
Hi Bjorn,
Op woensdag 20 januari 2021 om 15u09 schreef Bjørn Mork
:
Stijn Segers writes:
- ramips/mt7621 (DIR-860L B1): with sysupgrade (both with and
whithout-n)
Thanks.
Going through this now, I see that this device is using the "seama"
partition comptabile and splitter
ple with a DIR-882 A1 to confirm as well (I
know there are some).
Cheers
Stijn
Tested-by: Stijn Segers
---
.../drivers/mtd/mtdsplit/mtdsplit_uimage.c| 93
++-
.../linux/ramips/dts/mt7620a_fon_fon2601.dts | 3 +-
.../ramips/dts/mt7621_dlink_dir-8xx-a1.dtsi | 3 +-
This adds the PCI ID for the MT7613BE series, found in e.g.
the TP-Link EAP235-Wall v1.
Signed-off-by: Stijn Segers
---
hardware.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/hardware.txt b/hardware.txt
index da843be..ea74929 100644
--- a/hardware.txt
+++ b/hardware.txt
@@ -187,6
icked into thinking easy web UI flashing actually works.
Signed-off-by: Stijn Segers
---
target/linux/ramips/image/mt7620.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ramips/image/mt7620.mk
b/target/linux/ramips/image/mt7620.mk
index 2d0050f986..7f649aff88 100644
--- a/t
(RST &
CLK)
Suggested-by: Sergio Paracuellos
Signed-off-by: Stijn Segers
---
target/linux/ramips/dts/mt7621_dlink_dir-860l-b1.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/target/linux/ramips/dts/mt7621_dlink_dir-860l-b1.dts
b/target/linux/ramips/dts/mt7621_dlink_dir-860l-b1
Hi,
Op zaterdag 13 februari 2021 om 18u23 schreef Chuanhong Guo
:
Hi!
On Sat, Feb 13, 2021 at 5:55 PM Stijn Segers
wrote:
As suggested by Sergio, this adds GPIOs 19 and 8 explicitly into the
DIR-860L DTS, so the PCI-E ports get reset and the N radio (radio1)
on PCI-E port 1 comes up
well until Sergio
pointed out it really isn't.
Cheers
Stijn
Best
Adrian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-
(RST &
CLK)
Suggested-by: Sergio Paracuellos
Signed-off-by: Stijn Segers
---
target/linux/ramips/dts/mt7621_dlink_dir-860l-b1.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/linux/ramips/dts/mt7621_dlink_dir-860l-b1.dts
b/target/linux/ramips/dts/mt7621_dlink_dir-860l-b1
Adds the bits and bolts for the uboot settings for both the ZyXEL
GS1900-8HP v1 and v2.
Signed-off-by: Stijn Segers
---
package/boot/uboot-envtools/files/realtek | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/boot/uboot-envtools/files/realtek
b/package/boot/uboot-envtools/files
This adds the necessary nuts and bolts for the uboot settings for both the
ZyXEL GS1900-8HP v1 and v2.
Signed-off-by: Stijn Segers
---
Changes in v2: fix syntax error, better English.
---
package/boot/uboot-envtools/files/realtek | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package
/tp-link_archer_c20_v1#installation
Signed-off-by: Stijn Segers
---
target/linux/ramips/image/mt7620.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ramips/image/mt7620.mk
b/target/linux/ramips/image/mt7620.mk
index 7f649aff88..f8905ad2b7 100644
--- a/target/linux/ramips
card, disable it (RST & CLK)
Tested-by: Kurt Roeckx
Signed-off-by: Stijn Segers
---
target/linux/ramips/dts/mt7621_netgear_ex6150.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/target/linux/ramips/dts/mt7621_netgear_ex6150.dts
b/target/linux/ramips/dts/mt7621_netgear_ex6150
river cannot be built as a kernel module, enable it in the
>kernel config for all mt7621 devices.
>
>Run-tested on a Netgear R6800.
Works fine here too.
>
>Cc: Stijn Segers
>Cc: Hauke Mehrtens
>Signed-off-by: Sander Vanheule
Tested-by: Stijn Segers
>---
> target/lin
The Netgear GS108T v3 and its GS110TPP v1 sibling apparently label their
u-boot environment parition 'bdinfo' instead of 'u-boot-env'.
Signed-off-by: Stijn Segers
---
package/boot/uboot-envtools/files/realtek | 6 ++
1 file changed, 6 insertions(+)
diff --git a/package
, Netgear sticks to its own naming scheme here.
[1] https://patchwork.ozlabs.org/project/openwrt/list/?series=220259
Signed-off-by: Stijn Segers
---
package/boot/uboot-envtools/files/realtek | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/boot/uboot-envtools/files/realtek
b
Hi!
Op zondag 28 februari 2021 om 10u19 schreef Sander Vanheule
:
Hi Stijn
On Sat, 2021-02-27 at 23:05 +0100, Stijn Segers wrote:
The Netgear GS108T v3 and its GS110TPP v1 sibling apparently label
their u-boot environment parition 'bdinfo' instead of 'u-boot-env'.
Hi Bjørn,
Op zondag 28 februari 2021 om 17u03 schreef Bjørn Mork :
Stijn Segers writes:
Op zondag 28 februari 2021 om 10u19 schreef Sander Vanheule
:
Hi Stijn
On Sat, 2021-02-27 at 23:05 +0100, Stijn Segers wrote:
The Netgear GS108T v3 and its GS110TPP v1 sibling apparently
label
e 14.
Signed-off-by: Stijn Segers
---
target/linux/realtek/dts/rtl8380_netgear_gigabit.dtsi | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/target/linux/realtek/dts/rtl8380_netgear_gigabit.dtsi
b/target/linux/realtek/dts/rtl8380_netgear_gigabit.dtsi
index 2cda3c15a3..d31
This patch set fixes a few loose ends on the Realtek
target. Please backport these to 21.02 as well if we
decide to keep it around for the 21.02 release.
Stijn Segers (3):
realtek: add lua-rs232 to GS1900-10HP profile
realtek: add lua-rs232 to GS110TPP v1 profile
realtek: correct PoE power
The GS110TPP v1 has 8 PoE+ ports so it needs the lua-rs232 package
for PoE manipulation.
Signed-off-by: Stijn Segers
---
target/linux/realtek/image/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/realtek/image/Makefile
b/target/linux/realtek/image/Makefile
index
Somehow all the other supported ZyXEL switches have the lua-rs232 package
defined as an extra package, needed for PoE manipulation, but the
GS1900-10HP does not. Rectify this.
Signed-off-by: Stijn Segers
---
target/linux/realtek/image/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a
tches/gs110tpp
Signed-off-by: Stijn Segers
---
target/linux/realtek/base-files/etc/board.d/02_network | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/realtek/base-files/etc/board.d/02_network
b/target/linux/realtek/base-files/etc/board.d/02_network
index 1e199
Working brilliantly for weeks here as well.
Tested-by: Stijn Segers
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
this could probably be removed completely, but let's
> keep it for now since these drivers are still in development.
>
Merged, thanks!
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
#issuecomment-795174537
I'll bump lldpd to the latest version after this series is merged, and
debug the problem reported by John on the realtek target.
Stijn Tintel (4):
libcap: import from packages feed
libcap: drop invalid copyright header
libcap: bump to 2.48
lldpd: add libcap depen
Signed-off-by: Stijn Tintel
---
package/libs/libcap/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/package/libs/libcap/Makefile b/package/libs/libcap/Makefile
index 0206bd9d1d..29ff75c5cd 100644
--- a/package/libs/libcap/Makefile
+++ b/package/libs/libcap/Makefile
@@ -1,6 +1,4
Signed-off-by: Stijn Tintel
---
package/libs/libcap/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libs/libcap/Makefile b/package/libs/libcap/Makefile
index 29ff75c5cd..b8e45a52c7 100644
--- a/package/libs/libcap/Makefile
+++ b/package/libs/libcap
Now that libcap is in OpenWrt base, we can drop our custom patch to
disable libcap support and have lldpd depend on it instead. This will
allow the monitor process to drop its privileges instead of running as
root, improving security.
Signed-off-by: Stijn Tintel
---
package/network/services
Having libcap in OpenWrt base allows us to enable libcap support in
other packages in base.
In lldpd, this would allow the monitor process to drop its privileges
instead of running as root, improving security. It will also allow us to
drop our patch to disable libcap.
Signed-off-by: Stijn Tintel
On 12/03/2021 10:50, Petr Štetiar wrote:
Stijn Tintel [2021-03-12 01:25:24]:
Hi,
Having libcap in OpenWrt base allows us to enable libcap support in
other packages in base.
there is same functionality available through procd already so essentialy
you're throwing away that effort, incre
relocation R_X86_64_PC32 against symbol
> `__gmp_binvert_limb_table' can not be used when making a shared object;
> recompile with -fPIC
>
> Cc: Stijn Tintel
> Signed-off-by: Eneas U de Queiroz
> ---
>
> There's an error on one architecture, and all others work fine wit
The Netgear R6850 has its EEPROM data sitting at 0x28000 for the 5 GHz radio
and at 0x2 for the 2,4 GHz radio. See forum topic for a hex dump [1].
[1]
https://forum.openwrt.org/t/netgear-r6850-very-low-transmit-power-on-5ghz/90984
Signed-off-by: Stijn Segers
Tested-by: Bernt Ø
Hi Adrian,
Op vrijdag 12 maart 2021 om 22u01 schreef Adrian Schmutzler
:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
On Behalf Of Stijn Segers
Sent: Freitag, 12. März 2021 12:45
To: openwrt-devel@lists.openwrt.org
Cc: m...@david
"enabled",
>"enabled",
>"4.6W",
> "4W"
>],
>"power_budget": "77W",
>"power_consumption": "7.8W"
>}
>
>Tested-by: Bir
tition. This
> + could be used to increase the available memory, by using compressed
> memory.
> endef
>
Stijn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ut that PR either.
Cheers
Stijn
Hauke
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
ope
that needs OpenWrt
master), but I am unqualified to judge the code quality.
All I can say is it runs nicely here (including PoE).
Cheers
Stijn
Hauke
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailma
Hi,
Op donderdag 8 april 2021 om 8u35 schreef Bjørn Mork :
Stijn Segers writes:
A vote for keeping the realtek target here, I have three devices
here
in production. Very happy with them. The main catch I see with
relegating the realtek target to master would be less uptake on the
end
The Netgear GS108T v3 and its GS110TPP v1 sibling apparently label their
u-boot environment parition 'bdinfo' instead of 'u-boot-env'.
Signed-off-by: Stijn Segers
---
package/boot/uboot-envtools/files/realtek | 6 ++
1 file changed, 6 insertions(+)
diff --git a/package
tches/gs110tpp
Signed-off-by: Stijn Segers
---
target/linux/realtek/base-files/etc/board.d/02_network | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/realtek/base-files/etc/board.d/02_network
b/target/linux/realtek/base-files/etc/board.d/02_network
index 1e199
Add the rtl83xx-poe package to the device profiles for the
ZyXEL PoE switches that are currently supported:
- GS1900-10HP
- GS1900-8HP v1
- GS1900-8HP v2
Signed-off-by: Stijn Segers
---
This patch depends on the rtl83xx-poe package sitting in Patchwork:
https://patchwork.ozlabs.org/project
This is a set of assorted fixes and improvements for the realtek target.
Patch #3 depends on the rtl83xx-poe package sitting in Patchwork.
If we keep the realtek target for 21.02, please backport these from
master.
Stijn Segers (3):
uboot-envtools: add support for GS108T v3 & GS110TP
Hi,
Op donderdag 8 april 2021 om 12u33 schreef Stijn Segers
:
The Netgear GS108T v3 and its GS110TPP v1 sibling apparently label
their
u-boot environment parition 'bdinfo' instead of 'u-boot-env'.
I was still carrying prior to Bjorn's last rebase, but this is
On 9/04/2021 01:57, Rui Salvaterra wrote:
> It's in backports-5.4, but it wasn't ever merged. Upstream followed another
> approach, with flow offloading, which has much better performance. Drop this
> obsolete patch and refresh the kernel patches.
Acked-by: Stijn Tintel
1 - 100 of 609 matches
Mail list logo