nux/lantiq/config-4.4
Additionally you should check the phy-mode:
You are setting phy-mode = "rgmii", but Atheros says that the AR8030
is an "Ultra low-power single RMII Fast Ethernet PHY".
Thus you should probably change "rgmii" to "rmii".
Martin
On Sun,
On Sun, May 15, 2016 at 9:45 PM, Sebastian Ortwein wrote:
> Am 15.05.2016 um 17:37 schrieb Martin Blumenstingl:
> Okay thank you for support. Now all thinks works fine LAN, WIFI, Switch and
> USB.
> I attach my patch to add the support for OpenWRT.
Great - congratulations :-)
> Is
On Wed, May 18, 2016 at 9:54 AM, Ben Mulvihill wrote:
> On Wed, 2016-05-18 at 09:39 +0200, Oswald Buddenhagen wrote:
>> - NAND/UBI support is completely irrelevant for my box, and for
>> lantiq/Danube in general (IIRC). It appears to me that it would make
>> sense to split it off from the xway
On Tue, Aug 2, 2016 at 6:10 PM, Alexander Couzens wrote:
> On Tue, 2 Aug 2016 13:38:55 +
> Daniel Niasoff wrote:
>
>> I can provide remote ssh access if required. When using SSH you will
>> notice it feels sluggish due to this issue.
>>
>> Any ideas plase, I am really stuck here?
>
> I ca
This adds the changes from r46219 to the linux 4.1 patches as well.
Signed-off-by: Martin Blumenstingl
---
It seems that I forgot to include these in the original patchset which
added the 4.1 patches for the lantiq target.
Thanks to Mathias Kresin for finding this.
.../lantiq/patches-4.1/0028
Whenever two processes were executing different commands at the same
time then one of the commands sometimes got the response of the other
command.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/base-files/lib/functions/lantiq_dsl.sh | 2 ++
1 file changed, 2 insertions(+)
diff
On Wed, Oct 14, 2015 at 12:19 PM, Afkar Rafique wrote:
> Could anyone please explain how i can configure and read GPIO value.
There's an article on the wiki which explains how to set a GPIO to a
specific value: [0]
If you want to read a GPIO value then you use direction "in" and then
simply cat to
Hi John,
I am getting SPI errors on latest trunk.
It seems that those might be related to your SPI changes from last week.
I found that someone else reported a similar issue a few years ago: [0].
That patch was never applied and I'm not sure if it's 100% correct.
These are the errors I get witho
This should help finding potential problems with the SPI driver.
Signed-off-by: Martin Blumenstingl
---
.../lantiq/patches-3.18/0033-SPI-MIPS-lantiq-adds-spi-xway.patch | 4 +++-
.../linux/lantiq/patches-4.1/0033-SPI-MIPS-lantiq-adds-spi-xway.patch | 4 +++-
2 files changed, 6 insertions
Until now the SPI driver used the TX bits for the RX FIFO. This seems
uncritical for now since both are equals on my devices (VR9), but this
could cause problems on other SoCs.
Signed-off-by: Martin Blumenstingl
---
.../linux/lantiq/patches-3.18/0033-SPI-MIPS-lantiq-adds-spi-xway.patch | 2
Hi John,
On Thu, Oct 15, 2015 at 7:59 AM, John Crispin wrote:
> bummer. i had hoped that my patch fixed the issue.
>
> did you try the patch graham posted ?
I split the patch into two and tried:
1) flushing in ltq_spi_wait_ready
2) reducing rxreq_max in ltq_spi_rxreq_set
3) both of the changes fr
This updates the relevant source files to util-linux changeset
4419ffb9eff5801fdbd385a4a6199b3877f802ad.
Signed-off-by: Martin Blumenstingl
---
libblkid-tiny/bitops.h| 166 ++
libblkid-tiny/blkdev.h| 47 +-
libblkid-tiny/blkid.h | 147
Hello,
this updates the libblkid code and additionally adds F2FS support.
The libblkid-tiny binary is now slightly smaller:
Before:
19268 libblkid-tiny.so
After:
18256 libblkid-tiny.so
mount output of a F2FS device:
# mount | grep f2fs
/dev/sda1 on /mnt type f2fs
(rw,relatime
Signed-off-by: Martin Blumenstingl
---
CMakeLists.txt| 1 +
libblkid-tiny/f2fs.c | 101 ++
libblkid-tiny/libblkid-tiny.c | 1 +
3 files changed, 103 insertions(+)
create mode 100644 libblkid-tiny/f2fs.c
diff --git a
On Thu, Oct 8, 2015 at 6:13 PM, Sandy McArthur Jr wrote:
> While attempting to pivot overlay using the f2fs filesystem in a 4mib
> internal flash storage device on usb flash storage with the final CC
> 15.05 release I ran into the hurdle that the block command doesn't
> understand the magic bytes
This fixes #20409
Signed-off-by: Martin Blumenstingl
---
.../0043-MIPS-add-board-support-for-Arcadyan-VGV7510KW22.patch | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
a/package/boot/uboot-lantiq/patches/0043-MIPS-add-board-support-for-Arcadyan-VGV7510KW22.patch
Signed-off-by: Martin Blumenstingl
---
Unfortunately I am not sure if and how px5g-standalone should be
adjusted, so this should be done by someone else if required.
package/utils/px5g/px5g.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/utils/px5g/px5g.c b/package
On Sun, Nov 1, 2015 at 9:01 AM, John Crispin wrote:
> I'll merge this as is, however i am starting to wonder if we should not
> just autodetect the right fw to use and only pass 11G/22F as an option
I am *guessing* that it's due to binary size reasons (including all
GPHY firmwares in the u-boot bi
The old version (5.3.4.A.1.6-5.3.6.4.1.2) is not supported by the new
DSL driver. The new version (5.6.8.4.1.7-5.6.7.2.1.2) also brings
(theoretically) vectoring support.
Signed-off-by: Martin Blumenstingl
---
package/kernel/lantiq/ltq-vdsl-fw/src/vdsl_fw_install.sh | 8
package/kernel
Hi Felix,
On Sun, Nov 8, 2015 at 1:29 PM, Felix Fietkau wrote:
> Did you test this on a real VDSL line? Last time I tried a firmware from
> a newer Speedport build (some months ago), it did not work.
I thought it works as I've seen it entering SHOWTIME.
Unfortunately you are right, after a few se
This is a minor version update which fixes some small bugs. None of
these bugs were exploitable according to the release notes.
Signed-off-by: Martin Blumenstingl
---
package/libs/polarssl/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libs/polarssl
Signed-off-by: Martin Blumenstingl
---
Working fine for me after a short test on a QCA9880-BR4A.
package/firmware/ath10k-firmware/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/firmware/ath10k-firmware/Makefile
b/package/firmware/ath10k-firmware
Signed-off-by: Martin Blumenstingl
---
I couldn't test this change since I don't have a device that uses this.
target/linux/ar71xx/base-files/lib/preinit/82_patch_ath10k | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ar71xx/base-files/l
On Sun, Nov 29, 2015 at 7:25 PM, Andre Heider wrote:
> --- a/target/linux/lantiq/xrx200/target.mk
> +++ b/target/linux/lantiq/xrx200/target.mk
> @@ -7,7 +7,6 @@ CPU_SUBTYPE:=dsp
>
> DEFAULT_PACKAGES+=kmod-leds-gpio \
> kmod-gpio-button-hotplug \
> - ltq-vdsl-vr9-fw-installer \
>
On Thu, Dec 3, 2015 at 3:00 PM, Felix Fietkau wrote:
> Maybe it's worth testing the latest from here (seems to be newer):
> https://www.codeaurora.org/cgit/quic/qsdk/oss/firmware/ath10k-firmware/tree/10.2.4
I have just updated one of my devices to 10.2.4.97. I'll let it run
for a few days and send
On Sat, Dec 12, 2015 at 3:19 PM, John Crispin wrote:
> ok, let me know how it went, if you dont mind i'll close the 2 pending
> patches for now. if we merge we will most likely want the newest FW.
sure, feel free.
___
openwrt-devel mailing list
openwrt-d
Signed-off-by: Martin Blumenstingl
---
v2: Updated because patch #1 out of this series now uses 10.2.4.97-1
target/linux/ar71xx/base-files/lib/preinit/82_patch_ath10k | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ar71xx/base-files/lib/preinit/82_patch_ath10k
Signed-off-by: Martin Blumenstingl
---
package/firmware/ath10k-firmware/Makefile | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/package/firmware/ath10k-firmware/Makefile
b/package/firmware/ath10k-firmware/Makefile
index 596cf1f..882294c 100644
--- a/package
On Sat, Dec 12, 2015 at 3:19 PM, John Crispin wrote:
> if we merge we will most likely want the newest FW.
I have now tested 10.2.4.97 for a week and no crashes so far.
Thus I just sent an updated patchset.
___
openwrt-devel mailing list
openwrt-devel@li
linux 4.4 (since commit 08b3c894e56580b8ed3e601212a25bda974c3cc2
"MIPS: lantiq: Disable xbar fpi burst mode") requires that the xbar is
defined in the .dts of vrx200 (VR9) SoCs.
---
I am not sure if the xbar size is really 0x1000 or if it's smaller/larger.
Unfortunately there doesn't seem to be pub
gpio.h needs the linux/ prefix with linux 4.4.
---
package/kernel/lantiq/ltq-vmmc/patches/100-target.patch | 8
package/kernel/lantiq/ltq-vmmc/patches/400-falcon.patch | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/package/kernel/lantiq/ltq-vmmc/patches/100-target.
Upstream linux 4.2 commit 84be456f883c4685680fba8e5154b5f72e92957e
"remove " moves scatterlist.h to linux/ instead of asm/.
Upstream linux 4.3 commit b0d955ba4688fcba8112884931aea1f1e6f50f03
"crypto: aead - Remove old AEAD interfaces" removed aead_request_set_assoc.
aead_request_set_ad should be u
This removes one patch which was applied upstream with commit
67b9bcd36906e12a15ffec19463afbbd6a41660e. All other patches were
refreshed.
Signed-off-by: Martin Blumenstingl
---
include/kernel-version.mk | 4 +--
...spi-nor-disable-protection-for-Winbond-fl.patch | 35
According to the datasheet says that the xbar register range is
0x1F40-0x1F400FFF. Thanks to John Crispin for looking it up.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/vr9.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/lantiq/dts
On Mon, Jan 11, 2016 at 2:59 PM, John Crispin wrote:
> 0x1F40-0x1F400FFF means that its size is 0x1000. i think you having
> a off-by-one thinko ...
...and I think you are right!
Sorry for the noise, please drop this patch.
___
openwrt-devel mailing
Hello,
this series adds linux 4.4 support to the lantiq target.
It depends on the linux/generic 4.4.0 update because -rc8 contains a
build-fix for MIPS devices.
I have tested it on two (VRX200) devices:
- VGV7510KW22 (seems to work fine)
- TD-W8970 (the mtd_reads in mtd_split seem to only return
Remove the "DEU test manager" code which has not been used for more than
two years (as the kernel module is not installed anymore since
aa65888e08ec7279cfecc24c5bfe71cf9a016b91).
This fixes compilation on kernel 4.3 (which removes
aead_request_set_assoc) and newer.
Signed-off-
Upstream linux 4.2 commit 84be456f883c4685680fba8e5154b5f72e92957e
"remove " requires us to include linux/scatterlist.h
instead. This also works with older kernels (at least 4.1, thanks to
Hauke Mehrtens for testing).
Signed-off-by: Martin Blumenstingl
---
package/kernel/lantiq/l
Hi John,
On Mon, Jan 11, 2016 at 3:25 PM, Martin Blumenstingl
wrote:
> Here's the kernel log from the TD-W8970: https://paste.kde.org/pia7p73i9
> I have debugged it and split_tplink_kernel gets 0x2 as offset and
> 0x7A as size (which looks correct). However, when mtd_read t
ch with ath10k.
>> I recommend to only use firmware releases from ath10k-firmware.git as we
>> use those internally with ath10k. In any case, don't make any
>> assumptions about future from that firmware branch as it's so old.
Thanks for clarifying this.
> Thi
On Fri, Jan 13, 2017 at 6:30 PM, Mauro M. wrote:
> Hello,
>
> Is OpenWRT going to backport support for BtHomeHub5 from LEDE?
> This router is very well supported in LEDE, whilst support is only basic in
> OpenWrt,
> LEDE implemented some broken changes in the firewall that prevent basic
> routing
On Thu, Jan 12, 2017 at 3:35 PM, Daniel Golle wrote:
> Hi!
>
> The amount of patches on top of rt2x00 has grown into a huge pile
> during the past couple of years. To get things into a shape that allow
> discussing and merging them upstream, I created a tree on github based
> on wireless-drivers-n
On Sat, Jan 14, 2017 at 3:44 AM, Daniel Golle wrote:
> Hi Martin,
>
> On Sat, Jan 14, 2017 at 01:28:06AM +0100, Martin Blumenstingl wrote:
>> On Thu, Jan 12, 2017 at 3:35 PM, Daniel Golle wrote:
>> > Hi!
>> >
>> > The amount of patches on top of rt2x00
Hello,
I recently purchased a TP-Link TD-W8970 on which I have installed OpenWrt.
My goal is to use it as my main "DSL router", so it has to connect to
the internet.
For the reference: at the moment I'm using a "AVM FritzBox" for this
purpose, which is connected directly to the phone jack (the web
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 everyone,
you are included
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 ---
Hi Hauke,
On Mon, Apr 12, 2021 at
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 ---
Hi Martin,
On Mon, Apr 12, 2021 a
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 ---
Hi Enrico,
On Mon, Jul 29, 2019 a
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 Sun, Aug 11, 2019 at 1:00 PM Bi
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 ---
Hi Michal,
On Wed, Aug 14, 2019 a
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 ---
Hi Enrico,
On Sat, Aug 24, 2019 a
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 ---
Hi,
On Fri, Aug 17, 2018 at 12:05
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 Thu, Aug 16, 2018 at 5:06 AM Ch
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, Aug 22, 2018 at 6:58 PM Dm
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 ---
Hi Lorenzo,
thank you for your wo
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 ---
Hi,
(disclaimer: my knowledge abo
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 Jaap,
On Thu, May 24, 2018
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 Sat, Jun 9, 2018 at 4:15 PM Tom
t 11:09 PM Tomasz Maciej Nowak wrote:
>
> W dniu 09.06.2018 o 19:02, Martin Blumenstingl pisze:
> > On Sat, Jun 9, 2018 at 4:15 PM Tomasz Maciej Nowak wrote:
> >>
> >> Since the beginning there's been an issue with initializing the Atheros
> >> based
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 Thu, Jul 19, 2018 at 7:12 PM Th
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 Thu, Jul 19, 2018 at 7:13 PM Th
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 ---
Hi Enrico,
On Wed, Sep 4, 2019 at
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 ---
Hi Martin,
On Mon, Sep 16, 2019 a
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 ---
Hi Paul,
On Sun, Jan 12, 2020 at
3, 2020 at 9:13 AM Paul Spooren wrote:
>
> Hi,
>
> On 1/12/20 1:05 PM, Martin Blumenstingl wrote:
> > Hi Paul,
> >
> > On Sun, Jan 12, 2020 at 10:47 PM Paul Spooren wrote:
> >> Hi all,
> >>
> >> some time ago I created a (now outdated) d
un, Apr 11, 2021 at 7:51 PM Martin Blumenstingl
wrote:
[...]
> To improve the situation I suggest using Rafał Miłecki's approach also
> for the lantiq target:
> He is submitting patches upstream, then backporting them to OpenWrt.
> That way backports to the -stable tree are for free.
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 Sat, Jun 12, 2021 at 2:15 PM Bj
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 ---
Hi Lukas,
On Sat, Jun 12, 2021 at
a8 ("base-files: use "ports" array in board.json network for
> bridges")
> Signed-off-by: Hauke Mehrtens
Tested-by: Martin Blumenstingl #
BT Home Hub 5A with DSA patches
--- End Message ---
___
openwrt-devel mailing list
op
; before bringing up the actual interface.
>
> This is needed to make network in failsafe on systems with DSA work.
>
> Signed-off-by: Hauke Mehrtens
if you're keeping this patch instead of going with the backport you can add my:
Tested-by: Martin Blumen
terface.
>
> Just mark the Lantiq DEU as broken for now.
>
> Fixes: FS#3901
> Fixes: 53b6783907f3 ("mac80211: remove patches stripping down crypto support")
> Signed-off-by: Hauke Mehrtens
I am testing wifi with Linux 5.10 only these days where ltq-deu is
disabled any
n 27, 2021 at 8:57 PM Hauke Mehrtens wrote:
>
> On 6/27/21 9:38 AM, Martin Blumenstingl wrote:
> > Hi Hauke,
> >
> > On Sun, Jun 27, 2021 at 12:55 AM Hauke Mehrtens wrote:
> >>
> >> When the ltq_deu_vr9 kernel module is loaded, hostapd does not start any
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 ---
Hi Martin,
On Thu, Jul 1, 2021 at
et the CPU".
Add an info message if the watchdog supports the WDIOF_CARDRESET flag
and if the boot status indicates that the watchdog has previously reset
the system.
Signed-off-by: Martin Blumenstingl
---
watchdog.c | 31 +++
1 file changed, 31 insertions(+)
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 ---
Hi Andre,
On Sat, Sep 25, 2021 at
at 6:53 PM Martin Blumenstingl
wrote:
>
> Hi Andre,
>
> On Sat, Sep 25, 2021 at 1:17 PM Andre Heider wrote:
> [...]
> > With these 3 reverted (on top of da5bb885 "toolchain/gcc: switch to
> > version 11 by default") it works again:
> > Revert "h
gic which would adds the affected band and
typo: s/adds/add/
> channels. It now disables all channels which are not
> within the specified frequency range.
>
> Signed-off-by: Christian Lamparter
apart from above typo this is:
Reviewed-by: Martin Blumenstingl
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 ---
Hi Ansuel,
below are a few commen
sted these patches for a few days and they don't break my
HH5A so this gets my:
Tested-by: Martin Blumenstingl
Best regards,
Martin
--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
to the vectoring callback.
>
> Make these dependencies conditional on the specific package variants,
> so they are only built when actually needed.
>
> Signed-off-by: Jan Hoffmann
Tested-by: Martin Blumenstingl
This fixes a build issue on my local system when building the xway
subtar
device shows that the reported line uptime now matches
> the actual elapsed wall time. The ADSL variant is only compile-tested,
> but it should also work as the relevant code is identical.
>
> Signed-off-by: Jan Hoffmann
Tested-by: Martin Blumenstingl
statistics seem fine to me with th
ing the acos and acs commands via
> dsl_cpe_pipe.sh in the init script. However, doing it in the daemon
> itself has the advantage of also working if it is terminated in another
> way (for example during sysupgrade).
>
> Signed-off-by: Jan Hoffmann
sysupgrade with this patch in my tree d
gt; Signed-off-by: Andre Heider
Thanks for the patch! I got a cheap 7520 and flashed OpenWrt on it
using this patch. Everything works fine as far as I can tell, so:
Tested-by: Martin Blumenstingl
Best regards,
Martin
--- End Message ---
___
openwrt-dev
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, 2022
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 ---
Hi Adrian,
On Sat, Feb 1, 2020 at
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 ---
Hi Roger,
On Sun, Feb 2, 2020 at
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 ---
Hi Adrian,
On Sun, Feb 23, 2020 a
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 ---
Hi,
On Fri, Apr 10, 2020 at 11:47
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 ---
Hi Andreas,
On Sat, Mar 28, 2020
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 ---
Hi Adrian,
(sorry for being sligh
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 ---
Hi,
On Wed, Apr 22, 2020 at 1:21
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 ---
Hi Daniel,
On Mon, Jun 15, 2020 a
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 ---
Hi Adrian,
On Thu, Jun 18, 2020 a
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 ---
Hi John,
On Tue, Jun 23, 2020 at
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 ---
Hi Luca,
On Sun, Jul 5, 2020 at 1
5, 2020 at 1:42 PM Luca Olivetti wrote:
>
> El 5/7/20 a les 13:29, Martin Blumenstingl ha escrit:
> > Hi Luca,
> >
> > On Sun, Jul 5, 2020 at 1:07 PM Luca Olivetti wrote:
> > [...]
> >> I put a printk in every step of reg_fixed_regulator_probe
> >> (
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 ---
Hi Luca,
On Sun, Jul 5, 2020 at 3
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 ---
Hi Adrian,
On Sat, Sep 26, 2020 a
p 30, 2020 at 9:11 PM Adrian Schmutzler
wrote:
>
> Hi Martin,
>
> > -Original Message-
> > From: Martin Blumenstingl [mailto:martin.blumensti...@googlemail.com]
> > Sent: Mittwoch, 30. September 2020 20:55
> > To: Adrian Schmutzler
> > Cc: openwrt-de
101 - 199 of 199 matches
Mail list logo
