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 Wed, Oct 19, 2022 at 1:10 AM
On Tue, Oct 18, 2022 at 3:50 PM Peter Naulls wrote:
>
> On 10/18/22 17:10, Lukas Zeller wrote:
> .
> >
> > Just not any more - the mt7621 had this too. I currently patch it back into
> > 22.03's gpio-mt7621.c for my builds and set base in the DTS, see [3]
> >
> > I can follow the rationale to get
On 10/18/22 17:10, Lukas Zeller wrote:
.
Just not any more - the mt7621 had this too. I currently patch it back into
22.03's gpio-mt7621.c for my builds and set base in the DTS, see [3]
I can follow the rationale to get rid of legacy GPIOs, but in the context
of experimenting platforms, where
Hi Peter and Martin,
> On 18 Oct 2022, at 22:02, Peter Naulls wrote:
>
> On 10/18/22 15:55, Martin Blumenstingl wrote:
>> [...] my understanding is that the recommended way for
>> accessing GPIOs from userspace (in case that's what you need) should
>> be done through libgpiod.
>
> Thanks for
On 10/16/22 16:58, Sander Vanheule wrote:
Hi Alex,
Hi
[snip]
+
+ if (current_trigger != rtl_trigger && !bitmap_empty(group->ports,
group->size)) {
+ dev_warn(ctrl->dev, "cannot map (%d,%d) to group %d: 0x%02x
!= 0x%02x\n",
+ led->port, led->index,
On 10/18/22 15:55, Martin Blumenstingl wrote:
Hello Peter,
On Tue, Oct 18, 2022 at 9:34 PM Peter Naulls wrote:
Looks like there was some code loss when the driver came from an earlier kernel
series. Without this, my MT7621 board starts its GPIO offsets at 416 (why that
number, I don't
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 ---
Hello Peter,
On Tue, Oct 18,
Looks like there was some code loss when the driver came from an earlier kernel
series. Without this, my MT7621 board starts its GPIO offsets at 416 (why that
number, I don't know):
--- a/drivers/gpio/gpio-mt7621.c2022-10-18 15:03:42.596454871 -0400
+++ b/drivers/gpio/gpio-mt7621.c
út 18. 10. 2022 v 16:43 odesílatel Oldřich Jedlička
napsal:
>
> Hi,
>
> pá 9. 9. 2022 v 11:21 odesílatel Torsten Duwe napsal:
> >
> > On Thu, 8 Sep 2022 19:51:06 +0200
> > Thibaut wrote:
> >
> > > The issue was random. The client had a GUA assigned, below is the ipv6
> > > routing table at the
Hi,
pá 9. 9. 2022 v 11:21 odesílatel Torsten Duwe napsal:
>
> On Thu, 8 Sep 2022 19:51:06 +0200
> Thibaut wrote:
>
> > The issue was random. The client had a GUA assigned, below is the ipv6
> > routing table at the time of the issue:
> >
> > $ ip -6 route
> > 2a0e:e701:11c2::/64 dev bond0
Hi,
We decided to publish our internal fork of the Timesys SBOM Tool we found on
github. You find our version at: https://github.com/ads-tec/sbom-openwrt
It takes a complete OpenWRT build tree as input and will generate a SBOM
in CycloneDX JSON Format for the currently configured image.
This
For devices with a NAND and a NOR chip, it was noticed that the order of
initialization can be different between various kernel versions (4.4 vs.
5.4). As result, the mtd index changes for the u-boot-env partition - but
the uboot-envtool still kept the old partition index.
And since some devices
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* openwrt: jail: ignore missing .dynamic sect
-
http://patchwork.ozlabs.org/project/openwrt/patch/mailman.24701.1665327047.4154159.openwrt-de...@lists.openwrt.org/
- for: OpenWrt development
was: New
On some of the hardware revisions of Asus RT-AC88U, brcmfmac detects the
4366b1 wireless chip and tries to load the firmware file which doesn't
exist because it's not included in the image.
Therefore, include firmware for 4366b1 along with 4366c0. This way, all
hardware revisions of the router
14 matches
Mail list logo
