mtk-20170518/target/linux/ipq806x, branch master MTK 20170518 : Mediatek SDK based on OpenWRT Barrier Breaker kernel: bump 4.14 to 4.14.67 2018-08-28T21:05:39+00:00 Koen Vandeputte koen.vandeputte@ncentric.com 2018-08-28T14:10:40+00:00 01793e8752aa8211d6d74c92722787c403e5420d Refreshed all patches. Removed upstreamed patches: - 037-v4.18-0008-ARM-dts-BCM5301x-Fix-i2c-controller-interrupt-type.patch Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> 
Refreshed all patches.

Removed upstreamed patches:
- 037-v4.18-0008-ARM-dts-BCM5301x-Fix-i2c-controller-interrupt-type.patch

Compile-tested on: cns3xxx, imx6
Runtime-tested on: cns3xxx, imx6

Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
build: add mkrasimage 2018-08-28T09:26:53+00:00 David Bauer mail@david-bauer.net 2018-08-22T15:30:44+00:00 8e9a59a6b924469c0061d4bd945ae0c6dbfdecfe The current make-ras.sh image generation script for the ZyXEL NBG6617 has portability issues with bash. Because of this, factory images are currently not built correctly by the OpenWRT buildbots. This commit replaces the make-ras.sh by C-written mkrasimage. The new mkrasimage is also compatible with other ZyXEL devices using the ras image-format. This is not tested with the NBG6616 but it correctly builds the header for ZyXEL factory image. Signed-off-by: David Bauer <mail@david-bauer.net> 
The current make-ras.sh image generation script for the ZyXEL NBG6617
has portability issues with bash. Because of this, factory images are
currently not built correctly by the OpenWRT buildbots.

This commit replaces the make-ras.sh by C-written mkrasimage.

The new mkrasimage is also compatible with other ZyXEL devices using
the ras image-format.
This is not tested with the NBG6616 but it correctly builds the
header for ZyXEL factory image.

Signed-off-by: David Bauer <mail@david-bauer.net>
treewide: fix some cosmetic glitches in dts files 2018-08-27T17:31:17+00:00 Paul Wassi p.wassi@gmx.at 2018-08-23T07:35:04+00:00 e348ccc4e6e9d16d56bec77b69628205d58e6750 - fix single spaces hidden by a tab - replace indentation with spaces by tabs - make empty lines empty - drop trailing whitespace - drop unnecessary blank lines Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Paul Wassi <p.wassi@gmx.at> 
- fix single spaces hidden by a tab
- replace indentation with spaces by tabs
- make empty lines empty
- drop trailing whitespace
- drop unnecessary blank lines

Signed-off-by: Mathias Kresin <dev@kresin.me>
Signed-off-by: Paul Wassi <p.wassi@gmx.at>
treewide: fix upgrade led handling 2018-08-16T19:20:57+00:00 Mathias Kresin dev@kresin.me 2018-08-15T17:12:27+00:00 dd448cd2767c42d0ccde960da61585a2537eaf5a The upgrade led is only used if a running led is defined. If no running led is defined, the upgrade led is ignored and upgrade isn't indicated at all. Instead, turn off the running led prior to turning the upgrade led on. In most cases there isn't any visual change, but it allows to use an independent led for upgrade indication. Signed-off-by: Mathias Kresin <dev@kresin.me> 
The upgrade led is only used if a running led is defined. If no running
led is defined, the upgrade led is ignored and upgrade isn't indicated
at all.

Instead, turn off the running led prior to turning the upgrade led on.
In most cases there isn't any visual change, but it allows to use an
independent led for upgrade indication.

Signed-off-by: Mathias Kresin <dev@kresin.me>
treewide: consolidate upgrade state set 2018-08-16T19:20:57+00:00 Mathias Kresin dev@kresin.me 2018-08-15T16:55:01+00:00 56b8ac1e86eb5b0c500cbf8db60ce00aff01bcec Set the (sys)upgrade state when sourcing the stage2 script instead of setting the state for each target individual. This change fixes the, due to a missing state set, not working upgrade led on ath79 and apm821xx. Signed-off-by: Mathias Kresin <dev@kresin.me> 
Set the (sys)upgrade state when sourcing the stage2 script instead of
setting the state for each target individual.

This change fixes the, due to a missing state set, not working upgrade
led on ath79 and apm821xx.

Signed-off-by: Mathias Kresin <dev@kresin.me>
ipq806x: dts: Remove device_type = "ethernet-phy" 2018-07-19T16:58:24+00:00 Rosen Penev rosenp@gmail.com 2018-07-16T18:17:08+00:00 e22cc57593127bc888c6b04587a3a2e8e43abe66 device_type is deprecated. Upstream doesn't seem to like it either. Signed-off-by: Rosen Penev <rosenp@gmail.com> 
device_type is deprecated. Upstream doesn't seem to like it either.

Signed-off-by: Rosen Penev <rosenp@gmail.com>
ipq806x: fix numbering for Netgear R7800 LAN ports 2018-07-03T23:20:02+00:00 Aleksandr V. Piskunov aleksandr.v.piskunov@gmail.com 2018-07-01T13:40:37+00:00 36fea5a7b961132695918337f1c37b0e9a93978a Netgear R7800 switch LAN ports are numbered backwards in LuCI, i.e. numbering is not corresponding to the actual physical port labels, patch fixes that. Signed-off-by: Aleksandr V. Piskunov <aleksandr.v.piskunov@gmail.com> [merged with existing board using the same config] Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi> 
Netgear R7800 switch LAN ports are numbered backwards in LuCI,
i.e. numbering is not corresponding to the actual physical port labels,
patch fixes that.

