[OpenWrt-Devel] [sdwalker/sdwalker.github.io] 75e9cb: This week's update

2019-08-11 Thread Stephen Walker
Branch: refs/heads/master Home: https://github.com/sdwalker/sdwalker.github.io Commit: 75e9cb4d27fc659d27ccfa6f47f802dd922a0552 https://github.com/sdwalker/sdwalker.github.io/commit/75e9cb4d27fc659d27ccfa6f47f802dd922a0552 Author: Stephen Walker Date: 2019-08-11 (Sun, 11 Aug

[OpenWrt-Devel] [PATCH] lantiq: unify Fritz!Box LED mappings

2019-08-11 Thread David Bauer
This commit unifies the LED mapping of the AVM Fritz!Box routers, which have a combined Power/DSL LED. With the stock firmware, the Power LED has the following characteristics: - Blink when DSL sync is being established - Solid when DSL sync is present We can't completely resemble this

[OpenWrt-Devel] [PATCH] tools/patch: apply upstream patch for cve-2019-13638

2019-08-11 Thread Russell Senior
GNU patch through 2.7.6 is vulnerable to OS shell command injection that can be exploited by opening a crafted patch file that contains an ed style diff payload with shell metacharacters. The ed editor does not need to be present on the vulnerable system. This is different from CVE-2018-1000156.

[OpenWrt-Devel] [PATCH v3 4/5] ath79: add support for Netgear WNR1000 v2

2019-08-11 Thread Michal Cieslakiewicz
This patch adds ath79 support for Netgear WNR1000v2. Router was previously supported by ar71xx target only. Note: this is a 4_32 device with limited upgrade capabilities. Specification = * Description: Netgear WNR1000 v2 * Loader: U-boot * SOC: Atheros AR7240 (340 MHz) * RAM:

[OpenWrt-Devel] [PATCH v3 1/5] ath79: add LAN LEDs control bits for AR724x GPIO function pinmux

2019-08-11 Thread Michal Cieslakiewicz
Currently AR724x pinmux for register 0x18040028 controls only JTAG disable bit. This patch adds new DTS settings to control LAN LEDs and CLKs that allow full software control over these diodes - exactly the same is done by ar71xx target in device setup phase for many routers (WNR2000v3 for

[OpenWrt-Devel] [PATCH v3 2/5] ath79: WNR612v2: improve device support

2019-08-11 Thread Michal Cieslakiewicz
This patch improves ath79 support for Netgear WNR612v2. Router functionality becomes identical to ar71xx version. Changes include: * software control over LAN LEDs via sysfs * correct MAC addresses for network interfaces * correct image size in device definition * formatting adjustments to source

[OpenWrt-Devel] [PATCH v3 5/5] ath79: add support for Netgear WNR2200

2019-08-11 Thread Michal Cieslakiewicz
This patch adds ath79 support for Netgear WNR2200. Router was previously supported by ar71xx target only. Specification = * Description: Netgear WNR2200 * Loader: U-boot * SOC: Atheros AR7241 (360 MHz) * RAM: 64 MiB * Flash: 8 MiB (SPI NOR) - U-boot binary: 256 KiB

[OpenWrt-Devel] [PATCH v3 0/5] ath79: add support for some Netgear WNR routers

2019-08-11 Thread Michal Cieslakiewicz
This patchset enables ath79 target for following Netgear ar724x-based routers currently supported by ar71xx: * Netgear WNR1000v2 (tiny, 4_32) * Netgear WNR2000v3 (tiny, 4_32) * Netgear WNR2200 (generic, 8_64 + USB) and improves existing support for: * Netgear WNR612v2 (tiny, 4_32) For all above

[OpenWrt-Devel] [PATCH v3 3/5] ath79: add support for Netgear WNR2000 v3

2019-08-11 Thread Michal Cieslakiewicz
This patch adds ath79 support for Netgear WNR2000v3. Router was previously supported by ar71xx target only. Note: this is a 4_32 device with limited upgrade capabilities. Specification = * Description: Netgear WNR2000 v3 * Loader: U-boot * SOC: Atheros AR7241 (360 MHz) * RAM:

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

2019-08-11 Thread mail
> -Original Message- > From: Birger Koblitz [mailto:m...@birger-koblitz.de] > Sent: Sonntag, 11. August 2019 22:06 > To: m...@adrianschmutzler.de; 'OpenWrt Development List' de...@lists.openwrt.org> > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: use gpio_hog instead of gpio- > export > >

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

2019-08-11 Thread Birger Koblitz
Hi Adrian, On 11.08.19 21:15, m...@adrianschmutzler.de wrote: >> -Original Message- >> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] >> On Behalf Of Birger Koblitz >> Sent: Sonntag, 11. August 2019 13:11 >> To: m...@adrianschmutzler.de >> Cc: 'OpenWrt Development

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

2019-08-11 Thread Birger Koblitz
Dear Martin and Enrico, thanks for your comments. On 11.08.19 13:38, Martin Blumenstingl wrote: > On Sun, Aug 11, 2019 at 1:00 PM Birger Koblitz wrote: >> I'll go through the patches and remove anything that sounds like it >> might need user space configuration (i.e. not power the USB bus or

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

2019-08-11 Thread mail
> -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Birger Koblitz > Sent: Sonntag, 11. August 2019 13:11 > To: m...@adrianschmutzler.de > Cc: 'OpenWrt Development List' > Subject: Re: [OpenWrt-Devel] [PATCH] ath79: use gpio_hog

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

2019-08-11 Thread Enrico Mioso
Fully agree. And BTW, AT commands may not be a viable option in some cases. We need to be able to manipulate gpios from user space sometime. Thanks, Enrico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices

2019-08-11 Thread Denis 'GNUtoo' Carikli
Hi, I've a device with PowerLine. It's the devolo dLAN pro 500 wireless plus. It has an ath9k compatible WiFi (2.4GHz + 5GHz), and a free software bootloader, which is an old vendor fork of u-boot. The PowerLine part doesn't work out of the box and require a nonfree, non-redistributable

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

2019-08-11 Thread Martin Blumenstingl via openwrt-devel
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 --- On Sun, Aug 11, 2019 at 1:00 PM

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

2019-08-11 Thread Birger Koblitz
Dear Adrian, I'll resubmit a patch taking your comments into account. I am using a script that parses the DTS and I will use more of the original line-name to name the node, i.e. "tp-link:power:usb" -> power-usb "tp-link:reset:sr" -> reset-sr This should also prevent the double naming of the

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

2019-08-11 Thread Birger Koblitz
Dear Mathias and Piotr, thank you for your comments. I had incorrectly assumed that a gpio_hog could still be switched on/off from user space and that the only thing not possible was changing the direction. I'll go through the patches and remove anything that sounds like it might need user space

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

2019-08-11 Thread Piotr Dymacz
Hi Mathias, Birger, On 11.08.2019 11:36, Mathias Kresin wrote: 02/08/2019 11:58, Birger Koblitz: ramips: use gpio_hog instead of gpio-export The `gpio-export` functionality is a hack for missing kernel functionality, which was rejected in upstream kernel long time ago, for details see this

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

2019-08-11 Thread Mathias Kresin
02/08/2019 11:58, Birger Koblitz: ramips: use gpio_hog instead of gpio-export 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

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

2019-08-11 Thread Mathias Kresin
02/08/2019 11:57, Birger Koblitz: lantiq: use gpio_hog instead of gpio-export 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

Re: [OpenWrt-Devel] Review and cleanup of base packages

2019-08-11 Thread Mathias Kresin
Hey Petr, find some comments inline. 10/08/2019 11:58, Petr Štetiar: 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