[OpenWrt-Devel] [PATCH v2] build: add mkrasimage

2018-08-19 Thread David Bauer
The current make-ras.sh image generation script for the ZyXEL NBG6617 has portability issues with bash. Because of this, factory images are currently not built correctly by the OpenWRT buildbots. This commit replaces the make-ras.sh by C-written mkrasimage. The old script is still kept but can be

[OpenWrt-Devel] libtirpc broken Makefile?

2018-08-19 Thread Philip Prindeville
I just ran: % scripts/feeds update -i packages % rm -rf tmp/ % make defconfig oldconfig % grep libtirpc .config % grep "Package: libtirpc” tmp/.packageinfo % ls tmp/info/.packageinfo-feeds_packages_libtirpc ls: cannot access 'tmp/info/.packageinfo-feeds_packages_libtirpc': No such file or

[OpenWrt-Devel] openwrt/packages: [RFC] Proposed flattening of menuconfig menus

2018-08-19 Thread Daniel F. Dickinson
On 2018-08-13 06:19 AM, Karl Palsson wrote: > "Daniel F. Dickinson" wrote: >> Posting on list as I think the discussion should include as >> folks as possible in the discussion. >> >> https://github.com/openwrt/packages/issues/6745 >> >>> Especially when getting started with OpenWrt finding

Re: [OpenWrt-Devel] openwrt/packages: [RFC] Regarding preferences re: switch to codeload

2018-08-19 Thread Daniel F. Dickinson
On 2018-08-19 03:09 PM, Daniel F. Dickinson wrote: > Since it's holiday season I will wait until after first full week of > September to close https://github.com/openwrt/packages/issues/6748 which > discusses this issue. > > I would like to say that impatience (and I'm badly guilty of this too), >

Re: [OpenWrt-Devel] openwrt/packages: [RFC] Proposed flattening of menuconfig menus

2018-08-19 Thread Daniel F. Dickinson
On 2018-08-13 06:19 AM, Karl Palsson wrote: > "Daniel F. Dickinson" wrote: >> Posting on list as I think the discussion should include as >> folks as possible in the discussion. >> >> https://github.com/openwrt/packages/issues/6745 >> >>> Especially when getting started with OpenWrt finding

Re: [OpenWrt-Devel] openwrt/packages: [RFC] Regarding preferences re: switch to codeload

2018-08-19 Thread Daniel F. Dickinson
Since it's holiday season I will wait until after first full week of September to close https://github.com/openwrt/packages/issues/6748 which discusses this issue. I would like to say that impatience (and I'm badly guilty of this too), is a big part of the problem here and with the perceived

Re: [OpenWrt-Devel] [PATCH] ath79: drop SUPPORTED_DEVICES for all TP-LINK routers

2018-08-19 Thread Daniel F. Dickinson
On 2018-08-19 12:30 PM, Mathias Kresin wrote: > 08/19/2018 05:46 PM, Chuanhong Guo: >> Another difference there is that eth0 and eth1 are swapped for chips >> with builtin switch (except ar7240). And I think this one makes it >> really annoying to write a config migration script. > > Indeed, it

Re: [OpenWrt-Devel] [PATCH] ath79: drop SUPPORTED_DEVICES for all TP-LINK routers

2018-08-19 Thread Mathias Kresin
08/19/2018 05:46 PM, Chuanhong Guo: Another difference there is that eth0 and eth1 are swapped for chips with builtin switch (except ar7240). And I think this one makes it really annoying to write a config migration script. Indeed, it will be a pain. Not that I really like the idea, but

Re: [OpenWrt-Devel] [PATCH] ath79: drop SUPPORTED_DEVICES for all TP-LINK routers

2018-08-19 Thread Chuanhong Guo
Another difference there is that eth0 and eth1 are swapped for chips with builtin switch (except ar7240). And I think this one makes it really annoying to write a config migration script. We now have some boards got SUPPORTED_DEVICES from ar71xx and some boards not. I'm confused about whether we

Re: [OpenWrt-Devel] [PATCH] ath79: drop SUPPORTED_DEVICES for all TP-LINK routers

2018-08-19 Thread Dmitry Tunin
вс, 19 авг. 2018 г. в 17:46, Mathias Kresin : > > 2018-08-19 15:47 GMT+02:00 Chuanhong Guo : > > These lines are coming from ar71xx to allow using sysupgrade to > > switch from ar71xx to ath79. But a sysupgrade with config preserved > > won't work since some of the config files are incompatible. >

Re: [OpenWrt-Devel] [PATCH] ath79: drop SUPPORTED_DEVICES for all TP-LINK routers

