[no subject]
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 ---
Signed-off-by: Sebastian Careba
---
.../999-resize mamba kernel.patch | 50 ---
1 file changed, 50 deletions(-)
delete mode 100644 target/linux/mvebu/patches-5.10/999-resize mamba
kernel.patch
diff --git a/target/linux/mvebu/patches-5.10/999-resize mamba kernel.patch
b/target/linux/mvebu/patches-5.10/999-resize mamba kernel.patch
deleted file mode 100644
index a4230a4104..00
--- a/target/linux/mvebu/patches-5.10/999-resize mamba kernel.patch
+++ /dev/null
@@ -1,50 +0,0 @@
-diff --git
a/target/linux/mvebu/patches-5.4/999-DNM-dts-mamba-resize-3MB_to_4MB.patch
b/target/linux/mvebu/patches-5.4/999-DNM-dts-mamba-resize-3MB_to_4MB.patch
-new file mode 100644
-index 00..2752a92a3f
/dev/null
-+++ b/target/linux/mvebu/patches-5.4/999-DNM-dts-mamba-resize-3MB_to_4MB.patch
-@@ -0,0 +1,41 @@
-From 258233f00bcd013050efee00c5d9128ef8cd62dd Mon Sep 17 00:00:00 2001
-From: Tad
-Date: Fri, 5 Feb 2021 22:32:11 -0500
-Subject: [PATCH] DNM: ARM: dts: armada-xp-linksys-mamba: Increase kernel
- partition to 4MB
-
- arch/arm/boot/dts/armada-xp-linksys-mamba.dts | 8
- 1 file changed, 4 insertions(+), 4 deletions(-)
-
-diff --git a/arch/arm/boot/dts/armada-xp-linksys-mamba.dts
b/arch/arm/boot/dts/armada-xp-linksys-mamba.dts
-index d7bc27ae6..20e859021 100644
a/arch/arm/boot/dts/armada-xp-linksys-mamba.dts
-+++ b/arch/arm/boot/dts/armada-xp-linksys-mamba.dts
-@@ -456,9 +456,9 @@
- reg = <0xa0 0x280>; /* 40MB */
- };
-
-- partition@d0 {
-+ partition@e0 {
- label = "rootfs1";
-- reg = <0xd0 0x250>; /* 37MB */
-+ reg = <0xe0 0x240>; /* 36MB */
- };
-
- /* kernel2 overlaps with rootfs2 by design */
-@@ -467,9 +467,9 @@
- reg = <0x320 0x280>; /* 40MB */
- };
-
-- partition@350 {
-+ partition@360 {
- label = "rootfs2";
-- reg = <0x350 0x250>; /* 37MB */
-+ reg = <0x360 0x240>; /* 36MB */
- };
-
- /*
---
-2.29.2
-
---
-2.29.2
-
--
2.30.0
--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[no subject]
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 --- Signed-off-by: Sebastian Careba --- target/linux/mvebu/Makefile | 8 +- target/linux/mvebu/config-5.10| 436 ++ .../patches-5.10/002-add_powertables.patch| 770 ++ .../004-add_sata_disk_activity_trigger.patch | 39 + ...5-linksys_hardcode_nand_ecc_settings.patch | 17 + ...Mangle-bootloader-s-kernel-arguments.patch | 189 + ...sallow-XDP-program-on-hardware-buffe.patch | 53 ++ .../030-linkstation-poweroff.patch| 20 + .../patches-5.10/100-find_active_root.patch | 60 ++ .../patches-5.10/102-revert_i2c_delay.patch | 15 + .../205-armada-385-rd-mtd-partitions.patch| 19 + .../206-ARM-mvebu-385-ap-Add-partitions.patch | 35 + ...-armada-xp-linksys-mamba-broken-idle.patch | 10 + .../231-armada-xp-linksys-mamba-wan.patch | 11 + .../patches-5.10/240-linksys-status-led.patch | 50 ++ .../241-linksys-use-eth0-as-cpu-port.patch| 25 + .../250-adjust-compatible-for-linksys.patch | 68 ++ .../300-mvneta-tx-queue-workaround.patch | 26 + ...dicate-failure-to-enter-deeper-sleep.patch | 40 + ...-pci-mvebu-time-out-reset-on-link-up.patch | 60 ++ ...5-PCI-aardvark-Improve-link-training.patch | 135 +++ ...06-PCI-aardvark-Issue-PERST-via-GPIO.patch | 57 ++ .../407-PCI-aardvark-Add-PHY-support.patch| 116 +++ ...-t-touch-PCIe-registers-if-no-card-c.patch | 50 ++ ...-initialization-with-old-Marvell-s-A.patch | 44 + ...da388-clearfog-emmc-on-clearfog-base.patch | 87 ++ ...ts-marvell-armada37xx-Add-eth0-alias.patch | 20 + ...witch-PHY-operation-mode-to-2500base.patch | 20 + .../560-helios4-dts-status-led-alias.patch| 28 + ...-mvebu-armada-38x-enable-libata-leds.patch | 10 + .../999-resize mamba kernel.patch | 50 ++ 31 files changed, 2565 insertions(+), 3 deletions(-) create mode 100644 target/linux/mvebu/config-5.10 create mode 100644 target/linux/mvebu/patches-5.10/002-add_powertables.patch create mode 100644 target/linux/mvebu/patches-5.10/004-add_sata_disk_activity_trigger.patch create mode 100644 target/linux/mvebu/patches-5.10/005-linksys_hardcode_nand_ecc_settings.patch create mode 100644 target/linux/mvebu/patches-5.10/006-mvebu-Mangle-bootloader-s-kernel-arguments.patch create mode 100644 target/linux/mvebu/patches-5.10/022-mvneta-driver-disallow-XDP-program-on-hardware-buffe.patch create mode 100644 target/linux/mvebu/patches-5.10/030-linkstation-poweroff.patch create mode 100644 target/linux/mvebu/patches-5.10/100-find_active_root.patch create mode 100644 target/linux/mvebu/patches-5.10/102-revert_i2c_delay.patch create mode 100644 target/linux/mvebu/patches-5.10/205-armada-385-rd-mtd-partitions.patch create mode 100644 target/linux/mvebu/patches-5.10/206-ARM-mvebu-385-ap-Add-partitions.patch create mode 100644 target/linux/mvebu/patches-5.10/230-armada-xp-linksys-mamba-broken-idle.patch create mode 100644 target/linux/mvebu/patches-5.10/231-armada-xp-linksys-mamba-wan.patch create mode 100644 target/linux/mvebu/patches-5.10/240-linksys-status-led.patch create mode 100644 target/linux/mvebu/patches-5.10/241-linksys-use-eth0-as-cpu-port.patch create mode 100644 target/linux/mvebu/patches-5.10/250-adjust-compatible-for-linksys.patch create mode 100644 target/linux/mvebu/patches-5.10/300-mvneta-tx-queue-workaround.patch create mode 100644 target/linux/mvebu/patches-5.10/400-cpuidle-mvebu-indicate-failure-to-enter-deeper-sleep.patch create mode 100644 target/linux/mvebu/patches-5.10/401-pci-mvebu-time-out-reset-on-link-up.patch create mode 100644 target/linux/mvebu/patches-5.10/405-PCI-aardvark-Improve-link-training.patch create mode 100644 target/linux/mvebu/patches-5.10/406-PCI-aardvark-Issue-PERST-via-GPIO.patch create mode 100644 target/linux/mvebu/patches-5.10/407-PCI-aardvark-Add-PHY-support.patch create mode 100644 target/linux/mvebu/patches-5.10/408-PCI-aardvark-Don-t-touch-PCIe-registers-if-no-card-c.patch create mode 100644 target/linux/mvebu/patches-5.10/410-PCI-aardvark-Fix-initialization-with-old-Marvell-s-A.patch create mode 100644 target/linux/mvebu/patches-5.10/412-ARM-dts-armada388-clearfog-emmc-on-clearfog-base.patch create mode 100644 target/linux/mvebu/patches-5.10/520-arm64-dts-marvell-armada37xx-Add-eth0-alias.patch create mode 100644 target/linux/mvebu/patches-5.10/550-arm64-dts-uDPU-switch-PHY-operation-mode-to-2500base.patch create mode 100644 target/linux/mvebu/patches-5.10/560-helios4-dts-status-led-alias.patch create mode 100644 target/linux/mvebu/patches-5.10/561-mvebu-armada-38x-enable-libata-leds.patch create mode 100644 target/linux/mvebu/patches-5.10/999-resize mamba kernel.patch diff --git
Re: kernel 5.10: Wireguard wants some love
I hacked on it in https://github.com/openwrt/openwrt/pull/3876, not too pretty, but we can remove the whole thing once 5.4 is gone. On Tue, Feb 16, 2021 at 4:22 PM Ansuel Smith wrote: > > The compat module is no longer required and complains > about wireguard included in kernel from version 5.6. > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] mpc85xx-p1010: add Kernel 5.10 support
Hi Daniel, On 2/17/21 4:21 AM, Daniel Golle wrote: > On Tue, Feb 16, 2021 at 11:48:04PM +0100, David Bauer wrote: >> Tested on: Sophos RED 15W >> >> The TP-Link WL-WDR4900 needs to be disabled when 5.10 becomes the >> default kernel. > > That's sad. Why? See the next sentence ;) as well as this GitHub issue: https://github.com/openwrt/openwrt/pull/1773 Best David > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] mpc85xx-p1010: add Kernel 5.10 support
On Tue, Feb 16, 2021 at 11:48:04PM +0100, David Bauer wrote: > Tested on: Sophos RED 15W > > The TP-Link WL-WDR4900 needs to be disabled when 5.10 becomes the > default kernel. That's sad. Why? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] generic: don't lock when recursively deleting partitions
When recursively deleting partitions, don't acquire the masters
partition lock twice. Otherwise the process endy up in a deadlocked
state.
Signed-off-by: David Bauer
---
...when-recursively-deleting-partitions.patch | 24 +++
1 file changed, 24 insertions(+)
create mode 100644
target/linux/generic/pending-5.10/499-mtd-don-t-lock-when-recursively-deleting-partitions.patch
diff --git
a/target/linux/generic/pending-5.10/499-mtd-don-t-lock-when-recursively-deleting-partitions.patch
b/target/linux/generic/pending-5.10/499-mtd-don-t-lock-when-recursively-deleting-partitions.patch
new file mode 100644
index 00..505131b684
--- /dev/null
+++
b/target/linux/generic/pending-5.10/499-mtd-don-t-lock-when-recursively-deleting-partitions.patch
@@ -0,0 +1,24 @@
+From: David Bauer
+Date: Wed, 17 Feb 2021 03:21:39 +0100
+Subject: [PATCH] mtd: don't lock when recursively deleting partitions
+
+When recursively deleting partitions, don't acquire the masters
+partition lock twice. Otherwise the process endy up in a deadlocked
+state.
+
+Signed-off-by: David Bauer
+---
+ drivers/mtd/mtdpart.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/mtd/mtdpart.c
b/drivers/mtd/mtdpart.c
+@@ -474,7 +474,7 @@ static int __del_mtd_partitions(struct m
+
+ list_for_each_entry_safe(child, next, >partitions, part.node) {
+ if (mtd_has_partitions(child))
+- del_mtd_partitions(child);
++ __del_mtd_partitions(child);
+
+ pr_info("Deleting %s MTD partition\n", child->name);
+ ret = del_mtd_device(child);
--
2.30.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] openssl: bump to 1.1.1j
This fixes 4 security vulnerabilities/bugs: - CVE-2021-2839 - SSLv2 vulnerability. Openssl 1.1.1 does not support SSLv2, but the affected functions still exist. Considered just a bug. - CVE-2021-2840 - calls EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. - CVE-2021-2841 - The X509_issuer_and_serial_hash() function attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it was failing to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. - Fixed SRP_Calc_client_key so that it runs in constant time. This could be exploited in a side channel attack to recover the password. The 3 CVEs above are currently awaiting analysis. Signed-off-by: Eneas U de Queiroz --- This was run-tested on a WRT3200ACM (mvebu), using nginx, and wpad, and openssl-util. diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile index 714ce2059a..4fb4cb2784 100644 --- a/package/libs/openssl/Makefile +++ b/package/libs/openssl/Makefile @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=openssl PKG_BASE:=1.1.1 -PKG_BUGFIX:=i +PKG_BUGFIX:=j PKG_VERSION:=$(PKG_BASE)$(PKG_BUGFIX) PKG_RELEASE:=1 PKG_USE_MIPS16:=0 @@ -24,7 +24,7 @@ PKG_SOURCE_URL:= \ ftp://ftp.pca.dfn.de/pub/tools/net/openssl/source/ \ http://www.openssl.org/source/ \ http://www.openssl.org/source/old/$(PKG_BASE)/ -PKG_HASH:=e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee00d5242 +PKG_HASH:=aaf2fcb575cdf6491b98ab4829abf78a3dec8402b8b81efc8f23c00d443981bf PKG_LICENSE:=OpenSSL PKG_LICENSE_FILES:=LICENSE ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: [PATCH] ramips: mt7621: add TP-Link EAP235-Wall support
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Sander Vanheule
> Sent: Sonntag, 14. Februar 2021 11:03
> To: openwrt-devel@lists.openwrt.org
> Cc: Sander Vanheule ; Stijn Segers
>
> Subject: [PATCH] ramips: mt7621: add TP-Link EAP235-Wall support
>
> The TP-Link EAP235-Wall is a wall-mounted, PoE-powered AC1200 access
> point with four gigabit ethernet ports.
>
> When connecting to the device's serial port, it is strongly advised to use an
> isolated UART adapter. This prevents linking different power domains
> created by the PoE power supply, which may damage your devices.
>
> The device's U-Boot supports saving modified environments with `saveenv`.
> However, there is no u-boot-env partition, and saving modifications will
> cause the partition table to be overwritten. This is not an issue for running
> OpenWrt, but will prevent the vendor FW from functioning properly.
>
> Device specifications:
> * SoC: MT7621DAT
> * RAM: 128MiB
> * Flash: 16MiB SPI-NOR
> * Wireless 2.4GHz (MT7603EN): b/g/n, 2x2
> * Wireless 5GHz (MT7613BEN): a/n/ac, 2x2
> * Ethernet: 4× GbE
> * Back side: ETH0, PoE PD port
> * Bottom side: ETH1, ETH2, ETH3
> * Single white device LED
> * LED button, reset button (available for failsafe)
> * PoE pass-through on port ETH3 (enabled with GPIO)
>
> Datasheet of the flash chip specifies a maximum frequency of 33MHz, but
> that didn't work. 20MHz gives no errors with reading (flash dump) or writing
> (sysupgrade).
>
> Device mac addresses:
> Stock firmware uses the same MAC address for ethernet (on device label)
> and 2.4GHz wireless. The 5GHz wireless address is incremented by one.
> This address is stored in the 'info' ('default-mac') partition at an offset
> of 8
> bytes.
> From OEM ifconfig:
> eth a4:2b:b0:...:88
> ra0 a4:2b:b0:...:88
> rai0a4:2b:b0:...:89
>
> Flashing instructions:
> * Enable SSH in the web interface, and SSH into the target device
> * run `cliclientd stopcs`, this should return "success"
> * upload the factory image via the web interface
>
> Debricking:
> U-boot can be interrupted during boot, serial console is 57600 baud, 8n1 This
> allows installing a sysupgrade image, or fixing the device in another way.
> * Access serial header from the side of the board, close to ETH3,
> pin-out is (1:TX, 2:RX, 3:GND, 4:3.3V), with pin 1 closest to ETH3.
> * Interrupt bootloader by holding '4' during boot, which drops the
> bootloader into its shell
> * Change default 'serverip' and 'ipaddr' variables (optional)
> * Download initramfs with `tftpboot`, and boot image with `bootm`
> # tftpboot 8400 openwrt-initramfs.bin
> # bootm
>
> Hardware was kindly provided for porting by Stijn Segers.
>
> Tested-by: Stijn Segers
> Signed-off-by: Sander Vanheule
> ---
> Known issues with this device:
> The MT7613BE radio is currently not well supported by the mt7615 driver:
> - The EEPROM blob is not recognized, so (Tx) power levels aren't useful.
> Patch sent to linux-wireless:
> https://lore.kernel.org/linux-wireless/20210202085953.9564-1-
> san...@svanheule.net/
> - DFS support is incomplete (known issue for MT7613)
> - Radio stops responding after a while when idling, reboot required to
> bring it to life. Reported by Stijn, appears to be introduced by
> 2021-01-27 bump of mt76.
Please add the known issues to the preserved part of the commit message, I
think it's valuable information also for others.
>
> kern.err kernel: [ 7099.554067] mt7615e :02:00.0: Message 73 (seq 1)
> timeout
>
> .../dts/mt7621_tplink_eap235-wall-v1.dts | 172 ++
> target/linux/ramips/image/mt7621.mk | 12 ++
> .../mt7621/base-files/etc/board.d/02_network | 3 +
> tools/firmware-utils/src/tplink-safeloader.c | 29 +++
> 4 files changed, 216 insertions(+)
> create mode 100644 target/linux/ramips/dts/mt7621_tplink_eap235-wall-
> v1.dts
>
> diff --git a/target/linux/ramips/dts/mt7621_tplink_eap235-wall-v1.dts
> b/target/linux/ramips/dts/mt7621_tplink_eap235-wall-v1.dts
> new file mode 100644
> index 00..d63623dcbd
> --- /dev/null
> +++ b/target/linux/ramips/dts/mt7621_tplink_eap235-wall-v1.dts
> @@ -0,0 +1,172 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later #include "mt7621.dtsi"
I'd put an empty line between SPDX and first include.
> +
> +#include
> +#include
> +#include
> +
> +/ {
> + compatible = "tplink,eap235-wall-v1", "mediatek,mt7621-soc";
> + model = "TP-LINK EAP235-Wall v1";
"TP-Link" for consistency.
> +
> + aliases {
> + label-mac-device =
> + led-boot = _status;
> + led-failsafe = _status;
> + led-running = _status;
> + led-upgrade = _status;
> + };
> +
> + leds {
> + compatible = "gpio-leds";
> +
> + led_status: status {
> + label = "white:status";
> + color = ;
kernel 5.10: Wireguard wants some love
The compat module is no longer required and complains about wireguard included in kernel from version 5.6. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] rockchip: add Kernel 5.10 support
Remove all upstreamed patches and add the kernel configuration for version 5.10. The Rock Pi 4 was split in multiple versions. Add a DTS with the old name in order to keep compatibility while having kernel 5.4 and 5.10 in parallel. Switch to the Rock Pi 4A DTS once Kernel 5.4 support is removed. Tested-on: Nanoi R2S Signed-off-by: David Bauer --- target/linux/rockchip/Makefile| 1 + target/linux/rockchip/armv8/config-5.10 | 673 ++ target/linux/rockchip/armv8/config-5.4| 165 - target/linux/rockchip/config-default | 297 .../boot/dts/rockchip/rk3399-rock-pi-4.dts| 19 + ...-r8152-add-LED-configuration-from-OF.patch | 74 ++ ...et-add-RTL8152-binding-documentation.patch | 54 ++ ...-rockchip-use-system-LED-for-OpenWrt.patch | 31 + ...usb3-controller-node-for-RK3328-SoCs.patch | 62 ++ ...ckchip-enable-LAN-port-on-NanoPi-R2S.patch | 60 ++ ...dd-OF-node-for-USB-eth-on-NanoPi-R2S.patch | 28 + ...-host-by-default-on-rk3399-rock-pi-4.patch | 32 + 12 files changed, 1178 insertions(+), 318 deletions(-) create mode 100644 target/linux/rockchip/armv8/config-5.10 delete mode 100644 target/linux/rockchip/config-default create mode 100644 target/linux/rockchip/files-5.10/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dts create mode 100644 target/linux/rockchip/patches-5.10/002-net-usb-r8152-add-LED-configuration-from-OF.patch create mode 100644 target/linux/rockchip/patches-5.10/003-dt-bindings-net-add-RTL8152-binding-documentation.patch create mode 100644 target/linux/rockchip/patches-5.10/100-rockchip-use-system-LED-for-OpenWrt.patch create mode 100644 target/linux/rockchip/patches-5.10/101-dts-rockchip-add-usb3-controller-node-for-RK3328-SoCs.patch create mode 100644 target/linux/rockchip/patches-5.10/102-rockchip-enable-LAN-port-on-NanoPi-R2S.patch create mode 100644 target/linux/rockchip/patches-5.10/103-arm64-rockchip-add-OF-node-for-USB-eth-on-NanoPi-R2S.patch create mode 100644 target/linux/rockchip/patches-5.10/104-rockchip-use-USB-host-by-default-on-rk3399-rock-pi-4.patch diff --git a/target/linux/rockchip/Makefile b/target/linux/rockchip/Makefile index bcc0cc3f8f..7aeb0a3d55 100644 --- a/target/linux/rockchip/Makefile +++ b/target/linux/rockchip/Makefile @@ -8,6 +8,7 @@ FEATURES:=ext4 audio usb usbgadget display gpio fpu rootfs-part boot-part squash SUBTARGETS:=armv8 KERNEL_PATCHVER=5.4 +KERNEL_TESTING_PATCHVER=5.10 define Target/Description Build firmware image for Rockchip SoC devices. diff --git a/target/linux/rockchip/armv8/config-5.10 b/target/linux/rockchip/armv8/config-5.10 new file mode 100644 index 00..80230a722b --- /dev/null +++ b/target/linux/rockchip/armv8/config-5.10 @@ -0,0 +1,673 @@ +CONFIG_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_KEEP_MEMBLOCK=y +CONFIG_ARCH_MMAP_RND_BITS=18 +CONFIG_ARCH_MMAP_RND_BITS_MAX=33 +CONFIG_ARCH_MMAP_RND_BITS_MIN=18 +CONFIG_ARCH_MMAP_RND_COMPAT_BITS=11 +CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=11 +CONFIG_ARCH_PROC_KCORE_TEXT=y +CONFIG_ARCH_ROCKCHIP=y +CONFIG_ARCH_SELECT_MEMORY_MODEL=y +CONFIG_ARCH_SPARSEMEM_DEFAULT=y +CONFIG_ARCH_SPARSEMEM_ENABLE=y +CONFIG_ARCH_STACKWALK=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +CONFIG_ARC_EMAC_CORE=y +CONFIG_ARM64=y +CONFIG_ARM64_4K_PAGES=y +CONFIG_ARM64_CNP=y +# CONFIG_ARM64_ERRATUM_1165522 is not set +# CONFIG_ARM64_ERRATUM_1286807 is not set +# CONFIG_ARM64_ERRATUM_1418040 is not set +CONFIG_ARM64_ERRATUM_819472=y +CONFIG_ARM64_ERRATUM_824069=y +CONFIG_ARM64_ERRATUM_826319=y +CONFIG_ARM64_ERRATUM_827319=y +CONFIG_ARM64_ERRATUM_832075=y +CONFIG_ARM64_ERRATUM_843419=y +CONFIG_ARM64_ERRATUM_845719=y +CONFIG_ARM64_ERRATUM_858921=y +CONFIG_ARM64_HW_AFDBM=y +CONFIG_ARM64_MODULE_PLTS=y +CONFIG_ARM64_PAGE_SHIFT=12 +CONFIG_ARM64_PAN=y +CONFIG_ARM64_PA_BITS=48 +CONFIG_ARM64_PA_BITS_48=y +CONFIG_ARM64_PTR_AUTH=y +CONFIG_ARM64_RAS_EXTN=y +CONFIG_ARM64_SVE=y +# CONFIG_ARM64_SW_TTBR0_PAN is not set +CONFIG_ARM64_TAGGED_ADDR_ABI=y +CONFIG_ARM64_UAO=y +CONFIG_ARM64_VA_BITS=48 +# CONFIG_ARM64_VA_BITS_39 is not set +CONFIG_ARM64_VA_BITS_48=y +CONFIG_ARM64_VHE=y +CONFIG_ARM64_WORKAROUND_CLEAN_CACHE=y +# CONFIG_ARMV8_DEPRECATED is not set +CONFIG_ARM_AMBA=y +CONFIG_ARM_ARCH_TIMER=y +CONFIG_ARM_ARCH_TIMER_EVTSTREAM=y +CONFIG_ARM_ARCH_TIMER_OOL_WORKAROUND=y +CONFIG_ARM_CPUIDLE=y +CONFIG_ARM_GIC=y +CONFIG_ARM_GIC_V2M=y +CONFIG_ARM_GIC_V3=y +CONFIG_ARM_GIC_V3_ITS=y +CONFIG_ARM_GIC_V3_ITS_PCI=y +CONFIG_ARM_MHU=y +CONFIG_ARM_PSCI_CPUIDLE=y +CONFIG_ARM_PSCI_CPUIDLE_DOMAIN=y +CONFIG_ARM_PSCI_FW=y +# CONFIG_ARM_RK3399_DMC_DEVFREQ is not set +# CONFIG_ARM_SCMI_PROTOCOL is not set +CONFIG_ARM_SCPI_CPUFREQ=y +CONFIG_ARM_SCPI_POWER_DOMAIN=y +CONFIG_ARM_SCPI_PROTOCOL=y +CONFIG_ARM_SMMU=y +CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT=y +# CONFIG_ARM_SMMU_LEGACY_DT_BINDINGS is not set +CONFIG_ARM_SMMU_V3=y +# CONFIG_ARM_SMMU_V3_SVA is not set +CONFIG_AUDIT_ARCH_COMPAT_GENERIC=y
[PATCH] mpc85xx-p1010: add Kernel 5.10 support
Tested on: Sophos RED 15W The TP-Link WL-WDR4900 needs to be disabled when 5.10 becomes the default kernel. When building with all kmods enabled, the resulting kernel image exceeds the maximum size the bootloader reads from the flash. For more information, see GitHub issue #1773 Signed-off-by: David Bauer --- target/linux/mpc85xx/config-5.10 | 280 ++ target/linux/mpc85xx/p1010/target.mk | 2 + ...85xx-add-gpio-keys-to-of-match-table.patch | 10 + ...0-powerpc-85xx-tl-wdr4900-v1-support.patch | 83 ++ .../101-powerpc-85xx-hiveap-330-support.patch | 30 ++ .../102-powerpc-add-cmdline-override.patch| 37 +++ .../103-powerpc-85xx-red-15w-rev1.patch | 29 ++ ...change-P2020RDB-dts-file-for-OpenWRT.patch | 162 ++ .../105-powerpc-85xx-panda-support.patch | 30 ++ .../106-powerpc-85xx-ws-ap3710i-support.patch | 30 ++ ...ootwrapper-disable-uImage-generation.patch | 42 +++ 11 files changed, 735 insertions(+) create mode 100644 target/linux/mpc85xx/config-5.10 create mode 100644 target/linux/mpc85xx/patches-5.10/001-powerpc-85xx-add-gpio-keys-to-of-match-table.patch create mode 100644 target/linux/mpc85xx/patches-5.10/100-powerpc-85xx-tl-wdr4900-v1-support.patch create mode 100644 target/linux/mpc85xx/patches-5.10/101-powerpc-85xx-hiveap-330-support.patch create mode 100644 target/linux/mpc85xx/patches-5.10/102-powerpc-add-cmdline-override.patch create mode 100644 target/linux/mpc85xx/patches-5.10/103-powerpc-85xx-red-15w-rev1.patch create mode 100644 target/linux/mpc85xx/patches-5.10/104-powerpc-mpc85xx-change-P2020RDB-dts-file-for-OpenWRT.patch create mode 100644 target/linux/mpc85xx/patches-5.10/105-powerpc-85xx-panda-support.patch create mode 100644 target/linux/mpc85xx/patches-5.10/106-powerpc-85xx-ws-ap3710i-support.patch create mode 100644 target/linux/mpc85xx/patches-5.10/900-powerpc-bootwrapper-disable-uImage-generation.patch diff --git a/target/linux/mpc85xx/config-5.10 b/target/linux/mpc85xx/config-5.10 new file mode 100644 index 00..cb0d08ba91 --- /dev/null +++ b/target/linux/mpc85xx/config-5.10 @@ -0,0 +1,280 @@ +# CONFIG_40x is not set +# CONFIG_44x is not set +# CONFIG_ADVANCED_OPTIONS is not set +CONFIG_AR8216_PHY=y +CONFIG_AR8216_PHY_LEDS=y +CONFIG_ARCH_32BIT_OFF_T=y +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_KEEP_MEMBLOCK=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y +CONFIG_ARCH_MIGHT_HAVE_PC_SERIO=y +CONFIG_ARCH_MMAP_RND_BITS=11 +CONFIG_ARCH_MMAP_RND_BITS_MAX=17 +CONFIG_ARCH_MMAP_RND_BITS_MIN=11 +CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=17 +CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=11 +CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +CONFIG_ARCH_WEAK_RELEASE_ACQUIRE=y +CONFIG_ASN1=y +CONFIG_AUDIT_ARCH=y +CONFIG_BLK_MQ_PCI=y +CONFIG_BOOKE=y +CONFIG_BOOKE_WDT=y +# CONFIG_BSC9131_RDB is not set +# CONFIG_BSC9132_QDS is not set +# CONFIG_C293_PCIE is not set +CONFIG_CLONE_BACKWARDS=y +CONFIG_CLZ_TAB=y +CONFIG_CMDLINE="console=ttyS0,115200" +CONFIG_CMDLINE_FROM_BOOTLOADER=y +# CONFIG_CMDLINE_OVERRIDE is not set +# CONFIG_COMMON_CLK is not set +CONFIG_COMPAT_32BIT_TIME=y +# CONFIG_CORENET_GENERIC is not set +# CONFIG_CPM2 is not set +CONFIG_CPU_BIG_ENDIAN=y +CONFIG_CRYPTO_AEAD=y +CONFIG_CRYPTO_AEAD2=y +# CONFIG_CRYPTO_AES_PPC_SPE is not set +CONFIG_CRYPTO_AKCIPHER=y +CONFIG_CRYPTO_AKCIPHER2=y +CONFIG_CRYPTO_AUTHENC=y +CONFIG_CRYPTO_HASH=y +CONFIG_CRYPTO_HASH2=y +CONFIG_CRYPTO_HW=y +CONFIG_CRYPTO_LIB_POLY1305_RSIZE=1 +CONFIG_CRYPTO_MANAGER=y +CONFIG_CRYPTO_MANAGER2=y +# CONFIG_CRYPTO_MD5_PPC is not set +CONFIG_CRYPTO_NULL=y +CONFIG_CRYPTO_NULL2=y +CONFIG_CRYPTO_RNG=y +CONFIG_CRYPTO_RNG2=y +CONFIG_CRYPTO_RSA=y +# CONFIG_CRYPTO_SHA1_PPC is not set +# CONFIG_CRYPTO_SHA1_PPC_SPE is not set +# CONFIG_CRYPTO_SHA256_PPC_SPE is not set +CONFIG_DATA_SHIFT=12 +CONFIG_DEBUG_BUGVERBOSE=y +CONFIG_DNOTIFY=y +CONFIG_DTC=y +# CONFIG_E200 is not set +CONFIG_E500=y +# CONFIG_E5500_CPU is not set +# CONFIG_E6500_CPU is not set +CONFIG_EARLY_PRINTK=y +CONFIG_EDAC_ATOMIC_SCRUB=y +CONFIG_EDAC_SUPPORT=y +CONFIG_ENABLE_MUST_CHECK=y +CONFIG_FIXED_PHY=y +CONFIG_FSL_BOOKE=y +CONFIG_FSL_EMB_PERFMON=y +# CONFIG_FSL_ENETC_MDIO is not set +# CONFIG_FSL_FMAN is not set +CONFIG_FSL_LBC=y +CONFIG_FSL_PCI=y +CONFIG_FSL_PQ_MDIO=y +CONFIG_FSL_SOC=y +CONFIG_FSL_SOC_BOOKE=y +CONFIG_FW_LOADER_PAGED_BUF=y +CONFIG_GENERIC_ALLOCATOR=y +CONFIG_GENERIC_ATOMIC64=y +CONFIG_GENERIC_BUG=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_GENERIC_CMOS_UPDATE=y +CONFIG_GENERIC_CPU=y +CONFIG_GENERIC_CPU_AUTOPROBE=y +CONFIG_GENERIC_CPU_VULNERABILITIES=y +CONFIG_GENERIC_EARLY_IOREMAP=y +CONFIG_GENERIC_IRQ_SHOW=y +CONFIG_GENERIC_IRQ_SHOW_LEVEL=y +CONFIG_GENERIC_ISA_DMA=y +CONFIG_GENERIC_PCI_IOMAP=y +CONFIG_GENERIC_SMP_IDLE_THREAD=y +CONFIG_GENERIC_STRNCPY_FROM_USER=y +CONFIG_GENERIC_STRNLEN_USER=y +CONFIG_GENERIC_TIME_VSYSCALL=y +CONFIG_GEN_RTC=y +# CONFIG_GE_IMP3A is not set +CONFIG_GIANFAR=y +CONFIG_GPIOLIB=y
RE: [PATCH] ltq-vdsl-app: fix -Wundef warnings
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Mathias Kresin > Sent: Dienstag, 16. Februar 2021 19:35 > To: openwrt-devel@lists.openwrt.org > Subject: [PATCH] ltq-vdsl-app: fix -Wundef warnings > > The following warnings are shown during build: > > /usr/include/vdsl/cmv_message_format.h:33:6: warning: > "MEI_SUPPORT_DEBUG_STREAMS" is not defined, evaluates to 0 [-Wundef] > #if (MEI_SUPPORT_DEBUG_STREAMS == 1) > ^ > /usr/include/vdsl/drv_mei_cpe_interface.h:2256:6: warning: > "MEI_SUPPORT_OPTIMIZED_FW_DL" is not defined, evaluates to 0 [- > Wundef] #if (MEI_SUPPORT_OPTIMIZED_FW_DL == 1) > ^~~ > > The headers are provided by the MEI driver, but the defines are never set by > the vdsl app. While the struct with the MEI_SUPPORT_OPTIMIZED_FW_DL > conditional isn't used by the vdsl app, however > CMV_USED_PAYLOAD_8BIT_SIZE which value depends on > MEI_SUPPORT_DEBUG_STREAMS is. > > Since the MEI driver doesn't provide an autogenerated header with compile > flags, the flags are hardcoded for the vdsl app. > > Set them for the MEI driver as well, to indicate a relation to the values used > for the vdsl app and to be not surprised by a changed default in case the MEI > driver gets updated. Use the current default values defined in the MEI > driver. does this need PKG_RELEASE bump or is it really limited to altering compilation parameters? Best Adrian > > Signed-off-by: Mathias Kresin > --- > package/kernel/lantiq/ltq-vdsl-mei/Makefile | 11 ++- > package/network/config/ltq-vdsl-app/Makefile | 16 ++-- > 2 files changed, 24 insertions(+), 3 deletions(-) > > diff --git a/package/kernel/lantiq/ltq-vdsl-mei/Makefile > b/package/kernel/lantiq/ltq-vdsl-mei/Makefile > index 4a305d9c27..a15d0c931c 100644 > --- a/package/kernel/lantiq/ltq-vdsl-mei/Makefile > +++ b/package/kernel/lantiq/ltq-vdsl-mei/Makefile > @@ -54,6 +54,15 @@ endef > MAKE_FLAGS += \ > SHELL="$(BASH)" > > +# ltq-vdsl-app uses a header provided by the MEI driver which has some > +# conditionals. > +# Define the conditionals here to have the same view on both sides. If > +you # change them, you need to change them for the ltq-vdsl-app as well > +MEI_DRV_CFLAGS = \ > + -DMEI_DRV_ATM_PTM_INTERFACE_ENABLE=1 \ > + -DMEI_SUPPORT_DEBUG_STREAMS=1 \ > + -DMEI_SUPPORT_OPTIMIZED_FW_DL=1 > + > CONFIGURE_ARGS += \ > --enable-kernelincl="$(LINUX_DIR)/include" \ > --enable-device=vr9 \ > @@ -63,7 +72,7 @@ CONFIGURE_ARGS += \ > --enable-error_print \ > --enable-ifxos-include="-I$(STAGING_DIR)/usr/include/ifxos/" \ > --enable-ifxos-library="-L$(STAGING_DIR)/usr/lib" \ > - --enable-add_drv_cflags="- > DMEI_DRV_ATM_PTM_INTERFACE_ENABLE=1" \ > + --enable-add_drv_cflags="$(MEI_DRV_CFLAGS)" \ > --enable-linux-26 \ > --enable-kernelbuild="$(LINUX_DIR)" \ > --enable-drv_test_appl=yes \ > diff --git a/package/network/config/ltq-vdsl-app/Makefile > b/package/network/config/ltq-vdsl-app/Makefile > index 0968811984..7665f37514 100644 > --- a/package/network/config/ltq-vdsl-app/Makefile > +++ b/package/network/config/ltq-vdsl-app/Makefile > @@ -36,6 +36,18 @@ define Package/ltq-vdsl-app/description >Userland tool needed to control Lantiq VDSL CPE endef > > +# ltq-vdsl-app uses a header provided by the MEI driver which has some > +# conditionals. > +# > +# Define them here with the default values they would get in the MEI > +driver, # have the same view on both sides. > +# > +# If you change them, you need to change them for the ltq-vdsl-app as > +well VDSL_APP_CFLAGS = \ > + -DMAX_CLI_PIPES=1 \ > + -DMEI_SUPPORT_DEBUG_STREAMS=1 \ > + -DMEI_SUPPORT_OPTIMIZED_FW_DL=1 > + > CONFIGURE_ARGS += \ > --enable-vrx \ > --enable-vrx-device=vr9 \ > @@ -44,10 +56,10 @@ CONFIGURE_ARGS += \ > --enable-ifxos \ > --enable-ifxos-include="-I$(STAGING_DIR)/usr/include/ifxos" \ > --enable-ifxos-library="-I$(STAGING_DIR)/usr/lib" \ > - --enable-add-appl-cflags="-DMAX_CLI_PIPES=1" \ > + --enable-add-appl-cflags="$(VDSL_APP_CFLAGS)" \ > --enable-debug \ > --disable-dti \ > - --with-channels-per-line="1" \ > + --with-channels-per-line="1" > > #CONFIGURE_ARGS += --enable-model=full > #CONFIGURE_ARGS += --enable-model=lite > -- > 2.25.1 > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel openpgp-digital-signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: [PATCH] lantiq: vr9: set the usb led trigger via devicetree
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Mathias Kresin
> Sent: Dienstag, 16. Februar 2021 19:35
> To: openwrt-devel@lists.openwrt.org
> Subject: [PATCH] lantiq: vr9: set the usb led trigger via devicetree
>
> Assign the usbdev trigger via devicetree and drop the userspace handling of
> the usb leds.
Nice.
This should allow to drop the relevant lines from
xrx200/base-files/etc/board.d/01_leds as well.
Best
Adrian
>
> Signed-off-by: Mathias Kresin
> ---
> .../files/arch/mips/boot/dts/lantiq/vr9.dtsi | 14 ++
> .../mips/boot/dts/lantiq/vr9_lantiq_easy80920.dtsi | 12 +++-
> .../mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dtsi | 10 ++
> .../mips/boot/dts/lantiq/vr9_tplink_vr200.dtsi | 7 +++
> .../boot/dts/lantiq/vr9_zyxel_p-2812hnu-f1.dts | 13 ++---
> 5 files changed, 36 insertions(+), 20 deletions(-)
>
> diff --git a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
> b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
> index 60f7f7a4c0..85c584c1f1 100644
> --- a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
> +++ b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
> @@ -409,6 +409,8 @@
> };
>
> usb0: usb@e101000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> status = "disabled";
> compatible = "lantiq,xrx200-usb";
> reg = <0xe101000 0x1000
> @@ -418,9 +420,16 @@
> dr_mode = "host";
> phys = <_phy0>;
> phy-names = "usb2-phy";
> +
> + ehci_port1: port@1 {
> + reg = <1>;
> + #trigger-source-cells = <0>;
> + };
> };
>
> usb1: usb@e106000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> status = "disabled";
> compatible = "lantiq,xrx200-usb";
> reg = <0xe106000 0x1000>;
> @@ -429,6 +438,11 @@
> dr_mode = "host";
> phys = <_phy1>;
> phy-names = "usb2-phy";
> +
> + ehci_port2: port@1 {
> + reg = <1>;
> + #trigger-source-cells = <0>;
> + };
> };
>
> eth0: eth@e108000 {
> diff --git
> a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_easy80920.
> dtsi
> b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_easy80920.
> dtsi
> index f5b0b4f2a1..9cac3e6ec0 100644
> ---
> a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_easy80920.
> dtsi
> +++ b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_eas
> +++ y80920.dtsi
> @@ -15,9 +15,6 @@
> led-failsafe =
> led-running =
> led-upgrade =
> -
> - led-usb = _usb1;
> - led-usb2 = _usb2;
> };
>
> memory@0 {
> @@ -64,13 +61,18 @@
> label = "green:fxo";
> gpios = < 19 GPIO_ACTIVE_HIGH>;
> };
> - led_usb1: usb1 {
> + usb1 {
> label = "green:usb1";
> gpios = < 18 GPIO_ACTIVE_HIGH>;
> + trigger-sources = <_port1>;
> + linux,default-trigger = "usbport";
> };
> - led_usb2: usb2 {
> +
> + usb2 {
> label = "green:usb2";
> gpios = < 15 GPIO_ACTIVE_HIGH>;
> + trigger-sources = <_port2>;
> + linux,default-trigger = "usbport";
> };
> sd {
> label = "green:sd";
> diff --git
> a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dt
> si
> b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dt
> si
> index aa6c308ffe..d33b817f2d 100644
> ---
> a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dt
> si
> +++ b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw
> +++ 89x0.dtsi
> @@ -18,8 +18,6 @@
> led-dsl = _dsl;
> led-internet = _internet;
> led-wifi = _wifi;
> - led-usb = _usb0;
> - led-usb2 = _usb2;
> };
>
> memory@0 {
> @@ -67,14 +65,18 @@
> gpios = < 5 GPIO_ACTIVE_HIGH>;
> };
>
> - led_usb0: usb0 {
> + usb0 {
> label = "green:usb";
> gpios = < 19 GPIO_ACTIVE_HIGH>;
> + trigger-sources = <_port1>;
> +
[PATCH] lantiq: ARV752DPW22: set the usb led trigger via devicetree
Assign the usbdev trigger via devicetree and drop the userspace
handling of the usb leds
Add the PCI attached usb controller as trigger sources for the usb led
as well.
Signed-off-by: Mathias Kresin
---
.../arch/mips/boot/dts/lantiq/danube.dtsi | 7 +
.../lantiq/danube_arcadyan_arv752dpw22.dts| 28 ++-
2 files changed, 34 insertions(+), 1 deletion(-)
diff --git a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube.dtsi
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube.dtsi
index ced3e3bcb4..bb3e9fb188 100644
--- a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube.dtsi
+++ b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube.dtsi
@@ -254,6 +254,8 @@
};
usb: usb@e101000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
compatible = "lantiq,danube-usb";
reg = <0xe101000 0x1000
0xe12 0x3f000>;
@@ -263,6 +265,11 @@
phys = <_phy>;
phy-names = "usb2-phy";
status = "disabled";
+
+ ehci_port1: port@1 {
+ reg = <1>;
+ #trigger-source-cells = <0>;
+ };
};
deu@e103100 {
diff --git
a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube_arcadyan_arv752dpw22.dts
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube_arcadyan_arv752dpw22.dts
index 72483e4749..00ac016a42 100644
---
a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube_arcadyan_arv752dpw22.dts
+++
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/danube_arcadyan_arv752dpw22.dts
@@ -17,7 +17,6 @@
led-upgrade = _red;
led-dsl = _red;
- led-usb =
led-wifi =
};
@@ -78,6 +77,9 @@
umts: umts {
label = "red:umts";
gpios = < 3 GPIO_ACTIVE_LOW>;
+ trigger-sources = <_port1>,
+ <_port2>, <_port2>;
+ linux,default-trigger = "usbport";
};
wifi: wifi {
label = "red:wifi";
@@ -242,6 +244,30 @@
ralink,mtd-eeprom-swap;
mtd-mac-address = < 0x16>;
};
+
+ usb@0f,0 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "pci1106,3038";
+ reg = <0x7800 0 0 0 0>; /* :00:0f.0: UHCI Host Controller */
+
+ uhci_port2: port@2 {
+ reg = <2>;
+ #trigger-source-cells = <0>;
+ };
+ };
+
+ usb@0f,2 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "pci1106,3038";
+ reg = <0x7a00 0 0 0 0>; /* :00:0f.2: EHCI Host Controller*/
+
+ ehci_port2: port@2 {
+ reg = <2>;
+ #trigger-source-cells = <0>;
+ };
+ };
};
_phy {
--
2.25.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] lantiq: vr9: set the usb led trigger via devicetree
Assign the usbdev trigger via devicetree and drop the userspace
handling of the usb leds.
Signed-off-by: Mathias Kresin
---
.../files/arch/mips/boot/dts/lantiq/vr9.dtsi | 14 ++
.../mips/boot/dts/lantiq/vr9_lantiq_easy80920.dtsi | 12 +++-
.../mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dtsi | 10 ++
.../mips/boot/dts/lantiq/vr9_tplink_vr200.dtsi | 7 +++
.../boot/dts/lantiq/vr9_zyxel_p-2812hnu-f1.dts | 13 ++---
5 files changed, 36 insertions(+), 20 deletions(-)
diff --git a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
index 60f7f7a4c0..85c584c1f1 100644
--- a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
+++ b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9.dtsi
@@ -409,6 +409,8 @@
};
usb0: usb@e101000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
status = "disabled";
compatible = "lantiq,xrx200-usb";
reg = <0xe101000 0x1000
@@ -418,9 +420,16 @@
dr_mode = "host";
phys = <_phy0>;
phy-names = "usb2-phy";
+
+ ehci_port1: port@1 {
+ reg = <1>;
+ #trigger-source-cells = <0>;
+ };
};
usb1: usb@e106000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
status = "disabled";
compatible = "lantiq,xrx200-usb";
reg = <0xe106000 0x1000>;
@@ -429,6 +438,11 @@
dr_mode = "host";
phys = <_phy1>;
phy-names = "usb2-phy";
+
+ ehci_port2: port@1 {
+ reg = <1>;
+ #trigger-source-cells = <0>;
+ };
};
eth0: eth@e108000 {
diff --git
a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_easy80920.dtsi
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_easy80920.dtsi
index f5b0b4f2a1..9cac3e6ec0 100644
---
a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_easy80920.dtsi
+++
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_lantiq_easy80920.dtsi
@@ -15,9 +15,6 @@
led-failsafe =
led-running =
led-upgrade =
-
- led-usb = _usb1;
- led-usb2 = _usb2;
};
memory@0 {
@@ -64,13 +61,18 @@
label = "green:fxo";
gpios = < 19 GPIO_ACTIVE_HIGH>;
};
- led_usb1: usb1 {
+ usb1 {
label = "green:usb1";
gpios = < 18 GPIO_ACTIVE_HIGH>;
+ trigger-sources = <_port1>;
+ linux,default-trigger = "usbport";
};
- led_usb2: usb2 {
+
+ usb2 {
label = "green:usb2";
gpios = < 15 GPIO_ACTIVE_HIGH>;
+ trigger-sources = <_port2>;
+ linux,default-trigger = "usbport";
};
sd {
label = "green:sd";
diff --git
a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dtsi
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dtsi
index aa6c308ffe..d33b817f2d 100644
---
a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dtsi
+++
b/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_tdw89x0.dtsi
@@ -18,8 +18,6 @@
led-dsl = _dsl;
led-internet = _internet;
led-wifi = _wifi;
- led-usb = _usb0;
- led-usb2 = _usb2;
};
memory@0 {
@@ -67,14 +65,18 @@
gpios = < 5 GPIO_ACTIVE_HIGH>;
};
- led_usb0: usb0 {
+ usb0 {
label = "green:usb";
gpios = < 19 GPIO_ACTIVE_HIGH>;
+ trigger-sources = <_port1>;
+ linux,default-trigger = "usbport";
};
- led_usb2: usb2 {
+ usb2 {
label = "green:usb2";
gpios = < 20 GPIO_ACTIVE_HIGH>;
+ trigger-sources = <_port2>;
+ linux,default-trigger = "usbport";
};
led_wps: wps {
diff --git
a/target/linux/lantiq/files/arch/mips/boot/dts/lantiq/vr9_tplink_vr200.dtsi
[PATCH] ltq-vdsl-app: fix -Wundef warnings
The following warnings are shown during build: /usr/include/vdsl/cmv_message_format.h:33:6: warning: "MEI_SUPPORT_DEBUG_STREAMS" is not defined, evaluates to 0 [-Wundef] #if (MEI_SUPPORT_DEBUG_STREAMS == 1) ^ /usr/include/vdsl/drv_mei_cpe_interface.h:2256:6: warning: "MEI_SUPPORT_OPTIMIZED_FW_DL" is not defined, evaluates to 0 [-Wundef] #if (MEI_SUPPORT_OPTIMIZED_FW_DL == 1) ^~~ The headers are provided by the MEI driver, but the defines are never set by the vdsl app. While the struct with the MEI_SUPPORT_OPTIMIZED_FW_DL conditional isn't used by the vdsl app, however CMV_USED_PAYLOAD_8BIT_SIZE which value depends on MEI_SUPPORT_DEBUG_STREAMS is. Since the MEI driver doesn't provide an autogenerated header with compile flags, the flags are hardcoded for the vdsl app. Set them for the MEI driver as well, to indicate a relation to the values used for the vdsl app and to be not surprised by a changed default in case the MEI driver gets updated. Use the current default values defined in the MEI driver. Signed-off-by: Mathias Kresin --- package/kernel/lantiq/ltq-vdsl-mei/Makefile | 11 ++- package/network/config/ltq-vdsl-app/Makefile | 16 ++-- 2 files changed, 24 insertions(+), 3 deletions(-) diff --git a/package/kernel/lantiq/ltq-vdsl-mei/Makefile b/package/kernel/lantiq/ltq-vdsl-mei/Makefile index 4a305d9c27..a15d0c931c 100644 --- a/package/kernel/lantiq/ltq-vdsl-mei/Makefile +++ b/package/kernel/lantiq/ltq-vdsl-mei/Makefile @@ -54,6 +54,15 @@ endef MAKE_FLAGS += \ SHELL="$(BASH)" +# ltq-vdsl-app uses a header provided by the MEI driver which has some +# conditionals. +# Define the conditionals here to have the same view on both sides. If you +# change them, you need to change them for the ltq-vdsl-app as well +MEI_DRV_CFLAGS = \ + -DMEI_DRV_ATM_PTM_INTERFACE_ENABLE=1 \ + -DMEI_SUPPORT_DEBUG_STREAMS=1 \ + -DMEI_SUPPORT_OPTIMIZED_FW_DL=1 + CONFIGURE_ARGS += \ --enable-kernelincl="$(LINUX_DIR)/include" \ --enable-device=vr9 \ @@ -63,7 +72,7 @@ CONFIGURE_ARGS += \ --enable-error_print \ --enable-ifxos-include="-I$(STAGING_DIR)/usr/include/ifxos/" \ --enable-ifxos-library="-L$(STAGING_DIR)/usr/lib" \ - --enable-add_drv_cflags="-DMEI_DRV_ATM_PTM_INTERFACE_ENABLE=1" \ + --enable-add_drv_cflags="$(MEI_DRV_CFLAGS)" \ --enable-linux-26 \ --enable-kernelbuild="$(LINUX_DIR)" \ --enable-drv_test_appl=yes \ diff --git a/package/network/config/ltq-vdsl-app/Makefile b/package/network/config/ltq-vdsl-app/Makefile index 0968811984..7665f37514 100644 --- a/package/network/config/ltq-vdsl-app/Makefile +++ b/package/network/config/ltq-vdsl-app/Makefile @@ -36,6 +36,18 @@ define Package/ltq-vdsl-app/description Userland tool needed to control Lantiq VDSL CPE endef +# ltq-vdsl-app uses a header provided by the MEI driver which has some +# conditionals. +# +# Define them here with the default values they would get in the MEI driver, +# have the same view on both sides. +# +# If you change them, you need to change them for the ltq-vdsl-app as well +VDSL_APP_CFLAGS = \ + -DMAX_CLI_PIPES=1 \ + -DMEI_SUPPORT_DEBUG_STREAMS=1 \ + -DMEI_SUPPORT_OPTIMIZED_FW_DL=1 + CONFIGURE_ARGS += \ --enable-vrx \ --enable-vrx-device=vr9 \ @@ -44,10 +56,10 @@ CONFIGURE_ARGS += \ --enable-ifxos \ --enable-ifxos-include="-I$(STAGING_DIR)/usr/include/ifxos" \ --enable-ifxos-library="-I$(STAGING_DIR)/usr/lib" \ - --enable-add-appl-cflags="-DMAX_CLI_PIPES=1" \ + --enable-add-appl-cflags="$(VDSL_APP_CFLAGS)" \ --enable-debug \ --disable-dti \ - --with-channels-per-line="1" \ + --with-channels-per-line="1" #CONFIGURE_ARGS += --enable-model=full #CONFIGURE_ARGS += --enable-model=lite -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] lantiq: ltq-tapi: disable KPI and QOS
The QOS feature depends on KPI2UDP which was removed from the tree with
commit a95775e4b2a9 ("drop unmaintained packages") in 2012.
Since QOS was the last user of the KPI, the feature can be disabled by
default.
Signed-off-by: Mathias Kresin
---
package/kernel/lantiq/ltq-tapi/Config.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/kernel/lantiq/ltq-tapi/Config.in
b/package/kernel/lantiq/ltq-tapi/Config.in
index 84dbef2397..13ca388ad8 100644
--- a/package/kernel/lantiq/ltq-tapi/Config.in
+++ b/package/kernel/lantiq/ltq-tapi/Config.in
@@ -32,7 +32,7 @@ config VOICE_CPE_TAPI_DECT
config VOICE_CPE_TAPI_KPI
bool "KPI (Kernel Packet Interface)"
depends on PACKAGE_kmod-ltq-tapi
- default y
+ default n
help
Option to enable the generic kernel level packet interface
which allows accelerated packet transfer for various purposes.
@@ -43,7 +43,7 @@ config VOICE_CPE_TAPI_KPI
config VOICE_CPE_TAPI_QOS
bool "QOS for accelerated RTP packet handling"
depends on PACKAGE_kmod-ltq-tapi
- default y
+ default n
help
Option to enable an accelerated RTP packet transfer inside
the LINUX kernel space. This option requires the KPI2UDP
--
2.25.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] lantiq: set maximum kernel size
These boards have a fixed size kernel partition but do not limit the kernel size during image building. Disable image building for both boards as well, since the kernel of the last release as well as master are to big to fit into the 2 MByte kernel partition. Signed-off-by: Mathias Kresin --- target/linux/lantiq/image/ar9.mk| 2 ++ target/linux/lantiq/image/danube.mk | 2 ++ 2 files changed, 4 insertions(+) diff --git a/target/linux/lantiq/image/ar9.mk b/target/linux/lantiq/image/ar9.mk index ad061b2776..a973c90beb 100644 --- a/target/linux/lantiq/image/ar9.mk +++ b/target/linux/lantiq/image/ar9.mk @@ -34,6 +34,7 @@ define Device/bt_homehub-v3a DEVICE_VARIANT := Type A BOARD_NAME := BTHOMEHUBV3A SOC := ar9 + KERNEL_SIZE := 2048k DEVICE_PACKAGES := kmod-usb-dwc2 \ kmod-ltq-adsl-ar9-mei kmod-ltq-adsl-ar9 \ kmod-ltq-adsl-ar9-fw-a kmod-ltq-atm-ar9 \ @@ -42,6 +43,7 @@ define Device/bt_homehub-v3a kmod-ath9k kmod-owl-loader wpad-basic-wolfssl \ uboot-envtools SUPPORTED_DEVICES += BTHOMEHUBV3A + DEFAULT := n endef TARGET_DEVICES += bt_homehub-v3a diff --git a/target/linux/lantiq/image/danube.mk b/target/linux/lantiq/image/danube.mk index ea22081d65..73ec27222a 100644 --- a/target/linux/lantiq/image/danube.mk +++ b/target/linux/lantiq/image/danube.mk @@ -188,6 +188,7 @@ define Device/bt_homehub-v2b DEVICE_VARIANT := Type B BOARD_NAME := BTHOMEHUBV2B SOC := danube + KERNEL_SIZE := 2048k DEVICE_PACKAGES := kmod-usb-dwc2 \ kmod-ltq-adsl-danube-mei kmod-ltq-adsl-danube \ kmod-ltq-adsl-danube-fw-a kmod-ltq-atm-danube \ @@ -195,6 +196,7 @@ define Device/bt_homehub-v2b ltq-adsl-app ppp-mod-pppoa \ kmod-ath9k kmod-owl-loader wpad-basic-wolfssl SUPPORTED_DEVICES += BTHOMEHUBV2B + DEFAULT := n endef TARGET_DEVICES += bt_homehub-v2b -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH 21.02] feeds: freifunk: use mirror from openwrt.org
Hi, There is an issue on the freifunk repo exactly about this topic. https://github.com/freifunk/openwrt-packages/issues/37 Greets, Perry On 2/16/21 1:54 PM, Adrian Schmutzler wrote: > Hi, > >> -Original Message- >> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] >> On Behalf Of Petr Štetiar >> Sent: Dienstag, 16. Februar 2021 10:31 >> To: openwrt-devel@lists.openwrt.org >> Cc: Petr Štetiar >> Subject: [PATCH 21.02] feeds: freifunk: use mirror from openwrt.org >> >> We shouldn't rely on GitHub for anything serious for obvious reasons. >> >> References: >> https://github.com/openwrt/openwrt/pull/3701#issuecomment-770841946 >> Signed-off-by: Petr Štetiar >> --- >> >> We've recently got following notice from GitHub: >> >> "If we determine that a violation has occurred, we may need to disable the >> repository" >> >> BTW I find it quite weird, that we're using feed from external project and >> we >> don't have access there. This is for example issue now, where we wanted to >> prepare 21.02 release, but we can't even create branch in that feed >> repository, which is blocking builds[1]: >> >> Updating feed 'freifunk' from 'https://github.com/freifunk/openwrt- >> packages.git;openwrt-21.02' ... >> ... >> fatal: Remote branch openwrt-21.02 not found in upstream origin >> >> 1. http://buildbot.openwrt.org/openwrt- >> 21.02/images/builders/imx6%2Fgeneric/builds/1/steps/updatefeeds/logs/st >> dio > > In the discussion about adding this feed, there was only a very weak tendency > for the addition (I added it to master then): > > https://github.com/openwrt/openwrt/pull/3013 > > If this creates non-trivial problems/holdup or the maintainers are not > interested in moving, I think making the feed optional or removing it again > is the better option. > > Added Sven to the recipients. > > Best > > Adrian > >> >> feeds.conf.default | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/feeds.conf.default b/feeds.conf.default index >> 03bfacb620fd..7aa07a8916c1 100644 >> --- a/feeds.conf.default >> +++ b/feeds.conf.default >> @@ -2,7 +2,7 @@ src-git packages >> https://git.openwrt.org/feed/packages.git >> src-git luci https://git.openwrt.org/project/luci.git >> src-git routing https://git.openwrt.org/feed/routing.git >> src-git telephony https://git.openwrt.org/feed/telephony.git >> -src-git freifunk https://github.com/freifunk/openwrt-packages.git >> +src-git freifunk https://git.openwrt.org/feed/freifunk.git >> #src-git video https://github.com/openwrt/video.git >> #src-git targets https://github.com/openwrt/targets.git >> #src-git management https://github.com/openwrt- >> management/packages.git >> >> ___ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] build: prereq: drop support for Python 3.5
Hi, On 16/02/2021 17:17, Petr Štetiar wrote: Andre Heider [2021-02-16 08:21:08]: Hi, The meson build system bumped their python requirement to 3.6 for the 0.57.0 release. This patch ensures that OpenWrt can update meson while still relying on the host python. Current buildbot images are based on Debian 9, which uses Python 3.5 so merging this would result in broken buildbots. that's unfortunate. Are there plans to update from oldstable to stable? Thanks, Andre ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] build: prereq: drop support for Python 3.5
Andre Heider [2021-02-16 08:21:08]: Hi, > The meson build system bumped their python requirement to 3.6 for the 0.57.0 > release. This patch ensures that OpenWrt can update meson while still > relying on the host python. Current buildbot images are based on Debian 9, which uses Python 3.5 so merging this would result in broken buildbots. Cheers, Petr ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Submitting patches to core services...
Hi Luka, on this list, just prefix the patches with "ustream-ssl:" (or whatever) that way the according developer can find it John On 16.02.21 16:20, Luka Logar wrote: Hi, I've implemented LuCI TLS user certificate authentication (instead of standard user/password). How/where do I submit patches to rpcd, ustream-ssl, uhttpd and luci? Kind regards Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Submitting patches to core services...
Hi, I've implemented LuCI TLS user certificate authentication (instead of standard user/password). How/where do I submit patches to rpcd, ustream-ssl, uhttpd and luci? Kind regards Luka ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: [PATCH 21.02] feeds: freifunk: use mirror from openwrt.org
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Petr Štetiar > Sent: Dienstag, 16. Februar 2021 10:31 > To: openwrt-devel@lists.openwrt.org > Cc: Petr Štetiar > Subject: [PATCH 21.02] feeds: freifunk: use mirror from openwrt.org > > We shouldn't rely on GitHub for anything serious for obvious reasons. > > References: > https://github.com/openwrt/openwrt/pull/3701#issuecomment-770841946 > Signed-off-by: Petr Štetiar > --- > > We've recently got following notice from GitHub: > > "If we determine that a violation has occurred, we may need to disable the > repository" > > BTW I find it quite weird, that we're using feed from external project and we > don't have access there. This is for example issue now, where we wanted to > prepare 21.02 release, but we can't even create branch in that feed > repository, which is blocking builds[1]: > > Updating feed 'freifunk' from 'https://github.com/freifunk/openwrt- > packages.git;openwrt-21.02' ... > ... > fatal: Remote branch openwrt-21.02 not found in upstream origin > > 1. http://buildbot.openwrt.org/openwrt- > 21.02/images/builders/imx6%2Fgeneric/builds/1/steps/updatefeeds/logs/st > dio In the discussion about adding this feed, there was only a very weak tendency for the addition (I added it to master then): https://github.com/openwrt/openwrt/pull/3013 If this creates non-trivial problems/holdup or the maintainers are not interested in moving, I think making the feed optional or removing it again is the better option. Added Sven to the recipients. Best Adrian > > feeds.conf.default | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/feeds.conf.default b/feeds.conf.default index > 03bfacb620fd..7aa07a8916c1 100644 > --- a/feeds.conf.default > +++ b/feeds.conf.default > @@ -2,7 +2,7 @@ src-git packages > https://git.openwrt.org/feed/packages.git > src-git luci https://git.openwrt.org/project/luci.git > src-git routing https://git.openwrt.org/feed/routing.git > src-git telephony https://git.openwrt.org/feed/telephony.git > -src-git freifunk https://github.com/freifunk/openwrt-packages.git > +src-git freifunk https://git.openwrt.org/feed/freifunk.git > #src-git video https://github.com/openwrt/video.git > #src-git targets https://github.com/openwrt/targets.git > #src-git management https://github.com/openwrt- > management/packages.git > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH 21.02] feeds: freifunk: use mirror from openwrt.org
We shouldn't rely on GitHub for anything serious for obvious reasons. References: https://github.com/openwrt/openwrt/pull/3701#issuecomment-770841946 Signed-off-by: Petr Štetiar --- We've recently got following notice from GitHub: "If we determine that a violation has occurred, we may need to disable the repository" BTW I find it quite weird, that we're using feed from external project and we don't have access there. This is for example issue now, where we wanted to prepare 21.02 release, but we can't even create branch in that feed repository, which is blocking builds[1]: Updating feed 'freifunk' from 'https://github.com/freifunk/openwrt-packages.git;openwrt-21.02' ... ... fatal: Remote branch openwrt-21.02 not found in upstream origin 1. http://buildbot.openwrt.org/openwrt-21.02/images/builders/imx6%2Fgeneric/builds/1/steps/updatefeeds/logs/stdio feeds.conf.default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/feeds.conf.default b/feeds.conf.default index 03bfacb620fd..7aa07a8916c1 100644 --- a/feeds.conf.default +++ b/feeds.conf.default @@ -2,7 +2,7 @@ src-git packages https://git.openwrt.org/feed/packages.git src-git luci https://git.openwrt.org/project/luci.git src-git routing https://git.openwrt.org/feed/routing.git src-git telephony https://git.openwrt.org/feed/telephony.git -src-git freifunk https://github.com/freifunk/openwrt-packages.git +src-git freifunk https://git.openwrt.org/feed/freifunk.git #src-git video https://github.com/openwrt/video.git #src-git targets https://github.com/openwrt/targets.git #src-git management https://github.com/openwrt-management/packages.git ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
