From: Kalle Valo
Date: Thu, 29 Sep 2016 19:57:28 +0300
> this should be the last wireless-drivers-next pull request for 4.9, from
> now on only important bugfixes. Nothing really special stands out,
> iwlwifi being most active but other drivers also getting attention. More
On Thursday 29 September 2016, Felix Fietkau wrote:
> On 2016-09-08 12:54, Kalle Valo wrote:
> > Felix Fietkau writes:
> >
> >> Signed-off-by: Felix Fietkau
> >> ---
> >> .../bindings/net/wireless/mediatek,mt76.txt| 26
> >> ++
> >> 1
On 27 September 2016 at 11:24, Arend Van Spriel
wrote:
> On 26-9-2016 14:38, Rafał Miłecki wrote:
>> On 26 September 2016 at 14:13, Rafał Miłecki wrote:
>>> On 26 September 2016 at 13:46, Arend Van Spriel
>>> wrote:
From: Jes Sorensen
A device running without RX package aggregation could return more data
in the USB packet than the actual network packet. In this case the
could would clone the skb but then determine that that there was no
packet to handle and exit without freeing the
From: Jes Sorensen
The full RX descriptor is converted so converting tsfl again would
return it to it's original endian value.
Signed-off-by: Jes Sorensen
---
drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.h | 4 ++--
On 2016-09-08 12:54, Kalle Valo wrote:
> Felix Fietkau writes:
>
>> Signed-off-by: Felix Fietkau
>> ---
>> .../bindings/net/wireless/mediatek,mt76.txt| 26
>> ++
>> 1 file changed, 26 insertions(+)
>> create mode 100644
>>
On Thu, Sep 29, 2016 at 07:57:28PM +0300, Kalle Valo wrote:
> Hi Dave,
>
> this should be the last wireless-drivers-next pull request for 4.9, from
> now on only important bugfixes. Nothing really special stands out,
> iwlwifi being most active but other drivers also getting attention. More
>
Hi Dave,
this should be the last wireless-drivers-next pull request for 4.9, from
now on only important bugfixes. Nothing really special stands out,
iwlwifi being most active but other drivers also getting attention. More
details in the signed tag. Please let me know if there are any problems.
[+brian]
On Thu, Sep 29, 2016 at 9:39 AM, Amitkumar Karwar wrote:
> From: Xinming Hu
>
> This patch derives device tree node from pcie bus layer framework.
> Device tree bindings file has been renamed(marvell-sd8xxx.txt ->
> marvell-8xxx.txt) to accomodate
From: Xinming Hu
This patch derives device tree node from pcie bus layer framework.
Device tree bindings file has been renamed(marvell-sd8xxx.txt ->
marvell-8xxx.txt) to accomodate PCIe changes.
Signed-off-by: Xinming Hu
Signed-off-by: Amitkumar Karwar
Try refer the following for latest mesh setup using ath10k:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/mesh
---
Chun-Yeow
From: Wei Yongjun
Add the missing destroy_workqueue() before return from
mwifiex_add_virtual_intf() in the error handling case.
Signed-off-by: Wei Yongjun
---
drivers/net/wireless/marvell/mwifiex/cfg80211.c | 2 ++
1 file changed, 2
stock ath10k firmware does not report tx-rate so the kernel always sees 6Mbps.
I don't know about the splat..maybe post the function
that is causing that?
/home/matteo/linux-imx6/backports4.4.2-i2CAT/net/mac80211/util.c:2621
Thanks,
Ben
On 09/29/2016 06:39 AM, Matteo Grandi wrote:
Hello all,
From: Xinming Hu
This patch derives device tree node from pcie bus layer framework.
Device tree bindings file has been renamed(marvell-sd8xxx.txt ->
marvell-8xxx.txt) to accomodate PCIe changes.
Signed-off-by: Xinming Hu
Signed-off-by: Amitkumar Karwar
Hi Rob,
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Tuesday, September 20, 2016 2:58 AM
> To: Amitkumar Karwar
> Cc: linux-wireless@vger.kernel.org; Cathy Luo; Nishant Sarmukadam;
> devicet...@vger.kernel.org; Wei-Ning Huang; Xinming Hu
> Subject: Re: [PATCH] mwifiex: parse device tree
Kalle Valo writes:
>> was it intentional not to CC the linux-wireless list?
>
> No, that was a bug in my script. Thanks for noticing it! Please always
> report back if my script does something strange.
The bug is now fixed, it was just a matter of a loop being in wrong
Hello all,
I'm struggling with a problem related on ath10k drivers:
I'm using a Compex WLE600V5-27 (802.11ac) miniPCIe card for some HT
tests needed for my thesis.
I'm using ath10k drivers for this card, and backports-4.4.2, in
particular the firmware-5.bin_10.2.4.70.54 because it seem to be the
From: Xinming Hu
This patch derives device tree node from pcie bus layer framework.
Device tree bindings file has been renamed(marvell-sd8xxx.txt ->
marvell-8xxx.txt) to accomodate PCIe changes.
Signed-off-by: Xinming Hu
Signed-off-by: Amitkumar Karwar
Hello,
The program of Linux netdev 1.2 is now online !
http://netdevconf.org/1.2/schedule.html
As we stated, all of registered people is now in the mailing
list, people at netdevconf.org. If you wish to communicate
with the attendees of netdev 1.2, feel free to exchange
messages.
-- Hajime
On Tue, Sep 27, 2016 at 12:03 PM, Gucea Doru wrote:
> What is the decision triggering the exit from the PS mode immediately
> after the ping request? I am asking this because 802.11 PS legacy
> specifies that the client should wait for a beacon with TIM set in
> order to
> This clarifies the issue, thanks. Basically the reason is history -
> this user space code has been around for a while. It turns out the
> HCI BT driver doesn't exist as it should. If it did, then the
> regulator could be tied to the driver. Now I see what's missing.
So like what Marcel wrote
21 matches
Mail list logo