[OpenWrt-Devel] [PATCH] gitignore: ignore patches in OpenWrt root directory

2019-11-05 Thread Adrian Schmutzler
This will have GIT ignore patches in root directory, as created when using "git format-patch". Signed-off-by: Adrian Schmutzler --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 84e1a9d6d1..6549af83be 100644 --- a/.gitignore +++ b/.gitignore @@ -16,

Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615 rev. E4

2019-11-05 Thread Adrian Schmutzler
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On > Behalf Of Paul Fertser > Sent: Montag, 4. November 2019 22:20 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: add D-Link DIR-615

[OpenWrt-Devel] Broken WiFi on QCA9533 rev. 2

2019-11-05 Thread Adrian Schmutzler
Hi, for quite some time already we are struggling with broken WiFi on some TP-Link CPE devices having QCA9533 rev. 2 (QCA9533-BL3A SOC) in common. I'd be happy on some help here, since I've exhausted my debugging capabilities. 1. Symptoms: WiFi looks up on the device, some TX traffic is shown

[OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Adrian Schmutzler
From: Birger Koblitz The gpio-export functionality is a hack for missing kernel functionality, which was rejected in upstream kernel long time ago, for details see this email http://lists.infradead.org/pipermail/openwrt-devel/2019-February/015772.html, discussion in PR#1366 or https://github.com/

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Birger Koblitz
Thanks Adrian for taking this up again! Birger On 5 November 2019 16:12:02 CET, Adrian Schmutzler wrote: >From: Birger Koblitz > >The gpio-export functionality is a hack for missing kernel >functionality, which was rejected in upstream kernel long time ago, >for details see this email >http://

Re: [OpenWrt-Devel] Broken WiFi on QCA9533 rev. 2

2019-11-05 Thread David Bauer
Hello Adrian, during the CPE210v2 bringup it was discovered that the CPE210 has the wrong bootstrap option set for it's 25 MHz reference clock. Because of this, the device was originally not even booting with ar71xx. On ath79, the reference clock is not detected based on the bootstrap option,

Re: [OpenWrt-Devel] Broken WiFi on QCA9533 rev. 2

2019-11-05 Thread Adrian Schmutzler
Hi David, thanks for your response. To me it looks like qca953x already uses 25 MHz clock, or am I looking at the wrong value: https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/dts/qca953x.dtsi#L27 Best Adrian On 5 November 2019 16:46:59 CET, David Bauer wrote: >Hello Adri

Re: [OpenWrt-Devel] Broken WiFi on QCA9533 rev. 2

2019-11-05 Thread David Bauer
Hello Adrian, On 11/5/19 5:14 PM, Adrian Schmutzler wrote: > Hi David, > > thanks for your response. > > To me it looks like qca953x already uses 25 MHz clock, or am I looking at the > wrong value: Yes, however ath9k does not use this value but tries to determine the reference clock based on

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Bjørn Mork
Adrian Schmutzler writes: > This patch converts all DTS files with settings that normally do > not need user interaction, e.g. power for external USB ports, to > gpio_hog. Wouldn't it be better to map these as fixed regulators? Then you could eventually link them to the connected ports/controll

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Adrian Schmutzler
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On > Behalf Of Bjørn Mork > Sent: Dienstag, 5. November 2019 17:38 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org; Birger Koblitz > Subject: Re: [OpenWrt-Devel] [PATCH v2] ath79

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Bjørn Mork
"Adrian Schmutzler" writes: > But, based on the discussion here, the opposite has been identified as > superior solution (discussing nand subtarget): > https://github.com/openwrt/openwrt/pull/2184#discussion_r342136635 That's missing the point. Regulators are superior if there is controlling dri

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Adrian Schmutzler
Hi, > -Original Message- > From: Bjørn Mork [mailto:bj...@mork.no] > Sent: Dienstag, 5. November 2019 20:01 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org; 'Birger Koblitz' > Subject: Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio- > export > > "Adrian

[OpenWrt-Devel] ipq40xx: Bogus IMAGE_SIZE on asus rt-ac58u

2019-11-05 Thread Adrian Schmutzler
Hi, as stated already in the comment of an earlier patch, the asus_rt-ac58u on ipq40xx target has an IMAGE_SIZE of 20439364, which cannot be divided by 1024 and also does not seem to match anything in DTS. I couldn't identify what should be the correct value in this case, so maybe someone more

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Bjørn Mork
"Adrian Schmutzler" writes: > So, for the moment I think the gpio-hog is an improvement over gpio-export. Agreed 100% Bjørn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread mail
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Adrian Schmutzler > Sent: Dienstag, 5. November 2019 16:12 > To: openwrt-devel@lists.openwrt.org > Cc: Birger Koblitz > Subject: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog in

Re: [OpenWrt-Devel] Broken WiFi on QCA9533 rev. 2

2019-11-05 Thread David Bauer
Hello Adrian, I've prepared the attached patch, can you check if the situation improved with it? Best wishes David On 11/5/19 5:20 PM, David Bauer wrote: > Hello Adrian, > > On 11/5/19 5:14 PM, Adrian Schmutzler wrote: >> Hi David, >> >> thanks for your response. >> >> To me it looks like qca9

Re: [OpenWrt-Devel] Broken WiFi on QCA9533 rev. 2

2019-11-05 Thread mail
Hi David, I've just tested with the dump approach: diff --git a/package/kernel/mac80211/patches/ath/552-ahb_of.patch b/package/kernel/mac80211/patches/ath/552-ahb_of.patch index 1170fc64bd..57647e16fd 100644 --- a/package/kernel/mac80211/patches/ath/552-ahb_of.patch +++ b/package/kernel/mac80211

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Enrico Mioso
BTW, being able to toggle on and off USB power is essential in some cases. Can this be done with hog? Thanks! E > Il giorno 5 nov 2019, alle ore 17:44, Adrian Schmutzler > ha scritto: > > Hi, > >> -Original Message- >> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwr

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread mail
Hi, > -Original Message- > From: Enrico Mioso [mailto:mrkiko...@gmail.com] > Sent: Dienstag, 5. November 2019 23:07 > To: Adrian Schmutzler > Cc: Bjørn Mork ; openwrt-devel@lists.openwrt.org; Birger > Koblitz > Subject: Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of > gpio

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Piotr Dymacz
Hi Adrian, On 05.11.2019 22:19, m...@adrianschmutzler.de wrote: Hi, -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Adrian Schmutzler Sent: Dienstag, 5. November 2019 16:12 To: openwrt-devel@lists.openwrt.org Cc: Birger Koblitz Subj

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Enrico Mioso
Hello Adrian, and all. thank you for your work, again. So, the TP-Link TL-MR6400 uses USB power for this. But in general, where there is a port and you can plug a {3,4}G Gadget, the need of "resetting" the device via USB power removal arises. I know I am being pedantic here, and I am sorry for

Re: [OpenWrt-Devel] Broken WiFi on QCA9533 rev. 2

2019-11-05 Thread mail
Hi David, your patch is resolving the situation at the CPE210V2. I successfully performed an internet speed test while connected to the CPE by WiFi (and the CPE connected to the internet by eth0). (I also successfully tested on 1043ND v4 (qca9563) to stupidly check whether there is impact on o

[OpenWrt-Devel] [PATCH] fstools: Add support to read-only MTD partitions (eg. for recovery images)

2019-11-05 Thread brunompena
From: Bruno Pena Signed-off-by: Bruno Pena --- libfstools/mtd.c | 20 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/libfstools/mtd.c b/libfstools/mtd.c index 77c71ee..56dd1a9 100644 --- a/libfstools/mtd.c +++ b/libfstools/mtd.c @@ -36,20 +36,32 @@ struct mt

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread mail
Hi, TL;DR: 1. We should find an agreement that can be used coherently at least for new device support submissions. 2. Everyone (and particular committers) feel invited to add your view. > > I've just had a look at the openmesh_om5p-ac-v2, and it seems as if the > gpio-exports there are just volt

[OpenWrt-Devel] [PATCH] build: image: fix build breakage of some images

2019-11-05 Thread Petr Štetiar
Commit 881ed09ee6e2 ("build: create JSON files containing image info") has removed the crucial empty new line from the image copy step resulting in the following errors during make function expansion: GZ_SUFFIX := bash: GZ_SUFFIX: command not found Makefile:86: recipe for target 'openwrt-ath79

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Jeff Kletsky
On 11/5/19 11:01 AM, Bjørn Mork wrote: "Adrian Schmutzler" writes: But, based on the discussion here, the opposite has been identified as superior solution (discussing nand subtarget): https://github.com/openwrt/openwrt/pull/2184#discussion_r342136635 That's missing the point. Regulators are

Re: [OpenWrt-Devel] [PATCH] build: image: fix build breakage of some images

2019-11-05 Thread Paul Spooren
Thanks for debugging this! On 11/5/19 1:23 PM, Petr Štetiar wrote: Commit 881ed09ee6e2 ("build: create JSON files containing image info") has removed the crucial empty new line from the image copy step resulting in the following errors during make function expansion: GZ_SUFFIX := bash: GZ_S

[OpenWrt-Devel] [PATCH] ramips, mt7520: reproducible elecom-header uid/gid

2019-11-05 Thread Paul Spooren
The elecom-header renames the firmware image to v_0.0.0.bin, stores its MD5 sum as v_0.0.0.md5 and tars both files again. Both v_0.0.0 files are created as the build user making it harder to reproduce. This commit sets the owner/group of both files to root by adding extra options to the final tar

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Piotr Dymacz
Hi Adrian, On 06.11.2019 00:14, m...@adrianschmutzler.de wrote: Hi, TL;DR: 1. We should find an agreement that can be used coherently at least for new device support submissions. I believe the major issue here is that there is no 'in place' replacement for 'gpio-export' (or I'm just not awa

[OpenWrt-Devel] [PATCH] Revert "mt76: probe load mt7615 driver asynchronously"

2019-11-05 Thread DENG Qingfang
This reverts commit 81764319637f408623ed9f4bae3f0d149b010f07. After said commit, users report that MT7615 no longer works on boot and have to manually enable WiFi (via command "wifi") to make it work Fixes FS#2546 Signed-off-by: DENG Qingfang --- package/kernel/mt76/Makefile | 1 - 1 file chan

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Bjørn Mork
writes: > I'm not really convinced that resetting an USB device by toggling its > power really is a feature, and not just a workaround for a faulty USB > device. A workaround for a faulty USB device *is* a feature :-) This feature is very important to at least one group of users, as Enrico p

Re: [OpenWrt-Devel] [PATCH v2] ath79: use gpio_hog instead of gpio-export

2019-11-05 Thread Bjørn Mork
writes: > Well, normally I'd say to lower the TX power you would use the > user-space txpower setting and not change voltages of an amplifier. This choice will affect S/N. You'll probably limit the usable txpower range this way. Please use the features of the hardware. Don't hide them. Sure,