2018-08-19 Thread Mathias Kresin
2018-08-19 15:47 GMT+02:00 Chuanhong Guo : > These lines are coming from ar71xx to allow using sysupgrade to > switch from ar71xx to ath79. But a sysupgrade with config preserved > won't work since some of the config files are incompatible. To be honest, I don't see that your patch really fixes

Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020

2018-08-19 Thread Mathias Kresin
2018-08-19 14:52 GMT+02:00 Chuanhong Guo : > I've just noticed that Image metadata isn't required on ar71xx so at > least fot TP-LINK devices ar71xx accept factory firmware. Yes it isn't required (enforced) for ar71xx. But if present, the metadata is validated. And all ath9 images should have

[OpenWrt-Devel] [PATCH] ath79: drop SUPPORTED_DEVICES for all TP-LINK routers

2018-08-19 Thread Chuanhong Guo
These lines are coming from ar71xx to allow using sysupgrade to switch from ar71xx to ath79. But a sysupgrade with config preserved won't work since some of the config files are incompatible. This commit removed all SUPPORTED_DEVICES for TP-LINK routers. For those who want to use sysupgrade to

Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020

2018-08-19 Thread Chuanhong Guo
I've just noticed that Image metadata isn't required on ar71xx so at least fot TP-LINK devices ar71xx accept factory firmware. Dmitry Tunin 于2018年8月19日周日 下午7:34写道: > > вс, 19 авг. 2018 г. в 14:29, Dmitry Tunin : > > > > вс, 19 авг. 2018 г. в 12:28, Mathias Kresin : > > > > > > 18.08.2018 14:01,

Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020

2018-08-19 Thread Dmitry Tunin
вс, 19 авг. 2018 г. в 14:29, Dmitry Tunin : > > вс, 19 авг. 2018 г. в 12:28, Mathias Kresin : > > > > 18.08.2018 14:01, David Bauer: > > > Sysupgrading to ath79 from ar71xx currently fails because of mismatching > > > supported_devices. ar71xx is expecting "tl-mr3020" which is missing in > > > the

Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020

2018-08-19 Thread Dmitry Tunin
вс, 19 авг. 2018 г. в 12:28, Mathias Kresin : > > 18.08.2018 14:01, David Bauer: > > Sysupgrading to ath79 from ar71xx currently fails because of mismatching > > supported_devices. ar71xx is expecting "tl-mr3020" which is missing in > > the ath79 image. Upgrading from ath79 is unaffected, as the

Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020

2018-08-19 Thread Karl Palsson
Rosen Penev wrote: > On Sat, Aug 18, 2018 at 5:04 AM David Bauer > wrote: > > > > Sysupgrading to ath79 from ar71xx currently fails because of mismatching > > supported_devices. ar71xx is expecting "tl-mr3020" which is missing in > > the ath79 image. Upgrading from ath79 is unaffected, as the

[OpenWrt-Devel] [PATCH v2] ath79: ag71xx: apply interface mode to MII0/1_CTRL on ar71xx/ar913x

2018-08-19 Thread Chuanhong Guo
We currently don't have any code configuring interface mode in ath79, meaning that we relies on bootloader to set the correct interface mode. This patch added code to set interface correctly so that everything works even if bootloader configures it wrong.(e.g. on WNDR3800 u-boot set the second

Re: [OpenWrt-Devel] [PATCH] ath79: fix SUPPORTED_DEVICES for TL-MR3020

2018-08-19 Thread Mathias Kresin
18.08.2018 14:01, David Bauer: Sysupgrading to ath79 from ar71xx currently fails because of mismatching supported_devices. ar71xx is expecting "tl-mr3020" which is missing in the ath79 image. Upgrading from ath79 is unaffected, as the image contains the old string for ar71xx and the new one

Re: [OpenWrt-Devel] [PATCH v2] ath79: ag71xx: apply interface mode to MII0/1_CTRL on ar71xx/ar913x

2018-08-19 Thread Mathias Kresin
19.08.2018 09:02, Chuanhong Guo: Signed-off-by: Chuanhong Guo Please add a commit message. I'm sure you explained the issue and your fix somewhere. Not sure if I saw it in the forum or somewhere on github. Good commit messages serve at least three important purposes: - To speed up the

[OpenWrt-Devel] [PATCH v2] ath79: ag71xx: apply interface mode to MII0/1_CTRL on ar71xx/ar913x

2018-08-19 Thread Chuanhong Guo
Signed-off-by: Chuanhong Guo --- Changes since that RFC patch: Changed compatible string to ar7100-mii0/1-eth and ar9130-mii0-eth/ar9132-mii1-eth. AR9130 dosen't have a second gmac so I named the second one ar9132-mii1-eth. target/linux/ath79/dts/ar7100.dtsi| 4 +-