Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices
On 11/08/19 02:08, Joan Moreau via openwrt-devel wrote: >The Powerline system needs a "Lan name" in order to synchronize teh devices. >How this is translated in OpenWrt ? RE450 is not a powerline. Only supported device is *https://openwrt.org/toh/hwdata/tp-link/tp-link_tl-wpa8630* and it communicates to the QCA7500 powerline chip with plctool from open-plc-utils package, see the docs for that https://github.com/qca/open-plc-utils/blob/master/plc/plctool.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices
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 --- The Powerline system needs a "Lan name" in order to synchronize teh devices. How this is translated in OpenWrt ? On 2019-08-11 03:47, Lech Perczak wrote: W dniu 2019-08-10 o 16:30, Enrico Mioso pisze: Hello! I guess this is in a case-by-case basis - I have a TP-Link RE450 which is supported. I know there are also Wi-Fi-only devices, but don't think OpenWRt supports any of them. I guess this happens also due to the amount of flash and RAM memory those devices have. And - if you're going for the RE450, keep in mind it's u-boot doesn't seem to have any recovery method, so soldering an UART right away maybe a good option. Enrico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel RE450 is Wifi-only. There is actually one supported: https://openwrt.org/toh/hwdata/tp-link/tp-link_tl-wpa8630 -- Pozdrawiam, Lech Perczak ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel--- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] ath79: convert devices to interrupt-driven gpio-keys
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Dmitry Tunin > Sent: Samstag, 10. August 2019 19:47 > To: Adrian Schmutzler > Cc: OpenWrt Development List > Subject: Re: [OpenWrt-Devel] [PATCH v2] ath79: convert devices to > interrupt-driven gpio-keys > > As I mentioned before with 'gpio-keys' debounce-interval is not needed. In your other e-mail, you said without them it would work better. Now you are telling that they are not needed. In the latter case, I'd remove them. In the former case, it would be a matter of separate testing. Best Adrian 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: [OpenWrt-Devel] [PATCH] ath79: use gpio_hog instead of gpio-export
Hi,
> + usb {
> + gpio-hog;
> + line-name = "tp-link:power:usb";
> + gpios = <6 GPIO_ACTIVE_HIGH>;
> + output-high;
> };
> };
As stated earlier, I would prefer calling those blocks usb-power, usb1-power,
etc..
> diff --git a/target/linux/ath79/dts/qca9531_yuncore_a770.dts
> b/target/linux/ath79/dts/qca9531_yuncore_a770.dts
> index da5b6dc7db..18ad6307a1 100644
> --- a/target/linux/ath79/dts/qca9531_yuncore_a770.dts
> +++ b/target/linux/ath79/dts/qca9531_yuncore_a770.dts
> @@ -8,7 +8,7 @@
>
> / {
> model = "YunCore A770";
> - compatible = "yuncore,a770", "qca,qca9531";
> + compatible = "yuncore,a770", "qca,qca9533";
This should be removed.
> diff --git a/target/linux/ath79/dts/qca9561_tplink_archer-c5x.dtsi
> b/target/linux/ath79/dts/qca9561_tplink_archer-c5x.dtsi
> index 6d32fa3fc4..378c87c9ee 100644
> --- a/target/linux/ath79/dts/qca9561_tplink_archer-c5x.dtsi
> +++ b/target/linux/ath79/dts/qca9561_tplink_archer-c5x.dtsi
> @@ -54,22 +54,23 @@
> gpios = < 21 GPIO_ACTIVE_LOW>;
> };
> };
> +};
>
> - gpio-export {
> - compatible = "gpio-export";
> -
> - gpio_shift_register_oe {
> - gpio-export,name = "tp-link:oe:sr";
> - gpio-export,output = <0>;
> - gpios = < 16 GPIO_ACTIVE_HIGH>;
> - };
> + {
> + status = "okay";
>
> - gpio_shift_register_reset {
> - gpio-export,name = "tp-link:reset:sr";
> - gpio-export,output = <1>;
> - gpios = < 19 GPIO_ACTIVE_HIGH>;
> - };
> + sr {
> + gpio-hog;
> + line-name = "tp-link:oe:sr";
> + gpios = <16 GPIO_ACTIVE_HIGH>;
> + output-low;
> + };
>
> + sr {
> + gpio-hog;
> + line-name = "tp-link:reset:sr";
> + gpios = <19 GPIO_ACTIVE_HIGH>;
> + output-high;
> };
Those two should have different node names.
> diff --git a/target/linux/ath79/dts/qca9563_tplink_archer-c7-v4.dts
> b/target/linux/ath79/dts/qca9563_tplink_archer-c7-v4.dts
> index f4add2fe31..d892d0e960 100644
> --- a/target/linux/ath79/dts/qca9563_tplink_archer-c7-v4.dts
> +++ b/target/linux/ath79/dts/qca9563_tplink_archer-c7-v4.dts
> @@ -41,22 +41,6 @@
> };
> };
>
> - gpio-export {
> - compatible = "gpio-export";
> -
> - gpio_shift_register_oe {
> - gpio-export,name = "tp-link:oe:sr";
> - gpio-export,output = <0>;
> - gpios = < 1 GPIO_ACTIVE_LOW>; // 74HC595 /OE (Output
> Enable)
> - };
> -
> - gpio_shift_register_reset {
> - gpio-export,name = "tp-link:reset:sr";
> - gpio-export,output = <1>;
> - gpios = < 21 GPIO_ACTIVE_LOW>; // 74HC595 /SRCLR (Serial
> Clear)
> - };
> - };
> -
> leds {
> compatible = "gpio-leds";
>
> @@ -148,15 +132,29 @@
>
> };
>
> - {
> + {
> status = "okay";
> +
> + sr {
> + gpio-hog;
> + line-name = "tp-link:oe:sr";
> + gpios = <1 GPIO_ACTIVE_LOW>;
> + output-low;
> + };
> +
> + sr {
> + gpio-hog;
> + line-name = "tp-link:reset:sr";
> + gpios = <21 GPIO_ACTIVE_LOW>;
> + output-high;
> + };
> };
Same here.
Rest looks good, I haven't checked for duplicate definitions (you seem to
have addressed some).
Best
Adrian
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: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices
W dniu 2019-08-10 o 16:30, Enrico Mioso pisze: Hello! I guess this is in a case-by-case basis - I have a TP-Link RE450 which is supported. I know there are also Wi-Fi-only devices, but don't think OpenWRt supports any of them. I guess this happens also due to the amount of flash and RAM memory those devices have. And - if you're going for the RE450, keep in mind it's u-boot doesn't seem to have any recovery method, so soldering an UART right away maybe a good option. Enrico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel RE450 is Wifi-only. There is actually one supported: https://openwrt.org/toh/hwdata/tp-link/tp-link_tl-wpa8630 -- Pozdrawiam, Lech Perczak ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] ath79: convert devices to interrupt-driven gpio-keys
As I mentioned before with 'gpio-keys' debounce-interval is not needed. Default is OK and looks better on ar7161. Maybe testing on other targets is needed. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] ath79: convert devices to interrupt-driven gpio-keys
This converts all remaining devices to use interrupt-driven
gpio-keys compatible instead of gpio-keys-polled.
The poll-interval is removed.
Only ar7240_netgear_wnr612-v2 is kept at gpio-keys-polled, as
this one is using ath9k keys.
Signed-off-by: Adrian Schmutzler
---
Changed in v2:
- Rebased and retained ar7240_netgear_wnr612-v2 at polled keys
---
target/linux/ath79/dts/ar1022_iodata_wn-ag300dgr.dts | 3 +--
target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dts | 3 +--
target/linux/ath79/dts/ar7161_dlink_dir-825-b1.dts | 3 +--
target/linux/ath79/dts/ar7161_jjplus_ja76pf2.dts | 3 +--
target/linux/ath79/dts/ar7161_ubnt_routerstation.dtsi| 3 +--
target/linux/ath79/dts/ar7240_buffalo_whr-g301n.dts | 3 +--
target/linux/ath79/dts/ar7240_tplink_tl-wr74xn-v1.dtsi | 3 +--
target/linux/ath79/dts/ar7241_tplink.dtsi| 3 +--
target/linux/ath79/dts/ar7241_tplink_tl-wr842n-v1.dts| 3 +--
target/linux/ath79/dts/ar7241_ubnt_unifi.dts | 4 ++--
target/linux/ath79/dts/ar7241_ubnt_xm.dtsi | 4 ++--
target/linux/ath79/dts/ar7242_avm_fritz300e.dts | 3 +--
target/linux/ath79/dts/ar7242_buffalo_wzr-bhr.dtsi | 3 +--
target/linux/ath79/dts/ar7242_buffalo_wzr-hp-g302h-a1a0.dts | 3 +--
target/linux/ath79/dts/ar7242_tplink_tl-wr2543-v1.dts| 3 +--
target/linux/ath79/dts/ar9330_glinet_gl-ar150.dts| 3 +--
target/linux/ath79/dts/ar9330_pqi_air-pen.dts| 3 +--
target/linux/ath79/dts/ar9331_embeddedwireless_dorin.dts | 3 +--
target/linux/ath79/dts/ar9331_etactica_eg200.dts | 3 +--
target/linux/ath79/dts/ar9331_pisen_wmm003n.dts | 3 +--
target/linux/ath79/dts/ar9331_tplink_tl-mr3040-v2.dts| 3 +--
target/linux/ath79/dts/ar9331_tplink_tl-wr703n_tl-mr10u.dtsi | 3 +--
target/linux/ath79/dts/ar9331_tplink_tl-wr710n-v1.dts| 3 +--
target/linux/ath79/dts/ar9331_tplink_tl-wr741nd-v4.dtsi | 3 +--
target/linux/ath79/dts/ar9341_pcs_cr3000.dts | 3 +--
target/linux/ath79/dts/ar9341_tplink_tl-wr841-v8.dts | 3 +--
target/linux/ath79/dts/ar9341_tplink_tl-wr842n-v2.dts| 3 +--
target/linux/ath79/dts/ar9342_iodata_etg3-r.dts | 3 +--
target/linux/ath79/dts/ar9344_comfast_cf-e120a-v3.dts| 3 +--
target/linux/ath79/dts/ar9344_ocedo_raccoon.dts | 3 +--
target/linux/ath79/dts/ar9344_pcs_cap324.dts | 3 +--
target/linux/ath79/dts/ar9344_pcs_cr5000.dts | 3 +--
target/linux/ath79/dts/ar9344_tplink_tl-wdr4300.dtsi | 3 +--
target/linux/ath79/dts/ar9344_winchannel_wb2000.dts | 3 +--
target/linux/ath79/dts/qca9531_comfast_cf-e5.dts | 3 +--
target/linux/ath79/dts/qca9531_engenius_ews511ap.dts | 3 +--
target/linux/ath79/dts/qca9531_glinet_gl-ar300m.dtsi | 4 ++--
target/linux/ath79/dts/qca9531_glinet_gl-x750.dts| 3 +--
target/linux/ath79/dts/qca9533_comfast_cf-e110n-v2.dts | 3 +--
target/linux/ath79/dts/qca9533_tplink_cpe210.dtsi| 3 +--
target/linux/ath79/dts/qca9557_buffalo_bhr-4grv2.dts | 3 +--
target/linux/ath79/dts/qca9557_iodata_wn-ac-dgr.dtsi | 3 +--
target/linux/ath79/dts/qca9558_engenius_epg5000.dts | 3 +--
target/linux/ath79/dts/qca9558_ocedo_koala.dts | 3 +--
target/linux/ath79/dts/qca9558_openmesh_om5p-ac-v2.dts | 3 +--
target/linux/ath79/dts/qca9561_avm_fritz4020.dts | 3 +--
target/linux/ath79/dts/qca9561_tplink_archer-c5x.dtsi| 3 +--
target/linux/ath79/dts/qca9561_xiaomi_mi-router-4q.dts | 3 +--
target/linux/ath79/dts/qca9563_dlink_dir-859-a1.dts | 3 +--
target/linux/ath79/dts/qca9563_glinet_gl-ar750s.dts | 4 ++--
target/linux/ath79/dts/qca9563_phicomm_k2t.dts | 3 +--
51 files changed, 55 insertions(+), 102 deletions(-)
diff --git a/target/linux/ath79/dts/ar1022_iodata_wn-ag300dgr.dts
b/target/linux/ath79/dts/ar1022_iodata_wn-ag300dgr.dts
index 5ad8196a15..64f471649e 100644
--- a/target/linux/ath79/dts/ar1022_iodata_wn-ag300dgr.dts
+++ b/target/linux/ath79/dts/ar1022_iodata_wn-ag300dgr.dts
@@ -55,8 +55,7 @@
};
keys {
- compatible = "gpio-keys-polled";
- poll-interval = <20>;
+ compatible = "gpio-keys";
eco {
label = "eco";
diff --git a/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dts
b/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dts
index df22eb8dc4..f51bc0f771 100644
--- a/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dts
+++ b/target/linux/ath79/dts/ar7161_buffalo_wzr-hp-ag300h.dts
@@ -81,8 +81,7 @@
};
keys {
- compatible = "gpio-keys-polled";
- poll-interval = <20>;
+ compatible = "gpio-keys";
reset {
Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys
> So should it remove the change for ath9k keys and only do the other ones at > the moment? That's a good question. I suggest to leave devices that HAVE some keys attached to ath9k keys using 'gpio-keys-polled'. It makes no sense to use both drivers. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Dmitry Tunin > Sent: Samstag, 10. August 2019 18:25 > To: Adrian Schmutzler > Cc: OpenWrt Development List > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt- > driven gpio-keys > > > Can I add your Tested-by? > > I tested only one target, it makes no sense to add this. And I what about > ath9k keys. They are a problem. So should it remove the change for ath9k keys and only do the other ones at the moment? 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: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys
If you will be pushing it some way, remove debounce-interval too. Without it gpio-keys work better. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys
> Can I add your Tested-by? I tested only one target, it makes no sense to add this. And I what about ath9k keys. They are a problem. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Dmitry Tunin > Sent: Samstag, 10. August 2019 11:53 > To: Adrian Schmutzler > Cc: OpenWrt Development List > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt- > driven gpio-keys > > I tested gpio-keys on dir825b1 and didn't see a noticable change against gpio- > keys-polled. Both miss events and work poorly. > So no objections for a switch. Can I add your Tested-by? > > пн, 5 авг. 2019 г. в 19:27, Dmitry Tunin : > > > > > This recent Pull Request used gpio-keys on ar7100: > > > https://github.com/openwrt/openwrt/pull/1359 > > > > > > However, I cannot extract how well this was tested. > > > > I will have a device for testing around the next weekend. I'll report back. > > ___ > 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: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices
Hello! I guess this is in a case-by-case basis - I have a TP-Link RE450 which is supported. I know there are also Wi-Fi-only devices, but don't think OpenWRt supports any of them. I guess this happens also due to the amount of flash and RAM memory those devices have. And - if you're going for the RE450, keep in mind it's u-boot doesn't seem to have any recovery method, so soldering an UART right away maybe a good option. Enrico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Has OpenWrt suport for Powerline devices
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 --- like TPLink AV2000 or other (with or without Wifi) ?--- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] treewide: sync bootcount scripts across targets
This commit made the following changes to sync all bootcount scripts:
1. use boot() instead of start()
This script only needs to be executed once when boot is complete.
use boot() to make this explicit.
2. drop sourcing of /lib/functions.sh
This is aready done in /etc/rc.common.
3. ramips: replace board name checking with a case
Signed-off-by: Chuanhong Guo
---
target/linux/ath79/base-files/etc/init.d/bootcount| 1 +
target/linux/ipq40xx/base-files/etc/init.d/bootcount | 4 +---
target/linux/ipq806x/base-files/etc/init.d/bootcount | 4 +---
target/linux/kirkwood/base-files/etc/init.d/bootcount | 4 +---
target/linux/mvebu/base-files/etc/init.d/bootcount| 4 +---
target/linux/ramips/base-files/etc/init.d/bootcount | 11 +--
6 files changed, 10 insertions(+), 18 deletions(-)
diff --git a/target/linux/ath79/base-files/etc/init.d/bootcount
b/target/linux/ath79/base-files/etc/init.d/bootcount
index b71fbf9a69..c734fd9d33 100755
--- a/target/linux/ath79/base-files/etc/init.d/bootcount
+++ b/target/linux/ath79/base-files/etc/init.d/bootcount
@@ -1,4 +1,5 @@
#!/bin/sh /etc/rc.common
+
START=99
boot() {
diff --git a/target/linux/ipq40xx/base-files/etc/init.d/bootcount
b/target/linux/ipq40xx/base-files/etc/init.d/bootcount
index f2d76f125f..b9d625e296 100755
--- a/target/linux/ipq40xx/base-files/etc/init.d/bootcount
+++ b/target/linux/ipq40xx/base-files/etc/init.d/bootcount
@@ -2,9 +2,7 @@
START=99
-start() {
- . /lib/functions.sh
-
+boot() {
case $(board_name) in
alfa-network,ap120c-ac)
[ -n "$(fw_printenv bootcount changed 2>/dev/null)" ] &&\
diff --git a/target/linux/ipq806x/base-files/etc/init.d/bootcount
b/target/linux/ipq806x/base-files/etc/init.d/bootcount
index 6a5a6d52ad..d0bf708e66 100755
--- a/target/linux/ipq806x/base-files/etc/init.d/bootcount
+++ b/target/linux/ipq806x/base-files/etc/init.d/bootcount
@@ -2,9 +2,7 @@
START=99
-start() {
- . /lib/functions.sh
-
+boot() {
case $(board_name) in
linksys,ea8500)
mtd resetbc s_env || true
diff --git a/target/linux/kirkwood/base-files/etc/init.d/bootcount
b/target/linux/kirkwood/base-files/etc/init.d/bootcount
index 20fb3a425c..478f3d0134 100755
--- a/target/linux/kirkwood/base-files/etc/init.d/bootcount
+++ b/target/linux/kirkwood/base-files/etc/init.d/bootcount
@@ -2,9 +2,7 @@
START=99
-start() {
- . /lib/functions.sh
-
+boot() {
case $(board_name) in
linksys,audi|\
linksys,viper)
diff --git a/target/linux/mvebu/base-files/etc/init.d/bootcount
b/target/linux/mvebu/base-files/etc/init.d/bootcount
index 6e8e310849..dd2266bdc8 100755
--- a/target/linux/mvebu/base-files/etc/init.d/bootcount
+++ b/target/linux/mvebu/base-files/etc/init.d/bootcount
@@ -2,9 +2,7 @@
START=99
-start() {
- . /lib/functions.sh
-
+boot() {
case $(board_name) in
linksys,caiman |\
linksys,cobra |\
diff --git a/target/linux/ramips/base-files/etc/init.d/bootcount
b/target/linux/ramips/base-files/etc/init.d/bootcount
index 60b93f72b3..807801a34f 100755
--- a/target/linux/ramips/base-files/etc/init.d/bootcount
+++ b/target/linux/ramips/base-files/etc/init.d/bootcount
@@ -2,11 +2,10 @@
START=99
-start() {
- . /lib/functions.sh
-
- local board=$(board_name)
- if [ $board = "samknows,whitebox-v8" ]; then
+boot() {
+ case $(board_name) in
+ samknows,whitebox-v8)
fw_setenv bootcount 0
- fi
+ ;;
+ esac
}
--
2.21.0
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [14445.624549] ath10k_pci 0000:00:00.0: peer-unmap-event: unknown peer id 0
Hello all, This is the message I receive everytime I bring down Wi-Fi on my Archer C60 V2. root@C60:/# [14445.574213] device wlan1 left promiscuous mode [14445.579042] br-lan: port 2(wlan1) entered disabled state [14445.588397] device wlan0 left promiscuous mode [14445.593107] br-lan: port 3(wlan0) entered disabled state [14445.617585] ath10k_pci :00:00.0: peer-unmap-event: unknown peer id 0 [14445.624549] ath10k_pci :00:00.0: peer-unmap-event: unknown peer id 0 There are no issues, wanted just to let this know... bootlog attached. root@C60:/# cat /etc/openwrt_release DISTRIB_ID='OpenWrt' DISTRIB_RELEASE='SNAPSHOT' DISTRIB_REVISION='r10564-fc2df4f705' DISTRIB_TARGET='ath79/generic' DISTRIB_ARCH='mips_24kc' DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r10564-fc2df4f705' DISTRIB_TAINTS='' root@C60:/# Thanks! Enrico U-Boot 1.1.4 (Dec 6 2016 - 14:40:45) ap151 - Dragonfly 1.0 DRAM: 64 MB Top of RAM usable for U-Boot at: 8400 Reserving 402k for U-Boot at: 83f98000 Reserving 32832k for malloc() at: 81f88000 Reserving 44 Bytes for Board Info at: 81f87fd4 Reserving 36 Bytes for Global Data at: 81f87fb0 Reserving 128k for boot params() at: 81f67fb0 Stack Pointer at: 81f67f98 Now running in RAM - U-Boot at: 83f98000 Flash Manuf Id 0xc8, DeviceId0 0x40, DeviceId1 0x17 flash size 8MB, sector count = 128 Flash: 8 MB Using default environment In:serial Out: serial Err: serial Net: ath_gmac_enet_initialize... No valid address in Flash. Using fixed address No valid address in Flash. Using fixed address ath_gmac_enet_initialize: reset mask:c02200 Dragonfly> S27 PHY * : cfg1 0x8000 cfg2 0x7114 eth0: 00:03:7f:09:0b:ad athrs27_phy_setup ATHR_PHY_CONTROL 4 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :10 eth0 up ATHRS27: resetting s27 ATHRS27: s27 reset done : cfg1 0x800c cfg2 0x7214 eth1: 00:03:7f:09:0b:ad athrs27_phy_setup ATHR_PHY_CONTROL 0 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :50 athrs27_phy_setup ATHR_PHY_CONTROL 1 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :50 athrs27_phy_setup ATHR_PHY_CONTROL 2 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :50 athrs27_phy_setup ATHR_PHY_CONTROL 3 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :50 eth1 up eth0, eth1 Setting 0x181162c0 to 0x82 Reading Partition Table from NVRAM ... OK Parsing Partition Table ... OK factory boot check integer ok. load fs uboot at 0x1. Autobooting in 1 seconds ## Starting application at 0x8001 ... U-Boot 1.1.4 (Dec 6 2016 - 14:40:35) ap151 - Dragonfly 1.0 DRAM: 64 MB Top of RAM usable for U-Boot at: 8400 Reserving 120k for U-Boot at: 83fe Reserving 32832k for malloc() at: 81fd Reserving 44 Bytes for Board Info at: 81fcffd4 Reserving 36 Bytes for Global Data at: 81fcffb0 Reserving 128k for boot params() at: 81faffb0 Stack Pointer at: 81faff98 Now running in RAM - U-Boot at: 83fe Flash Manuf Id 0xc8, DeviceId0 0x40, DeviceId1 0x17 flash size 8MB, sector count = 128 Flash: 8 MB Using default environment In:serial Out: serial Err: serial Net: ath_gmac_enet_initialize... No valid address in Flash. Using fixed address No valid address in Flash. Using fixed address ath_gmac_enet_initialize: reset mask:c02200 Dragonfly> S27 PHY * : cfg1 0x8000 cfg2 0x7114 eth0: 00:03:7f:09:0b:ad athrs27_phy_setup ATHR_PHY_CONTROL 4 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :10 eth0 up ATHRS27: resetting s27 ATHRS27: s27 reset done : cfg1 0x800c cfg2 0x7214 eth1: 00:03:7f:09:0b:ad athrs27_phy_setup ATHR_PHY_CONTROL 0 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :10 athrs27_phy_setup ATHR_PHY_CONTROL 1 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :10 athrs27_phy_setup ATHR_PHY_CONTROL 2 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :10 athrs27_phy_setup ATHR_PHY_CONTROL 3 :1000 athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :10 eth1 up eth0, eth1 Setting 0x181162c0 to 0x82 Autobooting in 1 seconds ## Booting image at 9f03 ... Image Name: MIPS OpenWrt Linux-4.19.57 Created: 2019-07-21 21:30:27 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size:1888015 Bytes = 1.8 MB Load Address: 8006 Entry Point: 8006 Verifying Checksum at 0x9f030040 ...OK Uncompressing Kernel Image ... OK No initrd ## Transferring control to Linux (at address 8006) ... ## Giving linux memsize in bytes, 67108864 Starting kernel ... [0.00] Linux version 4.19.57 (builder@buildhost) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r10564-fc2df4f705)) #0 Sun Jul 21 21:30:27 2019 [0.00] bootconsole [early0] enabled [0.00] CPU0 revision is: 00019750 (MIPS 74Kc) [0.00] MIPS: machine is TP-Link Archer C60 v2 [0.00] SoC: Qualcomm Atheros QCA956X ver 1 rev 0 [0.00] Determined physical RAM map: [0.00] memory: 0400 @ (usable) [0.00] Initrd not found or empty - disabling initrd [0.00] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [0.00] Primary
[OpenWrt-Devel] Review and cleanup of base packages
Hi, one of the topics discussed during recent Hamburg meeting was "Review base packages"[1], where we simply talked about: * lack of formal definition for a base package * transfer of base packages which don't fit formal definition into feeds So, how can we define which package should be included in the base/master tree? (Any idea where to put this on the wiki?) * package is needed by device in order to - build the image and flashing tools - boot device into usable state * package is convenient for development (gdb, perf, strace, valgrind etc.) - couldn't one just symlink/install those packages from feeds? * it's convenient for testing (ct-bugcheck, fbtest, spidev_test, iperf3 etc.) - couldn't one just symlink/install those packages from feeds? * package is needed for automatic testing - couldn't one just symlink/install those packages from feeds? * it's not possible to build the package and/or tooling out of the tree For the initial discussion, I've simply created a list of packages which are not used by any target, so probably possible candidates for transfer into the feeds: boot/kexec-tools devel/gdb devel/perf devel/strace devel/trace-cmd devel/valgrind firmware/am33x-cm3 firmware/amd64-microcode kernel/avila-wdt kernel/gpio-nct5104d kernel/leds-apu2/src kernel/rtc-rv5c386a kernel/rtl8812au-ct kernel/trelay kernel/w1-gpio-custom libs/libbsd (lldpd) libs/libconfig libs/libevent2(lldpd) libs/libnetfilter-cthelper libs/libnetfilter-cttimeout libs/libnetfilter-log libs/libnetfilter-queue libs/libroxml libs/libusb-compat libs/nghttp2 (curl) libs/popt network/config/ltq-vdsl-app network/config/qos-scripts network/config/vti network/config/vxlan network/config/xfrm network/ipv6/464xlat network/ipv6/6in4 network/ipv6/6rd network/ipv6/6to4 network/ipv6/ds-lite network/ipv6/map network/ipv6/thc-ipv6 network/services/igmpproxy network/services/ipset-dns network/services/lldpd network/services/omcproxy network/services/openvpn-easy-rsa network/services/openvpn network/services/relayd network/services/samba36 network/services/umdns network/services/wireguard network/utils/curl network/utils/dante network/utils/iftop network/utils/iperf3 network/utils/iperf network/utils/iproute2 network/utils/ipset network/utils/iputils network/utils/iwcap network/utils/owipcalc network/utils/tcpdump network/utils/umbim network/utils/wpan-tools system/rpcd system/zram-swap utils/ct-bugcheck utils/fbtest utils/fritz-tools utils/fuse utils/lua5.3 utils/px5g utils/spidev_test utils/ugps utils/usbmode utils/usbreset utils/usbutils utils/xfsprogs 1. https://openwrt.org/meetings/hamburg2019/start#review_base_packages -- ynezz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ath79: convert devices to interrupt-driven gpio-keys
I tested gpio-keys on dir825b1 and didn't see a noticable change against gpio-keys-polled. Both miss events and work poorly. So no objections for a switch. пн, 5 авг. 2019 г. в 19:27, Dmitry Tunin : > > > This recent Pull Request used gpio-keys on ar7100: > > https://github.com/openwrt/openwrt/pull/1359 > > > > However, I cannot extract how well this was tested. > > I will have a device for testing around the next weekend. I'll report back. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
