[LEDE-DEV] [PATCH] ath9k: Add airtime fairness scheduler

2016-11-25 Thread Toke Høiland-Jørgensen
This adds a patch that introduces airtime fairness scheduling to ath9k, which can significantly improve network efficiency in mixed-rate environments. Signed-off-by: Toke Høiland-Jørgensen --- ...h9k-Introduce-airtime-fairness-scheduling.patch | 695 + 1 file changed, 695 ins

Re: [LEDE-DEV] [RFC] target: armvirt: new target

2016-11-25 Thread Yousong Zhou
On 25 November 2016 at 00:52, Felix Fietkau wrote: > On 2016-11-24 17:03, Yousong Zhou wrote: >> An ARM Cortex-A machine provided by QEMU. >> >> Kernel drivers enabled: >> >> - pl011, uart >> - pl031, rtc >> - pl061, gpio >> - pci-host-generic >> - virtio_{mmio,pci,net,blk,scsi,console,balloo

Re: [LEDE-DEV] [RFC] target: armvirt: new target

2016-11-25 Thread Yousong Zhou
On 25 November 2016 at 01:29, Christian Lamparter wrote: > Hello, > > On Friday, November 25, 2016 12:03:54 AM CET Yousong Zhou wrote: >> An ARM Cortex-A machine provided by QEMU. >> >> Kernel drivers enabled: >> >> - pl011, uart >> - pl031, rtc >> - pl061, gpio >> - pci-host-generic >> - vir

Re: [LEDE-DEV] [RFC] target: armvirt: new target

2016-11-25 Thread Christian Lamparter
On Saturday, November 26, 2016 12:43:38 AM CET Yousong Zhou wrote: > On 25 November 2016 at 01:29, Christian Lamparter > wrote: > > Hello, > > > > On Friday, November 25, 2016 12:03:54 AM CET Yousong Zhou wrote: > >> An ARM Cortex-A machine provided by QEMU. > >> > >> Kernel drivers enabled: > >>

[LEDE-DEV] [PATCH] mediatek: enable support for vfpv4 and neon

2016-11-25 Thread Christian Lamparter
While researching for the armvirt target, I looked at the existing arm platforms. It turns out that the mediatek target with its sole MT7623N/A chip is sold as a "highly integrated multimedia network router system-on-chip". To that end, it lists support for the "NEON multimedia processing engine wi

Re: [LEDE-DEV] Apology; Communication

2016-11-25 Thread Hartmut Knaack
Hi Daniel. Daniel Dickinson schrieb am 25.11.2016 um 01:26: > > To be clear, I think what I mean by lack of communication is that the > community doesn't see: > > 1) The planned technical directions for the project, including > a) Currently prioritized issues and plans to resolve them >

[LEDE-DEV] [PATCH v2 2/6] lantiq: specify the PCIe controller's interrupt, size and address cells

2016-11-25 Thread Martin Blumenstingl
This allows adding devices to the PCIe controller in the .dts files. Signed-off-by: Martin Blumenstingl --- target/linux/lantiq/dts/vr9.dtsi | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/target/linux/lantiq/dts/vr9.dtsi b/target/linux/lantiq/dts/vr9.dtsi index

[LEDE-DEV] [PATCH v2 1/6] lantiq: Register the device tree node with the PCIe controller

2016-11-25 Thread Martin Blumenstingl
This allows specifying PCI devices as children of the PCIe controller node to pass configuration data to them. Signed-off-by: Martin Blumenstingl --- .../lantiq/patches-4.4/0151-lantiq-ifxmips_pcie-use-of.patch | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/targ

[LEDE-DEV] [PATCH v2 5/6] kernel: mac80211: disable ath9k bands via device tree

2016-11-25 Thread Martin Blumenstingl
These properties allow overriding the settings from the EEPROM which indicate whether a band is enabled or not. Setting this property is only needed when the RF circuit does not support the 2.4GHz or 5GHz band while it is enabled nevertheless in the EEPROM. These patches will be replaced with a fu

[LEDE-DEV] [PATCH v2 6/6] lantiq: use ath9k device tree bindings binding/owl-loader

2016-11-25 Thread Martin Blumenstingl
This moves the extraction of the eeprom/calibration data to a hotplug firmware script. Additionally it modifies all .dts to configure ath9k directly from within the .dts. The owl-loader approach enables support on devices with exotic eeprom data locations (such as unaligned positions on the flash

[LEDE-DEV] [PATCH v2 4/6] kernel: mac80211: add pending ath9k EEPROM swapping patches

2016-11-25 Thread Martin Blumenstingl
There are two types of swapping the EEPROM data in the ath9k driver. Before this series one type of swapping could not be used without the other. The first type of swapping looks at the "magic bytes" at the start of the EEPROM data and performs swab16 on the EEPROM contents if needed. The second t

[LEDE-DEV] [PATCH v2 0/6] lantiq: use devicetree to configure ath9k

2016-11-25 Thread Martin Blumenstingl
This series uses devicetree to configure the devices with ath9k wifi chips. The first two patches are preparing PCIe for OF support (PCI devices are already configured via devicetree properly, so we don't have to do anything here). The third patch backports the ath9k devicetree bindings to our mac

[LEDE-DEV] [PATCH v2 3/6] kernel: mac80211: backport ath9k device tree support patches

2016-11-25 Thread Martin Blumenstingl
These patches add support for configuring ath9k based devices via devicetree. This was tested on PCI(e) based devices. This should work for AHB based devices as well (adding more AHB specific properties may still be needed) as soon as the ath79 platform is ready to populate the ath9k wmac via devic

Re: [LEDE-DEV] [RFC] target: armvirt: new target

2016-11-25 Thread Yousong Zhou
On 26/11/2016, Christian Lamparter wrote: > On Saturday, November 26, 2016 12:43:38 AM CET Yousong Zhou wrote: >> On 25 November 2016 at 01:29, Christian Lamparter >> wrote: >> > Hello, >> > >> > On Friday, November 25, 2016 12:03:54 AM CET Yousong Zhou wrote: >> >> An ARM Cortex-A machine provid

Re: [LEDE-DEV] Apology; Communication

2016-11-25 Thread Daniel Dickinson
On Fri, 25 Nov 2016 21:27:50 +0100 Hartmut Knaack wrote: > Hi Daniel. > > Daniel Dickinson schrieb am 25.11.2016 um 01:26: > > > > To be clear, I think what I mean by lack of communication is that > > the community doesn't see: > > > > 1) The planned technical directions for the project, inclu