On Thu, Sep 30, 2021 at 1:05 PM Nick wrote:
>
>
> On 9/30/21 21:43, Daniel Golle wrote:
> > On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote:
> >> On 30/09/2021 01:19, Nick wrote:
> >>> On 9/29/21 22:28, Hauke Mehrtens wrote:
> >>>
> kernel 5.10:
> We should get all targets t
(I'm cc'ing both openwrt-devel and openwrt-adm since both will be involved in
the decision)
> On Sep 29, 2021, at 4:28 PM, Hauke Mehrtens wrote:
>
> The OpenWrt 21.02 release is done and we should plan the next release.
> We already talked about this in the last meeting, see
> https://openwrt.
On 9/30/21 10:01, Nick wrote:
On 9/30/21 21:43, Daniel Golle wrote:
On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote:
On 30/09/2021 01:19, Nick wrote:
On 9/29/21 22:28, Hauke Mehrtens wrote:
kernel 5.10:
We should get all targets to kernel 5.10. All targets which are not
on ke
Hello,
I'm trying to mount a USB storage device using hotplug.d/block.
However, it never works during boot because "hotplug.d/block" is
triggered before modules.d are loaded. It only works if the filesystem
was already loaded by modules-boot.d (normally ext4).
I'm manually loading all fs modules
On 9/30/21 21:43, Daniel Golle wrote:
On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote:
On 30/09/2021 01:19, Nick wrote:
On 9/29/21 22:28, Hauke Mehrtens wrote:
kernel 5.10:
We should get all targets to kernel 5.10. All targets which are not
on kernel 5.10 when we branch off sho
On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote:
> On 30/09/2021 01:19, Nick wrote:
> > On 9/29/21 22:28, Hauke Mehrtens wrote:
> >
> >> kernel 5.10:
> >> We should get all targets to kernel 5.10. All targets which are not
> >> on kernel 5.10 when we branch off should get removed.
> >
On 30/09/2021 01:19, Nick wrote:
> On 9/29/21 22:28, Hauke Mehrtens wrote:
>
>> kernel 5.10:
>> We should get all targets to kernel 5.10. All targets which are not
>> on kernel 5.10 when we branch off should get removed.
> Kernel 5.15 could be also a LTS Kernel that should be released in the
> end
Hi Paul,
Thanks for the update, looks good to me.
On Thu, 2021-09-30 at 20:15 +0300, Paul Fertser wrote:
> The bootloader can leave the GPIO expander in a state which doesn't have
> output drivers enabled so GPIOs will properly work for input but output
> operations will have no effect.
>
> To a
Rich Brown wrote:
> - Having a firm feature freeze date decreases stress. If a particular
> feature is done/substantially working, it goes in. If it's not quite
> ready, it can skip this release, and get into the next release. (The
> alternative is what I think happened with DSA.
Heads up:
Forum has several reports that downloads.openwrt.org now fails in 21.02.0 and
master due to invalid certificate.
Possibly related to the letsencrypt's old root certificate expiring today
Or wolfssl not liking the remaining root cert?
https://letsencrypt.org/docs/dst-root-ca-x
When KERNEL_PERF_EVENTS is enabled in OpenWrt, or PERF_EVENTS in the
kernel config, the RPI_AXIPERF is exposed. Add it to the subtarget
kernel configs to avoid build failures.
Signed-off-by: Stijn Tintel
---
target/linux/bcm27xx/bcm2708/config-5.10 | 1 +
target/linux/bcm27xx/bcm2708/config-5.4
On 30/09/2021 19:58, Stijn Tintel wrote:
> When building an image for the bcm27xx target, some combinations of
> config options will fail to build due the SND_SOC_AD193X_SPI kernel
> config symbol being missing.
>
> The problem only occurs on bcm27xx as the target contains a patch that
> modifies t
When building an image for the bcm27xx target, some combinations of
config options will fail to build due the SND_SOC_AD193X_I2C and
SND_SOC_AD193X_SPI kernel config symbols being missing.
The problem only occurs on bcm27xx as the target contains a patch that
modifies the Kconfig file containing t
The bootloader can leave the GPIO expander in a state which doesn't have
output drivers enabled so GPIOs will properly work for input but output
operations will have no effect.
To avoid disrupting the boot in case the bootloader left direction and
data registers in an inconsistent state (e.g. pull
When building an image for the bcm27xx target, some combinations of
config options will fail to build due the SND_SOC_AD193X_SPI kernel
config symbol being missing.
The problem only occurs on bcm27xx as the target contains a patch that
modifies the Kconfig file containing the symbol. In the vanill
Cc Tobias, author of the 8f9cd1af0f9c ("swconfig: fix Broadcom b53 support").
Another option would be to revert above commit (.of_match_table part anyway).
On 30.09.2021 16:40, Rafał Miłecki wrote:
From: Rafał Miłecki
OpenWrt downstream b53 MDIO driver is bugged as it:
1. Registers as PHY dev
From: Rafał Miłecki
OpenWrt downstream b53 MDIO driver is bugged as it:
1. Registers as PHY device driver (while switch is an MDIO device)
2. Provides of_match_table
That results in bypassing kernel bus matching checks and probing b53 for
MDIO device treated as PHY device. It doesn't work as PHY
On Thu, Sep 30, 2021 at 02:49:57PM +0200, Florian Eckert wrote:
> Since the update of kernel from 5.4 to 5.10 in the openwrt master branch
> [1],
> I have problems with additional hardware on the I2C (SMBus) of my APU3.
>
> The Linux upstream removed the platform data support for my I2C IO-Expande
Since the update of kernel from 5.4 to 5.10 in the openwrt master branch
[1],
I have problems with additional hardware on the I2C (SMBus) of my APU3.
The Linux upstream removed the platform data support for my I2C
IO-Expander mcp23s08 [3].
Because of this change I could not use my own written p
Héllo,
https://github.com/openwrt/packages/pull/16244
Is there any chance of integration ?
Thanks…
G.Kerma
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Fixes the boot loader LZMA decompression issue:
LZMA ERROR 1 - must RESET board to recover
Signed-off-by: Mirko Parthey
---
Please consider backporting to openwrt-21.02, which is also affected.
target/linux/ramips/image/rt305x.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/
Hi Paul,
On Wed, 2021-09-29 at 23:52 +0300, Paul Fertser wrote:
> The bootloader can leave the GPIO expander in a state which doesn't have
> output drivers enabled so GPIOs will properly work for input but output
> operations will have no effect.
>
> To avoid disrupting the boot in case the bootl
22 matches
Mail list logo
