Fix the missing missing ;; after the cAP ac case.
Fixes: 93d9119 ("ipq40xx: add MikroTik cAP ac support")
Signed-off-by: Robert Marko
---
target/linux/ipq40xx/base-files/etc/board.d/01_leds | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ipq40xx/base-files/etc/board.d/01_leds
On 20/02/2022 12:39, Robert Marko wrote:
Fix the missing missing ;; after the cAP ac case.
Fixes: 93d9119 ("ipq40xx: add MikroTik cAP ac support")
Signed-off-by: Robert Marko
Merged. Thanks! Had to change the SoB as it didn't match
and openwrt.git doesn't let me push otherwise.
Cheers,
Remove some (dead) debugging code from the Realtek timer to clean up the
sources of this driver.
Signed-off-by: Sander Vanheule
---
.../files-5.10/arch/mips/kernel/cevt-rtl9300.c | 18 +++---
1 file changed, 3 insertions(+), 15 deletions(-)
diff --git
The Realtek timer node for RTL930x doesn't have any child nodes, making
the use of '#address-cells' quite pointless. It is also not an interrupt
controller, meaning it makes no sense to define '#interrupt-cells'.
The I/O address for this node is also wrong, but this is hidden by the
fact that the
The RTL8231 is an external chip, and not part of the SoC. That means
it is more appropriate to define it in the board specific (base) files,
instead of the DT include for the SoC itself.
Moving the RTL8231 definition also ensures that boards with no GPIO
expander, or an alternative one, don't
The default value for a DT node's status property is already "okay", so
there's no need to specify it again. Drop the status property to clean
up the DTS.
Signed-off-by: Sander Vanheule
---
target/linux/realtek/dts-5.10/rtl8393_zyxel_gs1900-48.dts | 2 --
1 file changed, 2 deletions(-)
diff
The assigned output index for the event timers was quite low, lower even
than the ethernet interrupt. This means that high network load could
preempt timer interrupts, possibly leading to all sorts of strange
behaviour.
Increase the interrupt output index of the event timers to 5, which is
the
GPIO 5 on the RTL8231 can be used to reset the system, but gpio-restart
uses gpiod_set_value. This triggers a kernel warning and backtrace for
GPIO pins that can sleep, such as the RTL8231's. Two warnings are
emitted by libgpiod, and a third warning by gpio-restart itself after it
fails to restart
On Sun, 20 Feb 2022 at 14:28, Christian Lamparter wrote:
>
> On 20/02/2022 12:39, Robert Marko wrote:
> > Fix the missing missing ;; after the cAP ac case.
> >
> > Fixes: 93d9119 ("ipq40xx: add MikroTik cAP ac support")
> > Signed-off-by: Robert Marko
>
> Merged. Thanks! Had to change the SoB as
When driven by a GPIO pin, the system LED needs to be configured as
active high. Otherwise the LED switches off after booting and
initialisation.
Fixes: 47f5a0a3eed5 ("realtek: Add support for ZyXEL GS1900-48 Switch")
Signed-off-by: Sander Vanheule
---
On 2/19/22 20:16, Petr Štetiar wrote:
Linus Walleij [2021-04-14 15:23:11]:
Hi,
Several targets enable this selectively, probably some of
them should consider disabling it and see what happens.
we're now using musl 1.2.2 so we should be good to go. So if you want to
proceed, can you please
On 2/17/22 15:51, Petr Štetiar wrote:
This is amalgamation of backported changes since 4.7.0-stable release:
Sergey V. Lobanov (2):
5b13b0b02c70 wolfssl: update to 5.1.1-stable
7d376e6e528f libs/wolfssl: add SAN (Subject Alternative Name) support
Andre Heider (3):
3f8adcb215ed
Bootargs for devices in the realtek target were previously consolidated
in commit af2cfbda2bf5 ("realtek: Consolidate bootargs"), since all
devices currently use the same arguments.
Commit a75b9e3ecb61 ("realtek: Adding RTL930X sub-target") reverted this
without any argumentation, so let's undo
The address in some node names doesn't match the actual offset specified
in the DT node. Update the names to fix this.
While fixing the node names, also drop the unused node labels.
Fixes: 0a7565e53653 ("realtek: Update rtl839x.dtsi for realtek,rtl-intc, new
gpio controller remove RTL8231
The I/O base address for the timers was hardcoded into the driver,
or derived from the HW IRQ number as an even more horrible hack. All
supported SoC families have these timers, but with hardcoded addresses
the code cannot be reused right now.
Request the timer's base address from the DT
The new timer provided to support RTL930x SoCs has evaded proper review
before getting merged, so some clean-ups are now required. These patches
should fix the most glaring issues with the code.
These changes were tested on a ZyXEL XGS1250-12.
Sander Vanheule (3):
realtek: clean up RTL930x
Hi,
during development I came across situations where the RTL839x
SoC's own reset did not always completely reset its state.
U-Boot was no longer able to boot via tftp afterwards.
This is the same situation we see on the RTL838x.
While users will hopefully never mess up the SoC as during
Hi
I have a Huawei ME909s-120.
When I switch directly from configuration #2 to #3, MBIM, the modem
will not respond to any MBIM messages.
I need to go via configuration #0, and a short delay, and then to
configuration #3 to make my modem to
respond.
It´s the same for Huawei ME909s as well.
BR
On Sun, Feb 20, 2022 at 09:13:24PM +0100, Birger Koblitz wrote:
> Hi,
>
> during development I came across situations where the RTL839x
> SoC's own reset did not always completely reset its state.
> U-Boot was no longer able to boot via tftp afterwards.
> This is the same situation we see on the
On Thu, Feb 03, 2022 at 01:44:11AM +0100, Ansuel Smith wrote:
> Add support for multi-cpu dsa. This is a reworked version of the RFC patch
> proposed some time ago.
> By default every dsa port is connected to the first cpu port and the command
> 'ip link set PORT cpu CPU_PORT' can be used to
On Thu, Feb 03, 2022 at 01:44:12AM +0100, Ansuel Smith wrote:
> Add support for cpu set useful to set CPU port for dsa devices.
Please also document the newly added 'cpu' parameter in the command-
line output -- the manpage isn't even installed/available for OpenWrt
users.
>
> Signed-off-by:
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 ---
Branch: refs/heads/master
Hi,
All the major new features for the next OpenWrt major release are mostly
merged into master. The kernel 5.10 upgrade for the bcm63xx target is
still missing.
Paul created a issue to track the remaining tasks:
https://github.com/openwrt/openwrt/issues/9248
This will be extended with new
Thanks for all the work done towards this.
And thankfully SELinux will not be activated by default.
Regards
Fernando
On 20/02/2022 19:57, Hauke Mehrtens wrote:
Hi,
All the major new features for the next OpenWrt major release are
mostly merged into master. The kernel 5.10 upgrade for the
>
> On Thu, Feb 03, 2022 at 01:44:12AM +0100, Ansuel Smith wrote:
> > Add support for cpu set useful to set CPU port for dsa devices.
>
> Please also document the newly added 'cpu' parameter in the command-
> line output -- the manpage isn't even installed/available for OpenWrt
> users.
>
Should
From: Chuanhong Guo
It's reported that current memory detection code occasionally detects
larger memory under some bootloaders.
Current memory detection code tests whether address space wraps around
on KSEG0, which is unreliable because it's cached.
Rewrite memory size detection to perform the
On Thu, Feb 17, 2022 at 11:51 AM Petr Štetiar wrote:
>
> This is amalgamation of backported changes since 4.7.0-stable release:
>
> Sergey V. Lobanov (2):
>
> 5b13b0b02c70 wolfssl: update to 5.1.1-stable
> 7d376e6e528f libs/wolfssl: add SAN (Subject Alternative Name) support
>
> Andre
This changes the configuration of engines from the global openssl.cnf to
files in the /etc/ssl/engines.cnf.d directory. The engines.cnf file has
the list of enabled engines, while each engine has its own configuration
file installed under /etc/ssl/engines.cnf.d.
Patches were refreshed with
This enables an engine during its package's installation, by adding it
to the engines list in /etc/ssl/engines.cnf.d/engines.cnf.
The engine build system was reworked, with the addition of an engine.mk
file that groups some of the engine packages' definitions, and could be
used by out of tree
This series builds upon what was first started by Daniel Danzberger,
with some suggestions by Florian Eckert to enable the engines when they
are installed.
The series split is subject to discussion:
- the first commit does a patch cleanup proposed by Rosen Penev, and
also splits the
This uses uci to configure engines, by generating a list of enabled
engines in /var/etc/ssl/engines.cnf from engines configured in
/etc/config/openssl:
config engine 'devcrypto'
option enabled '1'
Currently the only options implemented are 'enabled', which defaults to
true and
On Sat, Feb 19, 2022 at 12:01 PM Petr Štetiar wrote:
>
> Alex Henrie [2022-01-20 22:06:07]:
>
> Hi,
>
> it looks like you need just this two variables:
>
> DEVICE_MODEL := EMG2926-Q10A
> RAS_BOARD := AAVK-EMG2926Q10A
>
> so following copy seems a bit much against my DRY taste:
>
> > +define
The Zyxel EMG2926-Q10A is 99% the Zyxel NBG6716, but the bootloader
expects a different product name when flashing over TFTP. Also, the
EMG2926-Q10A always has 128 MiB of NAND flash whereas the NBG6716
reportedly can have either 128 MiB or 256 MiB.
Signed-off-by: Alex Henrie
---
v2: Avoid
On Mon, Feb 21, 2022 at 01:37:10AM +0100, Ansuel Smith wrote:
> >
> > On Thu, Feb 03, 2022 at 01:44:12AM +0100, Ansuel Smith wrote:
> > > Add support for cpu set useful to set CPU port for dsa devices.
> >
> > Please also document the newly added 'cpu' parameter in the command-
> > line output --
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 19.02.2022 12:04, Petr Štetiar
35 matches
Mail list logo
