Hi,
> -Original Message-
> From: Stefan Lippers-Hollmann [mailto:s@gmx.de]
> Sent: Freitag, 28. Februar 2020 22:21
> To: John Crispin
> Cc: Adrian Schmutzler ; OpenWrt Development List
> ; Chuanhong Guo ;
> Koen Vandeputte
> Subject: Re: [OpenWrt-Devel] RFT
Hi,
> -Original Message-
> From: Russell Senior [mailto:russ...@personaltelco.net]
> Sent: Samstag, 29. Februar 2020 14:10
> To: openwrt-devel@lists.openwrt.org
> Cc: Adrian Schmutzler
> Subject: Re: [OpenWrt-Devel] [PATCH RFC v3] ath79: add support for th
Ah, and please use git format-patch, your v2/v3 didn't even make it into
patchwork.
> -Original Message-
> From: Russell Senior [mailto:russ...@personaltelco.net]
> Sent: Samstag, 29. Februar 2020 14:10
> To: openwrt-devel@lists.openwrt.org
> Cc: Adrian Schmutzler
> Sub
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Heppler, J. Scott
> Sent: Samstag, 7. März 2020 22:24
> To: openwrt-de...@openwrt.org
> Subject: [OpenWrt-Devel] ramips: adding support for TRENDnet DIR-810DR
>
> I'm looking
Hi David,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of David Bauer
> Sent: Montag, 9. März 2020 02:07
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH] ramips: add support for Ubiquiti UniFi
> nanoHD
>
>
Hi,
> I noticed, however, that the green "Internet" LED blinks to the LAN4 port,
> while -I guess- it should blink to the INTERNET (wan/eth0.2) port.
> But this was already happening before, it's not related to your patch.
green internet LED is not present in the DTS (only orange WAN LED), and
Of Roger Pueyo Centelles | Guifi.net via openwrt-devel
> Sent: Montag, 2. März 2020 15:59
> To: Adrian Schmutzler ; openwrt-
> de...@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 2/2] ramips: fix and tidy up DTS for
D-
> Link DIR-810L
>
> The sender domain has a
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Yousong Zhou
> Sent: Donnerstag, 5. März 2020 12:57
> To: Petr Štetiar
> Cc: OpenWrt Development List
> Subject: Re: [OpenWrt-Devel] [PATCH] malta: fix missing watchdog
>
Hi,
> -Original Message-
> From: Roger Pueyo Centelles | Guifi.net [mailto:roger.pu...@guifi.net]
> Sent: Montag, 2. März 2020 15:59
> To: Adrian Schmutzler ; openwrt-
> de...@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 2/2] ramips: fix and tidy up DTS for
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Tim Harvey
> Sent: Montag, 2. März 2020 18:02
> To: Petr Štetiar ; Adrian Schmutzler
> ; openwrt-devel@lists.openwrt.org
> Cc: Tim Harvey
> Subject: [Ope
Hi,
> --- a/target/linux/imx6/base-files/etc/board.d/02_network
> +++ b/target/linux/imx6/base-files/etc/board.d/02_network
> @@ -13,7 +13,11 @@ case "$board" in
> cubox-i |\
> *gw51xx |\
> *gw52xx |\
> -*gw5904)
> +*gw5904 |\
> +*gw5907 |\
> +*gw5910 |\
> +*gw5912 |\
> +*gw5913)
Is there any
From: Pawel Dembicki
Signed-off-by: Pawel Dembicki
---
Since I've mostly done cosmetic changes on this target,
I'd be happy about an Acked-by so I can push this bump.
The patch for adding 4.19 support on this target is actually
from 2018.
Adrian
---
target/linux/kirkwood/Makefile | 3 +--
1
sed, minor commit message/title adjustments]
Signed-off-by: Adrian Schmutzler
---
.../arm/boot/dts/kirkwood-linksys-audi.dts| 23 ++
.../kirkwood/patches-4.19/105-ea4500.patch| 31 ---
2 files changed, 22 insertions(+), 32 deletions(-)
diff --git
a/target/linux/kirk
EW-810DR
> support
>
> On Feb 27, 2020: 13:37, Adrian Schmutzler wrote:
> >Hi,
> >
> >> -Original Message-
> >> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> >> Behalf Of Heppler, J. Scott
> >> Sent: Donners
amips: add support for dir810l and asus rp-n53")
Signed-off-by: Adrian Schmutzler
---
target/linux/ramips/dts/mt7620a_dlink_dir-810l.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ramips/dts/mt7620a_dlink_dir-810l.dts
b/target/linux/ramips/dts/mt7620a
This patch addresses several issues for D-Link DIR-810L:
- add correct button codes
- harmonize button node names
- use generic flash@0
- remove unused pin groups from state_default
- improve sorting of properties
The patch is only build-tested.
Signed-off-by: Adrian Schmutzler
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Heppler, J. Scott
> Sent: Donnerstag, 27. Februar 2020 03:39
> To: openwrt-de...@openwrt.org
> Subject: [OpenWrt-Devel] [PATCH v2] ramips: add TRENDnet TEW-810DR support
>
>
> > What's the base for the v0/v1 distinction? Is that visible to the user
> > somehow?
> > I fear that meaningful naming will be the biggest problem here...
>
> v0 and v1 mostly come from the need to distinguish between them. You could
> think of the digit as the least significant digit of the
> -Original Message-
> From: Raylynn Knight [mailto:raykni...@me.com]
> Sent: Donnerstag, 27. Februar 2020 06:16
> To: Adrian Schmutzler
> Cc: openWrt Development List
> Subject: Re: [OpenWrt-Devel] [PATCH] kirkwood: convert DTS patches into plain
> DTS files
>
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
>
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"
> +
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
>
Hi,
> -Original Message-
> From: man...@gorani.run [mailto:man...@gorani.run]
> Sent: Samstag, 22. Februar 2020 16:29
> To: m...@adrianschmutzler.de; openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] Some questions - help needed
>
> On 20. 2. 22. 9:48 PM,
Hi,
when looking for PKG_VERSION, I've stumbled across the following:
PKG_VERSION:=$(PKG_VERSION)
https://github.com/openwrt/openwrt/blob/master/package/devel/binutils/Makefile#L
16
Is there any reason to have that I don't see, or can this just be removed?
Best
Adrian
Hi Daniel,
> -Original Message-
> From: Daniel Golle [mailto:dan...@makrotopia.org]
> Sent: Montag, 24. Februar 2020 17:43
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org; Hans Dedecker ;
> Jo-Philipp Wich ; Andre Valentin ; Daniel
> Golle ; John Crispi
the
resulting package version string is bigger than before.
Cc: Hans Dedecker
Cc: Felix Fietkau
Cc: Andre Valentin
Cc: Matthias Schiffer
Cc: Jo-Philipp Wich
Cc: Steven Barth
Cc: Daniel Golle
Cc: John Crispin
Signed-off-by: Adrian Schmutzler
---
package/kernel/om-watchdog/Makefile
penWrt buildroot anyway.
I personally see it the same way, though I'm aware this in handled differently
for different targets.
This change will just remove one layer of complexity.
Acked-by: Adrian Schmutzler
Best
Adrian
___
openwrt-devel mailing
> -Original Message-
> From: Piotr Dymacz [mailto:pep...@gmail.com]
> Sent: Donnerstag, 20. Februar 2020 18:58
> To: Adrian Schmutzler ; openwrt-
> de...@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 2/2] rssileds: restrict package to targets
> where it i
pendencies are provided when building for the
relevant targets ar71xx, ath79 and ramips, it seems more tidy to
specify them explicitly.
Signed-off-by: Adrian Schmutzler
---
package/network/utils/rssileds/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/network/util
It does not seem very sensible to provide the rssileds package
on targets without corresponding LEDs, so restrict it to the
targets where it is used at the moment.
Signed-off-by: Adrian Schmutzler
---
package/network/utils/rssileds/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Christopher Hill
> Sent: Montag, 17. Februar 2020 16:03
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] Mikrotik ar71xx -> ath79 port
>
> Hi,
>
> New here, and am
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Christopher Hill
> Sent: Montag, 17. Februar 2020 16:03
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] Mikrotik ar71xx -> ath79 port
>
> Hi,
>
> New here, and am
0 0x9f02 0x3c
> bootm 0x9f02
- flash factory image from OEM WebUI
- sysupgrade from ar71xx image
Signed-off-by: Adrian Schmutzler
---
.../ath79/dts/ar7240_tplink_tl-wa701nd-v1.dts | 9 +
.../ath79/dts/ar7240_tplink_tl-wa730re-v1.dts | 9 +
.../ath79/dts/ar7240_t
Hi,
since 19.07 release we have changed device/image names in several targets to
make naming schemes in OpenWrt more systematic and harmonize them between
targets.
Today, I have also renamed most of the brcm target for a similar reason.
To aid downstream and other developers to keep
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Alexander 'lynxis' Couzens
> Sent: Mittwoch, 12. Februar 2020 13:02
> To: dw...@infradead.org
> Cc: OpenWrt Development List
> Subject: [OpenWrt-Devel] jffs2 runs into read-only on
Hi,
some nitpicks below.
> -Original Message-
> From: Daniel Golle [mailto:dan...@makrotopia.org]
> Sent: Dienstag, 11. Februar 2020 19:35
> To: openwrt-devel@lists.openwrt.org
> Cc: Chuanhong Guo ; Adrian Schmutzler
> ; Piotr Dymacz
> Subject: [PATCH v4 2/
Fernández Rojas [mailto:nolt...@gmail.com]
Sent: Montag, 10. Februar 2020 18:03
To: Adrian Schmutzler ;
openwrt-devel@lists.openwrt.org
Subject: Re: [PATCH] brcm2708: rename target to bcm27xx
Hi Adrian,
You can rename them to bcm27xx, since those packages also refer to BCM2709,
BCM2710
r 2020 13:00
> To: Adrian Schmutzler ;
openwrt-devel@lists.openwrt.org
> Subject: Re: [PATCH] brcm2708: rename target to bcm27xx
>
> Hi Adrian,
>
> Thanks for taking care of this.
>
> Acked-by: Álvaro Fernández Rojas
___
open
31_tpl
ink_tl-mr3020-v1.dts#L123
So, can somebody lend me some expertise whether the value is okay?
Best
Adrian Schmutzler
[1] https://github.com/openwrt/openwrt/pull/2752#discussion_r375829096
___
openwrt-devel mailing list
openwrt-devel@lists.openw
to node and remove the
redundant status=okay there.
This should allow to enable USB power on these devices.
Fixes: FS#2753
Signed-off-by: Adrian Schmutzler
---
target/linux/ath79/dts/ar9341_tplink.dtsi | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/target
-by: Adrian Schmutzler
---
package/base-files/files/etc/init.d/boot | 2 +-
package/kernel/broadcom-wl/Makefile | 4 +--
package/kernel/linux/modules/netdevices.mk| 4 +--
package/kernel/linux/modules/other.mk | 4 +--
package/kernel/linux/modules/usb.mk | 12
Hi,
currently we have several Broadcom based targets named after that:
- bcm53xx
- brcm47xx
- brcm63xx
- brcm2708
As you can see, the names are inconsistent with respect to bcm vs. brcm.
While kernel has codified "brcm" for the vendor name in compatible [1], the
target names are about the
to node and remove the
redundant status=okay there.
This should allow to enable USB power on these devices.
Fixes: FS#2753
Signed-off-by: Adrian Schmutzler
---
This has been created based on a bug report:
https://bugs.openwrt.org/index.php?do=details_id=2753
There has been no feedback, so I
Hi,
we currently have a PR [1] where somebody wants to set SMALL_FLASH for mt7620 in
ramips target due to kernel size restriction for that particular device.
I'm actually not too fond of doing that to all the other devices because of one
single device needing it.
However, I wonder whether we
Hi,
> > > +
> > > + led_system_green: system_green {
> > > + label = "rut955:green:system";
> > > + gpios = <_ext 6 GPIO_ACTIVE_HIGH>;
> > > + default-state = "on";
> > > + linux,default-trigger = "phy0tpt";
> >
> > tpt
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Daniel Golle
> Sent: Mittwoch, 5. Februar 2020 16:19
> To: openwrt-devel@lists.openwrt.org
> Cc: Gerhard Bertelsmann ; Adrian Schmutzler
> ; Piotr Dymacz
Hi,
> + leds {
> + compatible = "gpio-leds";
> +
> + signal0 {
> + label = "rut955:green:signal1";
Still signalX not matching here.
> + gpios = <_ext 0 GPIO_ACTIVE_HIGH>;
> + };
[...]
> +
> +
> -Original Message-
> From: Alin Năstac [mailto:alin.nas...@gmail.com]
> Sent: Mittwoch, 5. Februar 2020 14:43
> To: Adrian Schmutzler
> Cc: openwrt-devel
> Subject: Re: [OpenWrt-Devel] [netifd][PATCH] interface-ip: transfer prefix
> route
> ownership to
Hi,
please use a "v2" next time.
Best
Adrian
> -Original Message-
> From: Alin Năstac [mailto:alin.nas...@gmail.com]
> Sent: Mittwoch, 5. Februar 2020 14:38
> To: Adrian Schmutzler
> Cc: Hans Dedecker ; openwrt-devel de...@lists.openwrt.org>
> Subje
Hi,
works for me as well.
However, I'd prefer a shorter commit title, e.g.
interface-ip: transfer prefix route ownership for deprecated ipv6addr to kernel
Best
Adrian
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Alin
moved there (unless vendor also used
multiple purpose LEDs the same way).
But since we have these case in our code right now, I think this workaround is
necessary ATM.
Acked-by: Adrian Schmutzler
Best
Adrian
>
> Signed-off-by: Piotr Dymacz
> ---
> package/base-files/Makef
> -Original Message-
> From: Michal Cieslakiewicz [mailto:michal.cieslakiew...@wp.pl]
> Sent: Montag, 3. Februar 2020 18:04
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH v2 2/2] ath79: uboot-envtools: add
&g
, 20. Januar 2020 21:20
> To: openwrt-devel@lists.openwrt.org
> Cc: Adrian Schmutzler
> Subject: [OpenWrt-Devel] [PATCH v2 2/2] ath79: uboot-envtools: add Netgear
> WNDR3700v2
>
> Add Netgear WNDR3700v2 to the list of supported boards.
>
> Signed-off-by: Michal Ciesla
This introduces a variable KERNEL_DTB_LZMA to replace the frequently
used sequence "kernel-bin | append-dtb | lzma", similar to the
same variable in ramips target.
Signed-off-by: Adrian Schmutzler
---
target/linux/ath79/image/Makefile | 5 +++--
target/linux/ath79/im
To make it more obvious what it does, this renames the variable
for the sequence "kernel-bin | append-dtb | lzma" to KERNEL_DTB_LZMA.
Signed-off-by: Adrian Schmutzler
---
target/linux/ramips/image/Makefile | 4 ++--
target/linux/ramips/image/common-tp-link.mk | 10 +---
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Paul Oranje
> Sent: Sonntag, 2. Februar 2020 23:26
> To:
> Cc: openwrt-devel@lists.openwrt.org; Piotr Dymacz
> Subject: Re: [OpenWrt-Devel] [PATCH] ath79: introduces KERNEL_LZMA
This introduce a variable KERNEL_LZMA to replace the frequently
used sequence "kernel-bin | append-dtb | lzma", similar to the
KERNEL_DTB variable in ramips target.
Signed-off-by: Adrian Schmutzler
---
target/linux/ath79/image/Makefile | 5 +++--
target/linux/ath79/im
> Ok, will send this as part of v2.
I will mark 3/8 as rejected.
I'd merge 1, 2 and 4 tomorrow or on Sunday, so if you want to wait for
additional input on 5-8 you can also only send the former as smaller v2
patchset.
Best
Adrian
>
> Regards
>
> >
> >>
> >>> DEVICE_DTS_DIR and DTS_DIR
Hi,
> -Original Message-
> From: Tomasz Maciej Nowak [mailto:tome...@o2.pl]
> Sent: Freitag, 31. Januar 2020 19:39
> To: Adrian Schmutzler ; openwrt-
> de...@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 4/8] mvebu: image: keep global DTS_DIR
> intact
>
> When variables are _not_ set, but are added to DEVICE_VARS, the variables will
> have the last value set to any device before (i.e. the last device setting
it). Note
> that Device/Default counts like an include to the current device there.
Still not precise enough here:
When variables are
Hi,
> I saw similar behavior when variables were set but not added to DEVICE_VARS.
> From the tests I've done before sending, the produced images looked fine, but
> I'll re-test that to make sure.
When variables are set, but are _not_ added to DEVICE_VARS, the variables will
have _one_ single
Hi,
during support of the Ubiquiti Nanostation Loco XW, we encountered the following
blocks in ar71xx which are only present for devices not migrated to ath79 yet:
static struct mdio_board_info ubnt_loco_m_xw_mdio_info[] = {
{
[...]
.platform_data =
ces alphabetically
>
> Signed-off-by: Tomasz Maciej Nowak
Acked-by: Adrian Schmutzler
Haven't checked whether it's correct of course.
> ---
> target/linux/mvebu/image/cortex-a72.mk | 30 ++--
> target/linux/mvebu/image/cortex-a9.mk | 198 -
> 2 f
s makefile
> names
>
> Align subtargets makefiles names to actual subtargets.
>
> Signed-off-by: Tomasz Maciej Nowak
Acked-by: Adrian Schmutzler
> ---
> target/linux/mvebu/image/Makefile| 6 +++---
> target/linux/mvebu/image/{cortex-a53.mk
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Tomasz Maciej Nowak
> Sent: Freitag, 31. Januar 2020 16:46
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH 4/8] mvebu: image: keep global DTS_DIR intact
>
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Tomasz Maciej Nowak
> Sent: Freitag, 31. Januar 2020 16:46
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH 3/8] mvebu: image: drop empty variables from
>
: 050da2107a7e ("mediatek: backport upstream mediatek patches")
Signed-off-by: Adrian Schmutzler
Acked-by: John Crispin
---
As discussed with John, this is a replacement for the patch
[OpenWrt-Devel,RFC,RFT,2/2] mediatek: mt7623: add back images for
mt7623a-rfb-emmc
Just sendi
for previously
independent definitions where appropriate.
Signed-off-by: Adrian Schmutzler
---
I'd be happy about some Tested-by!
Changes in v2:
- Rebased due to removed DEVICE_PACKAGES for Archer C20i
---
target/linux/ramips/image/common-tp-link.mk | 39 +++
target/linux/ramips/image/mt7620.mk
for previously
independent definitions where appropriate.
Signed-off-by: Adrian Schmutzler
---
I'd be happy about some Tested-by!
---
target/linux/ramips/image/common-tp-link.mk | 39 +++
target/linux/ramips/image/mt7620.mk | 46 +++--
target/linux/ramips/image/mt7621.mk
Hi,
> (I should first say that I don't know enough about the ar71xx-ath79 migration
> to know if this idea will work, but I don't recall seeing it mentioned
> before.)
>
> What if we add a migration package for 18.06 that ar71xx users can opt-in and
> install, which (when the user initiates
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of David Bauer
> Sent: Dienstag, 28. Januar 2020 21:05
> To: drvl...@gmail.com; achte...@googlemail.com; openwrt-devel de...@lists.openwrt.org>
> Subject: [OpenWrt-Devel] Netgear
Hi David,
On 1/28/20 5:34 PM, Adrian Schmutzler wrote:
>> The GL.iNet microuter-N300 (internally referred as MT300N-v4) is a
>> pocket-size travel router. It is essentially identical to the VIXMINI
>> (internally referred as MT300N-v3) but with double the RAM and
>
Hi David,
some nitpick comments below.
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of David Bauer
> Sent: Sonntag, 26. Januar 2020 23:26
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH] ramips: add
Hi,
> There is easy way to check GMACx <> ethX assignment order in mach-*.c
> files. Just check order of ath79_register_eth() calls:
>
> ath79_register_eth(0);
> ath79_register_eth(1);
>
> Will register GMAC0 as eth0, GMAC1 as eth1
>
> ath79_register_eth(1);
> ath79_register_eth(0);
>
> Will
Hi Piotr,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Piotr Dymacz
> Sent: Montag, 27. Januar 2020 21:45
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org; gch981...@gmail.com;
> ansuels...@gm
Just a quick one:
> > So, no matter what we do, there is no easy way forward.
>
> We could remove all ar71xx -> ath79 migration helper scripts, ar71xx
> board names from supported devices lists in ath79 images and make the
> target a brand new, without any concerns about soon-to-be obsolete
There are several cases where phy-mode and status properties are
set again in DTS(I) files although those were set to the same values
in parent DTSI files already. Remove those cases (and thus also stop
their proliferation by copy/paste).
Signed-off-by: Adrian Schmutzler
---
target/linux/ath79
-by: Adrian Schmutzler
---
target/linux/ath79/dts/ar9132_tplink_tl-wa901nd-v2.dts | 4 ++--
target/linux/ath79/dts/ar9342_ubnt_nanostation-m-xw.dts | 4 ++--
target/linux/ath79/dts/qca9558_tplink_re350k-v1.dts | 7 ---
target/linux/ath79/dts/qca9558_tplink_rex5x.dtsi| 9 ++---
target
by converting all LINUX_4_19 symbols
to their inverted LINUX_4_14 equivalents.
Signed-off-by: Adrian Schmutzler
---
package/kernel/i2c-gpio-custom/Makefile| 2 +-
package/kernel/linux/modules/iio.mk| 2 +-
package/kernel/linux/modules/netdevices.mk | 2 +-
package/kernel/linux/modules
in image/Makefile, so the values are set directly in
image/lzma-loader/Makefile and the overwrite in image/Makefile is
removed.
Signed-off-by: Adrian Schmutzler
---
target/linux/ath79/image/Makefile | 1 -
target/linux/ath79/image/lzma-loader/Makefile | 4 ++--
2 files changed, 2
-by: Adrian Schmutzler
---
I plan to take care of other targets, too, and maybe provide a generic
loader-common, but for now this is limited to ath79 so we can support
the mikrotik devices there.
---
target/linux/ath79/image/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
drastically.
Signed-off-by: Adrian Schmutzler
---
target/linux/ramips/image/Makefile | 1 +
target/linux/ramips/image/mt7621.mk | 68 +
target/linux/ramips/image/mt76x8.mk | 42 +-
target/linux/ramips/image/rt288x.mk | 10 +
4 files changed, 7 insertions
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Piotr Dymacz
> Sent: Dienstag, 21. Januar 2020 20:13
> To: Petr Štetiar ; openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH 19.07] ramips: mt7621: ubnt-erx:
Hi,
is there someone who can/wants to review the Semtech SX150x I2C GPIO expander
implemented for Netgear R6800 in https://github.com/openwrt/openwrt/pull/2614 ?
Best
Adrian
openpgp-digital-signature.asc
Description: PGP signature
___
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Piotr Dymacz
> Sent: Dienstag, 21. Januar 2020 00:34
> To: m...@adrianschmutzler.de; 'David Bauer' ;
> gch981...@gmail.com
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re:
Hi,
I will leave that decision to David, who merged it in the first place.
Best
Adrian
> -Original Message-
> From: Christoph Krapp [mailto:achte...@googlemail.com]
> Sent: Dienstag, 21. Januar 2020 12:01
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH] [19.07]
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Stijn Segers
> Sent: Montag, 20. Januar 2020 19:50
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH] [19.07] ramips: add kmod-mt7615e module to
> Netgear
lakiewicz
> Sent: Sonntag, 22. Dezember 2019 21:53
> To: openwrt-devel@lists.openwrt.org
> Cc: Adrian Schmutzler ; David Bauer bauer.net>
> Subject: [OpenWrt-Devel] [PATCH v2 2/4] ath79: WNDR4300: increase kernel
> partition to 4M
>
> Increase kernel partition from 2 MiB
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of Tomasz Maciej Nowak
> Sent: Montag, 20. Januar 2020 16:08
> To: Adrian Schmutzler ; openwrt-
> de...@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATC
of
the board name as variable.
Signed-off-by: Adrian Schmutzler
---
.../mvebu/base-files/etc/board.d/01_leds | 55 -
.../mvebu/base-files/lib/upgrade/platform.sh | 52
.../base-files/etc/board.d/02_network | 31 ++
.../base-files/lib/preinit
at it, change the DTS name of the armada-3720-udpu to lower-case,
which is the common practice for DTS file names.
Signed-off-by: Adrian Schmutzler
---
.../{armada-3720-uDPU.dts => armada-3720-udpu.dts} | 0
target/linux/mvebu/image/Makefile | 1 +
target/linux/mvebu/im
This moves the if conditions for choosing which image Makefiles
are used to the parent image/Makefile. It seems more convenient
to have "codeflow" in the parent while the subtarget-specific
files only contain the definitions.
Signed-off-by: Adrian Schmutzler
---
target/linux/m
In zynq target, the DEVICE_DTS variable is always set consistent
with the model part of the device definition name.
This patch replaces the redundant definitions for the individual
devices with a common recipe.
Signed-off-by: Adrian Schmutzler
---
target/linux/zynq/image/Makefile | 5 +
1
and
SUPPORTED_DEVICES addition there.
For new devices, nothing has changed, and just DEVICE_DTS has to
be set manually.
Signed-off-by: Adrian Schmutzler
---
target/linux/kirkwood/image/Makefile | 22 ++
1 file changed, 2 insertions(+), 20 deletions(-)
diff --git a/target/linux/kirkwood
Makefile to ensure
sysupgrade is still working.
Signed-off-by: Adrian Schmutzler
---
target/linux/octeon/image/Makefile | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/target/linux/octeon/image/Makefile
b/target/linux/octeon/image/Makefile
index 42bd5df1da
No need to have specific setup when default case does the same.
Signed-off-by: Adrian Schmutzler
---
target/linux/octeon/base-files/etc/board.d/01_network | 4
1 file changed, 4 deletions(-)
diff --git a/target/linux/octeon/base-files/etc/board.d/01_network
b/target/linux/octeon/base
Hi,
> -Original Message-
> From: Filip Moc [mailto:l...@moc6.cz]
> Sent: Freitag, 17. Januar 2020 13:53
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org; Enrico Mioso
> Subject: Re: [PATCH v4] ath79: add support for TP-Link TL-MR6400
>
> Hi,
>
Hi,
I've just sent an updated patch ("v4") to the list.
Some comments below.
> -Original Message-
> From: Filip Moc [mailto:l...@moc6.cz]
> Sent: Donnerstag, 16. Januar 2020 22:27
> To: Adrian Schmutzler
> Cc: 'Enrico Mioso' ; openwrt-devel@lists.openwrt.or
errors.
- eth1 (LAN) always shows carrier as 1 even if no cable is plugged in (this
works "correctly" on ar71xx)
Signed-off-by: Enrico Mioso
[rebase and several adjustments]
Signed-off-by: Adrian Schmutzler
Tested-by: Filip Moc
---
.../ath79/dts/qca9531_tplink_tl-mr6400-v1
Hi,
> - [ -z "$(echo $grp | cut -d: -f4 | grep $2)" ] || return
> - [ -n "$(echo $grp | grep ":$")" ] && delim=""
> + echo "$grp" | cut -d: -f4 | grep -q $2 || return
> + echo "$grp" | grep -q ":$" || delim=""
logic (&& ||) seems to be inverted here.
Just send the fixed one as
601 - 700 of 1150 matches
Mail list logo
