[LEDE-DEV] GPIO-JTAG: Compex WPQ864:

2017-08-26 Thread Neeraj Sallh
Hello, My immediate need is to figure out if some pins on a Compex WPQ864 are free to be used as GPIO pins. Compex guys have said that JTAG pins can be used. Can someone in this community guide me regarding this? 1. I have read the documentation files from the code base, like GPIO.txt, gpio-legacy

Re: [LEDE-DEV] IPv6 link locals, vlans and bridging

2017-08-26 Thread Kevin Darbyshire-Bryant
On 25/08/17 14:54, Baptiste Jonglez wrote: On 25-08-17, Kevin Darbyshire-Bryant wrote: Are you sure it's related to your complex bridging setup? Maybe dnsmasq just fails to answer on link-local IPv6 addresses in all cases? This was already reported before: https://bugs.lede-project.org/in

Re: [LEDE-DEV] [PATCH] brcm63xx: Add Sercomm AD1018 support

2017-08-26 Thread Jonas Gorski
Hi, On 20 August 2017 at 17:32, Daniel Gonzalez Cabanelas wrote: > Add support for the Sercomm AD1018 router > > This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash, > with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB > host port (not soldered). > > Since NAND flash chips aren't st

Re: [LEDE-DEV] [PATCH] sdk: automatically use all CPU cores for xz

2017-08-26 Thread Jonas Gorski
On 18 August 2017 at 15:06, Karl Palsson wrote: > > Bjørn Mork wrote: >> This looks yucky. Experimenting a bit, I see that the result >> with >> >> a) -T 0 depends on multi-core vs single-core >> b) -T 1 is always different from the output of -T x where x > 1 >> c) -T x where x > 1 is indepen

Re: [LEDE-DEV] Transmit timeouts with mtk_eth_soc and MT7621

2017-08-26 Thread Kristian Evensen
Hi, On Sat, Aug 26, 2017 at 7:43 AM, Mingyu Li wrote: > Hi. > > i check the code again. found xmit_more can cause tx timeout. you can > reference this. > https://www.mail-archive.com/netdev@vger.kernel.org/msg123334.html > so the patch should be like this. edit mtk_eth_soc.c > > tx_num =

Re: [LEDE-DEV] [PATCH] brcm63xx: Add Sercomm AD1018 support

2017-08-26 Thread Daniel
2017-08-26 12:26 GMT+02:00 Jonas Gorski : > Hi, >> +}; >> + >> +&leds { >> + status = "ok"; >> + >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_led0 &pinctrl_led1 &pinctrl_serial_led >> +&pinctrl_ephy0_spd_led &pinctrl_ephy1_act_led >> +

[LEDE-DEV] [PATCH] scripts/dowload.pl: use glob to expand target dir

2017-08-26 Thread Zoltan Gyarmati
If CONFIG_DOWNLOAD_FOLDER is set to for example "~/dl", the download script fails to create the .hash and .dl files with the following errors: Cannot create file ~/dl/dropbear-2017.75.tar.bz2.dl: No such file or directory sh: 1: cannot create ~/dl/dropbear-2017.75.tar.bz2.hash: Directory nonexist

Re: [LEDE-DEV] Transmit timeouts with mtk_eth_soc and MT7621

2017-08-26 Thread Kristian Evensen
Hello again, On Sat, Aug 26, 2017 at 12:38 PM, Kristian Evensen wrote: > Hi, > > On Sat, Aug 26, 2017 at 7:43 AM, Mingyu Li wrote: >> Hi. >> >> i check the code again. found xmit_more can cause tx timeout. you can >> reference this. >> https://www.mail-archive.com/netdev@vger.kernel.org/msg12333

Re: [LEDE-DEV] Transmit timeouts with mtk_eth_soc and MT7621

2017-08-26 Thread Kristian Evensen
Hi, On Sat, Aug 26, 2017 at 4:47 PM, Kristian Evensen wrote: > I guess our common theory is that something is causing TX interrupts > not to be enabled again. After reading up on NAPI > (https://wiki.linuxfoundation.org/networking/napi), it seems that the > recommended way of using NAPI on clear-

[LEDE-DEV] [PATCH 2/4] ramips/RT5350F-OLINUXINO(-EVB) dts: invert WiFi LED polarity

2017-08-26 Thread Zoltan Gyarmati
The polarity of WLAN_ACT LED on the base module needs to inverted in order to be 'on' when the WiFi interface is active Signed-off-by: Zoltan Gyarmati --- target/linux/ramips/dts/RT5350F-OLINUXINO.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/ramips/dts/RT5350F-OLINUXINO.

[LEDE-DEV] [PATCH 0/4] ramips/RT5350F-OLINUXINO(-EVB) improve device tree support

2017-08-26 Thread Zoltan Gyarmati
This patchset aims to improve the device tree support for the RT5350F-OLINUXINO(-EVB) boards. Some of the changes are coming from the HW vendor's own OpenWrt fork at https://github.com/OLIMEX/openwrt which is rather outdated by now, so i've synced/rebased the patches and tested them. Zoltan Gyarm

[LEDE-DEV] [PATCH 1/4] ramips/RT5350F-OLINUXINO(-EVB) dts: introduce RT5350F-OLINUXINO.dtsi

2017-08-26 Thread Zoltan Gyarmati
The RT5350F-OLINUXINO(-EVB).dts files' content are nearly the same, so to avoid code duplication this patch creates RT5350F-OLINUXINO.dtsi file which covers the base board's features. The corresponding RT5350F-OLINUXINO.dts just includes the new .dtsi and the RT5350F-OLINUXINO-EVB.dts adds the EVB

[LEDE-DEV] [PATCH 4/4] ramips/RT5350F-OLINUXINO(-EVB) dts: enable ttyS1

2017-08-26 Thread Zoltan Gyarmati
The RT5350F's second UART pins are available on the base module and on the EVB as well, so enable it in the device tree. Additionaly, the uartlite@c00 and uart@500 nodes swapped in rt5350.dtsi to keep the serial console as ttyS0. Signed-off-by: Zoltan Gyarmati --- target/linux/ramips/dts/RT535

[LEDE-DEV] [PATCH 3/4] ramips/RT5350F-OLINUXINO(-EVB) dts: enable i2c

2017-08-26 Thread Zoltan Gyarmati
The RT5350F i2c pins is available on the base module and on the EVB as well, so enable it in the dts. Signed-off-by: Zoltan Gyarmati --- target/linux/ramips/dts/RT5350F-OLINUXINO.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/target/linux/ramips/dts/RT5350F-OLINUXINO.dtsi b/target

Re: [LEDE-DEV] [PATCH lede-17.01 1/4] x86/generic: use HIGHMEM64G instead of HIGHMEM4G to fix PAE and Xen

2017-08-26 Thread Baptiste Jonglez
Hi, On 25-07-17, Sven Roederer wrote: > On Samstag, 15. Juli 2017 22:57:53 CEST Baptiste Jonglez wrote: > > From: Baptiste Jonglez > > > > This is a backport of 641a65fd062987a456216cc4fa91ff2910528261 in master. > > > > This change re-enables PAE for the 32-bit x86 subtarget, which is > > inte