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 ---
Sorry, I did intend the email for
Signed-off-by: J. Scott Heppler
ramips: add support for TRENDnet TEW-810DR
Exact hardware clone for the D-Link DIR-810L. See OpenWRT device pages
and review the PCB photos, boot logs and MTP flash partitions.
https://openwrt.org/toh/trendnet/trendnet_tew-810dr_1.0_1.1
https://openwrt.org/toh/d
Signed-off-by: Tim Harvey
---
target/linux/octeontx/config-5.4 | 634 +
...nderx-use-proper-interface-type-for-RGMII.patch | 47 ++
...hunderx-workaround-BGX-TX-Underflow-issue.patch | 150 +
...03-can-mcp251x-convert-to-half-duplex-SPI.patch | 51 ++
.
On 26.02.20 17:17, Tim Harvey wrote:
On Wed, Feb 26, 2020 at 5:27 AM John Crispin wrote:
On 25.02.20 22:58, Tim Harvey wrote:
Hi Tim,
thanks for the patch, we are in the process of bumping to v5.4. Would
you have time to also try bumping octeontx to v5.4 ? staging tree is
located here ->
http
Am 25.02.2020 um 22:41 schrieb Rosen Penev:
> I don't see any of my init script changes breaking this.
>
> Does this work?
> --- a/net/stubby/files/stubby.init
> +++ b/net/stubby/files/stubby.init
> @@ -205,7 +205,7 @@ generate_config()
> }
>
> config_foreach handle_resolver resolver
>
Hi Tim,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Tim Harvey
> Sent: Mittwoch, 26. Februar 2020 17:18
> To: John Crispin
> Cc: OpenWrt Development List
> Subject: Re: [OpenWrt-Devel] [PATCH] octeontx: move to 4.19 kernel
>
On Wed, Feb 26, 2020 at 5:27 AM John Crispin wrote:
>
> On 25.02.20 22:58, Tim Harvey wrote:
>
> Hi Tim,
> thanks for the patch, we are in the process of bumping to v5.4. Would
> you have time to also try bumping octeontx to v5.4 ? staging tree is
> located here ->
> https://git.openwrt.org/?p=ope
>> A first step could be to establish a *versions.json* file at the root of
>> downloads.openwrt.org! The file would allow to check if a device still runs
>> the latest release. JSON seems common enough and is well supported by LuCIs
>> JavaScript implementation and also via jshn.sh on a CLI/scrip
On Wed, Feb 26, 2020 at 10:48 AM Paul Oranje wrote:
>
> Having read the whole conversation: an impressive piece of work.
>
> Could this helps with ipq806x ?
> On ipq806x qce isn't available on all SOCs (supposedly only on ipq8064) and
> therefore support has been removed from the kernel [1].
>
>
Hi,
> --- a/target/linux/ramips/base-files/lib/ramips.sh
> +++ b/target/linux/ramips/base-files/lib/ramips.sh
> @@ -478,6 +478,9 @@ ramips_board_detect() {
> *"TEW-714TRU")
> name="tew-714tru"
> ;;
> + *"TEW-810DR")
> +name="tew-810dr"
> +
Op 25 feb. 2020, om 14:02 heeft Eneas Queiroz het
volgende geschreven:
>
> Hi
>
> I have finished working on
> https://github.com/openwrt/openwrt/pull/2518, fixing some bugs with
> the crypto engine, and adding asm modules to crypto algorithms, since
> the engine is not very fast when using "ne
Paul Spooren [2020-02-23 00:04:59]:
[ adding openwrt-devel to the Cc: loop ]
Hi,
> A first step could be to establish a *versions.json* file at the root of
> downloads.openwrt.org! The file would allow to check if a device still runs
> the latest release. JSON seems common enough and is well su
On 25.02.20 22:58, Tim Harvey wrote:
Hi Tim,
thanks for the patch, we are in the process of bumping to v5.4. Would
you have time to also try bumping octeontx to v5.4 ? staging tree is
located here ->
https://git.openwrt.org/?p=openwrt/staging/xback.git;a=summary and we
plan to merge it to mas
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Russell Senior
> Sent: Mittwoch, 26. Februar 2020 11:20
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH RFC] ath79: add support for the ar7240 version
> of
The Ubiquiti Bullet M2HP come in two flavors, based on ar7240 and
ar7241. Both are supported by ar71xx, despite the different SoCs. The
ath79 target, however, currently supports only the ar7241. The ar7240
version apparently has a differently wired ethernet interface and the
ar7241-based image co
15 matches
Mail list logo