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

2019-10-16 Thread mail
Hi, > +define Device/netgear_wnr2200-8m > + $(Device/netgear_wnr2200_common) > + DEVICE_VARIANT := 8M > + IMAGE_SIZE := 7808k > + IMAGES += factory-NA.img > + IMAGE/factory-NA.img := $$(IMAGE/default) | netgear-dni NA | \ > + check-size (IMAGE_SIZE) > + SUPPORTED_DEVICES +=

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

2019-10-16 Thread mail
Hi, > { > @@ -116,6 +123,8 @@ > ath9k: wifi@0,0 { > compatible = "pci168c,002b"; > reg = <0x 0 0 0 0>; > + mtd-mac-address = < 0x0>; > + mtd-mac-address-increment = <1>; Sorry if I ask again, but I do not remember whether I asked

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

2019-10-16 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 v5 3/5] ath79: add support for Netgear WNR2000 v3

2019-10-16 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:

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

2019-10-16 Thread Michal Cieslakiewicz
This patch adds ath79 support for Netgear WNR2200. Router was previously supported by ar71xx target only (8 MiB variant). Netgear WNR2200 has two flash versions - 8MiB sold in EU, US etc. and 16 MiB for Russia and China markets. Apart from flash size both variants share the same hardware

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

2019-10-16 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 * dts: 'keys' renamed to

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

2019-10-16 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 and 16_64, USB) and improves existing support for: * Netgear WNR612v2 (tiny, 4_32) For

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

2019-10-16 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:

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

2019-10-16 Thread Jo-Philipp Wich
Hi, > Silly question, does 18.6 have the same issue or is this a regression in > relation to 18.6? I believe it is a regression but I am not 100% sure yet. ~ Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

2019-10-16 Thread Sebastian Moeller
> On Oct 16, 2019, at 21:54, Jo-Philipp Wich wrote: > > Hi, > >> Does it impact OpenWrt ? or just some OpenWrt based distributions ? >> (might influence who need to fix this ;) ) > > it impacts the usage of the kmod compatibility repositories - apparently > they're completely ignored by

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

2019-10-16 Thread Jo-Philipp Wich
Hi, > Does it impact OpenWrt ? or just some OpenWrt based distributions ? > (might influence who need to fix this ;) ) it impacts the usage of the kmod compatibility repositories - apparently they're completely ignored by opkg. This problem was reported in the forum by a user who was unable to

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

2019-10-16 Thread Etienne Champetier
Hi Jo, Le mer. 16 oct. 2019 à 12:15, Jo-Philipp Wich a écrit : > > Hi, > > another blocker: > > opkg fails to select the correct provider package in case multiple > repositories provide the same kmod with different versions and only one > of the provider satisfied version dependency constraints.

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

2019-10-16 Thread Jo-Philipp Wich
Hi, another blocker: opkg fails to select the correct provider package in case multiple repositories provide the same kmod with different versions and only one of the provider satisfied version dependency constraints. Someone needs to debug and fix this. ~ Jo signature.asc Description:

[OpenWrt-Devel] libstdcpp size

2019-10-16 Thread Rosen Penev
With each new version of OpenWrt, the size of libstdcpp keeps increasing: ar71xx target: 247.5 KB - 15.05 365.0 KB - 17.01 371.6 KB - 18.04 The configure file for libstdcpp lists a dual ABI option that is enabled by default. Maybe this is the reason for the huge jump in size? Unfortunately, I

Re: [OpenWrt-Devel] [PATCH 1/8] ncurses: add cygwin compatibility

2019-10-16 Thread Rosen Penev
On Tue, Oct 15, 2019 at 1:12 AM Paul Oranje wrote: > > > > > Op 8 okt. 2019, om 14:57 heeft Alberto Bursi > > het volgende geschreven: > > ... > > Yeah it seems these patches are for using the build system with cygwin. I > > think there should be more explanation on why you want that. > > Dear

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

2019-10-16 Thread Daniel Golle
Hi, On Mon, Oct 14, 2019 at 11:11:34AM +0200, Alberto Bursi wrote: > > On 11/10/19 12:59, Jo-Philipp Wich wrote: > > Hi Bjørn, > > > > > Or: Start discussing the release blockers here and now. Thanks. > > 1) Blocker: LuCI master needs to be backported to 19.07 > > Time estimate: 2-3 weeks > >

[OpenWrt-Devel] Joining the SFC

2019-10-16 Thread John Crispin
Hi, the OpenWrt project has, after months of deliberation, decided to leave the SPI and intents to join the Software Freedom Conservancy as future fiscal sponsor. Prior to contacting the SFC and SPI we had a discussion among the contributors which started during the Hamburg meeting. We