Signed-off-by: Aleksandr V. Piskunov <aleksandr.v.piskunov@gmail.com>
[merged with existing board using the same config]
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
ipq806x: drop gpio export patch 2018-06-28T16:39:57+00:00 Mathias Kresin dev@kresin.me 2018-06-28T16:10:50+00:00 750e4b62b170c7709ebe2524588b35ff9faf0542 The hack isn't used by any board. Signed-off-by: Mathias Kresin <dev@kresin.me> 
The hack isn't used by any board.

Signed-off-by: Mathias Kresin <dev@kresin.me>
ipq806x: switch the NBG6817 wlan LEDs from amber to white 2018-06-28T16:39:57+00:00 Stefan Lippers-Hollmann s.l-h@gmx.de 2018-06-28T12:04:46+00:00 7c7ca66109468b57f06d20eafbb9523aecc91706 The original device support patch configured the amber wlan LEDs (which are meant as error indicator by the OEM) controlled by the SOC's GPIO as wlan traffic indicators, as the correct white wlan LEDs are connected to GPIOs controlled by the QCA9984/ ath10k wlan cards were not accessible. The recent addition of GPIO/ LED support to ath10k now makes it possible to use the correct white LEDs instead - and "mac80211: ath10k: use tpt LED trigger by default" also enables them by default. While both LEDs are independent of each other (two separate LEDs sharing one light tunnel), triggering both on wlan traffic is not the intended behaviour (bright yellow light). Tested on the ZyXEL NBG6817. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> 
The original device support patch configured the amber wlan LEDs (which
are meant as error indicator by the OEM) controlled by the SOC's GPIO
as wlan traffic indicators, as the correct white wlan LEDs are
connected to GPIOs controlled by the QCA9984/ ath10k wlan cards were
not accessible. The recent addition of GPIO/ LED support to ath10k now
makes it possible to use the correct white LEDs instead - and
"mac80211: ath10k: use tpt LED trigger by default" also enables them by
default. While both LEDs are independent of each other (two separate
LEDs sharing one light tunnel), triggering both on wlan traffic is not
the intended behaviour (bright yellow light).

Tested on the ZyXEL NBG6817.

Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
ipq806x: remove "firmware" partition definition from netgear routers 2018-06-27T20:11:06+00:00 Hannu Nyman hannu.nyman@iki.fi 2018-06-27T18:52:45+00:00 7b74b40fe927ae5d2f88dfab8e26b75207878c9d Remove the "firmware" partition definition from the DTS of R7800 to fix sysupgrade. Commit 4645a6d3 defined CONFIG_MTD_SPLIT_UIMAGE_FW=y for ipq806x and that causes mtd to misbehave as additional kernel and ubi partitions are detected from inside the "firmware" partition. [ 1.111324] 0x000001480000-0x000001880000 : "kernel" [ 1.121005] 0x000001880000-0x000007900000 : "ubi" [ 1.283912] 0x000007900000-0x000008000000 : "reserve" [ 1.296407] 0x000001480000-0x000007900000 : "firmware" [ 1.468043] no rootfs found after FIT image in "firmware" [ 2.426860] 2 uimage-fw partitions found on MTD device firmware [ 2.426931] 0x000001480000-0x000001880000 : "kernel" [ 2.440420] 0x000001880000-0x000007900000 : "ubi" Both kernel and ubi are already defined in DTS, so this duplication leads into errors in sysupgrade: Writing from <stdin> to kernel ... ubiattach: error!: strtoul: unable to parse the number '6 mtd10' ubiattach: error!: bad MTD device number: "6 mtd10" The partition is defined to same area as kernel+ubi, and is not needed for sysupgrade anymore. Remove it to fix things. Only tested for the R7800 but all of them should behave equal. Fixes: FS#1617 Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi> [squashed commits, add "tested on" note] Signed-off-by: Mathias Kresin <dev@kresin.me> 
Remove the "firmware" partition definition from the DTS of R7800
to fix sysupgrade.

Commit 4645a6d3 defined CONFIG_MTD_SPLIT_UIMAGE_FW=y for ipq806x
and that causes mtd to misbehave as additional kernel and ubi
partitions are detected from inside the "firmware" partition.
  [    1.111324] 0x000001480000-0x000001880000 : "kernel"
  [    1.121005] 0x000001880000-0x000007900000 : "ubi"
  [    1.283912] 0x000007900000-0x000008000000 : "reserve"
  [    1.296407] 0x000001480000-0x000007900000 : "firmware"
  [    1.468043] no rootfs found after FIT image in "firmware"
  [    2.426860] 2 uimage-fw partitions found on MTD device firmware
  [    2.426931] 0x000001480000-0x000001880000 : "kernel"
  [    2.440420] 0x000001880000-0x000007900000 : "ubi"

Both kernel and ubi are already defined in DTS, so this duplication
leads into errors in sysupgrade:
  Writing from <stdin> to kernel ...
  ubiattach: error!: strtoul: unable to parse the number '6 mtd10'
  ubiattach: error!: bad MTD device number: "6 mtd10"

The partition is defined to same area as kernel+ubi, and is not
needed for sysupgrade anymore. Remove it to fix things.

Only tested for the R7800 but all of them should behave equal.

Fixes: FS#1617

Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
[squashed commits, add "tested on" note]
Signed-off-by: Mathias Kresin <dev@kresin.me>