> From: linux-wireless-ow...@vger.kernel.org
> [mailto:linux-wireless-ow...@vger.kernel.org] On Behalf Of Baumann,
> Christoph (C.)
> Sent: Wednesday, June 29, 2016 9:45 PM
> To: linux-wireless@vger.kernel.org
> Subject: Re: [PATCH v8] Add new mac80211 driver mwlwifi.
>
> Hello David,
>
> I tried
On 2016年06月30日 01:25, Johannes Berg wrote:
[please don't quote everything to add a single line]
I applied it today, but forgot to say so.
Thanks, and sorry for wrong quotation.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vg
On Mon, Jun 27, 2016 at 12:26 PM, Felix Fietkau wrote:
> On 2016-06-24 14:34, Martin Blumenstingl wrote:
>> Signed-off-by: Martin Blumenstingl
>> ---
>> this is a new patch which didn't exist in v2 yet, it prepares the new
>> function ath_bus_type_to_string which will be used in patch #3
>>
>> d
On Wednesday, June 29, 2016 10:54:38 PM CEST Priit Laes wrote:
> On Wed, 2016-06-29 at 21:33 +0200, Arnd Bergmann wrote:
> > What is the size of this nvram file? As it's board specific, I wonder
> > if we can simply include it inside of the DT verbatim. I remember
> > doing that (in the pre-dtb da
On 29 June 2016 at 21:54, Rafał Miłecki wrote:
> This is the latest patchset needed to get brcmfmac working reasonably well
> with BCM4366.
>
> Both patches were already sent as V2 RFC (10 days ago), there were no more
> comments since then and this is the same code as in V2 RFC. I was mostly
> w
New firmwares (e.g. 10.10.69.36 for BCM4366) support "interface_remove"
for removing interfaces. Try to use this method on cfg80211 request. In
case of older firmwares (e.g. 7.35.177.56 for BCM43602 as I tested) this
will just result in firmware rejecting command and this won't change any
behavior.
So far when receiving event about in-firmware-interface removal our
event worker was notifying listener and afterwards it was removing Linux
interface.
First of all it was resulting in slightly unexpected order. The listener
(del_virtual_intf callback) was (usually) returning with success before
w
On Wed, 2016-06-29 at 21:33 +0200, Arnd Bergmann wrote:
> On Wednesday, June 29, 2016 8:51:44 PM CEST Arend Van Spriel wrote:
> > > Typical wifi devices will have some sort of non volatile storage
> > > on board to not only store the ethernet(mac) address, but also
> > > to contain e.g. info about
On Wednesday, June 29, 2016 8:51:44 PM CEST Arend Van Spriel wrote:
> > Typical wifi devices will have some sort of non volatile storage
> > on board to not only store the ethernet(mac) address, but also
> > to contain e.g. info about the antenna gain so that the firmware
> > and/or the driver can
On 29-6-2016 20:51, Arend Van Spriel wrote:
> On 29-6-2016 20:01, Hans de Goede wrote:
>> Hi,
>>
>> On 29-06-16 19:00, Kalle Valo wrote:
>>> Hans de Goede writes:
>>>
Hi,
On 29-06-16 16:42, Jonas Gorski wrote:
> Hi,
>
> On 29 June 2016 at 16:04, Hans de Goede wrote:
>>>
On 29-6-2016 20:01, Hans de Goede wrote:
> Hi,
>
> On 29-06-16 19:00, Kalle Valo wrote:
>> Hans de Goede writes:
>>
>>> Hi,
>>>
>>> On 29-06-16 16:42, Jonas Gorski wrote:
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
> Add a brcm,nvram_file_name dt property to allow overr
Hi,
On 29-06-16 19:00, Kalle Valo wrote:
Hans de Goede writes:
Hi,
On 29-06-16 16:42, Jonas Gorski wrote:
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
Add a brcm,nvram_file_name dt property to allow overruling the default
nvram filename for sdio devices. The idea is that we can spe
HI,
On 29-06-16 19:01, Kalle Valo wrote:
Hans de Goede writes:
The cubietruck uses an ap6210 sdio wifi module, set brcm,nvram_file_name
to brcmfmac43362-ap6210.txt so that we can ship the ap6210 specific
nvram file in linunx-firmware to get the wifi to work out of the box
without users needin
Hans de Goede writes:
> Hi,
>
> On 29-06-16 16:42, Jonas Gorski wrote:
>> Hi,
>>
>> On 29 June 2016 at 16:04, Hans de Goede wrote:
>>> Add a brcm,nvram_file_name dt property to allow overruling the default
>>> nvram filename for sdio devices. The idea is that we can specify a
>>> board specific
Hans de Goede writes:
> The cubietruck uses an ap6210 sdio wifi module, set brcm,nvram_file_name
> to brcmfmac43362-ap6210.txt so that we can ship the ap6210 specific
> nvram file in linunx-firmware to get the wifi to work out of the box
> without users needing to download and install the nvram f
On Thu, 2016-06-30 at 00:08 +0900, Masashi Honma wrote:
[please don't quote everything to add a single line]
> Is there any comment about this ?
>
I applied it today, but forgot to say so. Sorry about that.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
Guy Mishol wrote:
> Since stations can now be added before association
> (NL80211_FEATURE_FULL_AP_CLIENT_STATE support),
> no supported rates are set when the station is added
> to the fw, resulting in fw recovery.
>
> Fix it by first configuring the AP basic rates as
> the station configured rat
Rafał Miłecki wrote:
> We obviously don't want to fall through in that switch. With this change
> 1) We wait for event (triggered by p2p_disc) as expected
> 2) We remove interface manually on timeout
> 3) We return 0 on success instead of -ENOTSUPP
>
> Signed-off-by: Rafał Miłecki
Thanks, 1 patc
Rafał Miłecki wrote:
> This header provides two inline functions using struct brcmf_if so we
> need core.h to avoid:
>
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.h: In function
> ‘ndev_to_prof’:
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.h:368:13: error:
> deref
Rafał Miłecki wrote:
> This function can work just fine with const pointer, it only calls
> alloc_netdev which take const as well. Moreover it makes this function
> more flexible as some cfg80211 callback may provide const char * as
> well, e.g. add_virtual_intf. This will be needed for more advanc
Rafał Miłecki wrote:
> Removing P2P interface is handled by sending a proper request to the
> firmware. On success firmware triggers an event and driver's handler
> removes a matching interface.
>
> However on event timeout we remove interface directly from the cfg80211
> callback. Current code do
On Wed, Jun 29, 2016 at 1:50 PM, Krishna Chaitanya
wrote:
> On Wed, Jun 29, 2016 at 1:41 PM, Karl Beldan wrote:
>> On Mon, Jun 27, 2016 at 9:53 AM, Chaitanya TK
>> wrote:
>>>
>>> From: Chaitanya T K
>>>
>>> If peer support reception of STBC and LDPC, enable them for better
>>> performance.
>>>
Arnd Bergmann wrote:
> 'register' is a keyword in C and cannot be used in place of a
> variable name, as shown by this -Wextra warning:
>
> drivers/net/wireless/cisco/airo.c:1105:29: error: 'register' is not at
> beginning of declaration [-Werror=old-style-declaration]
>
> This replaces the 're
Amitkumar Karwar wrote:
> From: Ganapathi Bhat
>
> When an association command is sent to firmware but the process is
> killed before the command response arrives, driver will try to
> access bss_desc which is already freed. This issue is fixed by
> checking return value of bss_start.
>
> Signe
Prasun Maiti wrote:
> The two members min_scan_time and max_scan_time of structure
> "mwifiex_ie_types_btcoex_scan_time" are of two bytes each. The values
> are assigned directtly from firmware without endian conversion handling.
> So, wrong datas will get saved in big-endian systems.
>
> This pa
Arnd Bergmann wrote:
> Compiling the rtlwifi drivers for ARM with gcc -Wextra warns about lots of
> incorrect code that results from 'char' being unsigned here, e.g.
>
> realtek/rtlwifi/rc.c:113:18: error: comparison is always true due to limited
> range of data type [-Werror=type-limits]
> real
Bruno Herrera wrote:
> pdev_data pointer is being freed with kfree but the pointer is not dynamic
> allocated.
>
> Signed-off-by: Bruno Herrera
Thanks, 1 patch applied to wireless-drivers-next.git:
6edc119ed3b5 wlcore: sdio: Fix crash on wlcore_probe_of when failing to
parse/map irq
--
Sen
Pavel Andrianov wrote:
> lbs_mac_event_disconnected may free priv->currenttxskb
> while lbs_hard_start_xmit accesses to it.
> The patch adds a spinlock for mutual exclusion.
>
> Tested on OLPC XO-1 (usb8388) and XO-1.5 (sd8686) with v4.7-rc3.
>
> Confirmed that lbs_mac_event_disconnected is bein
Jes Sorensen wrote:
> From: Jes Sorensen
>
> Documentation for enabling USB aggregation and whether to select
> interrupt or bulk delivery of interrupt events.
>
> Signed-off-by: Jes Sorensen
Thanks, 3 patches applied to wireless-drivers-next.git:
e4ac0a8ac8ba rtl8xxxu: Add bit definitions f
Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> A dedicated workqueue has been used since the workitem (viz
> &priv->cmd_work per priv, which maps to lbtf_cmd_work) is involved in
> actual command processing and may be used on a memory reclaim path.
> The
Rafał Miłecki wrote:
> This change reorders some operations in brcmf_setup_ifmodes in hope to
> make it simpler:
> 1) It allocates arrays right before filling them. This way it's easier
>to follow requested array length as it's immediately followed by
>code filling it. It's easier to check
Hello,
testing mwifiex with iperf I ran into an issue with the bandwidth in RX and TX
direction.
If I run iperf as UDP server on the target I can get a throughput of up to 90
MBits/s.
With changed directions I have to limit the bandwidth to 10 MBits/s to keep
things stable.
Above that limit I g
Hello David,
I tried this new driver and it worked for me (board based on Renesas R-Car H3).
But Inoticed that the data rates are asymmetrical (seen from the device):
* iperf -c (mainly TX): 598 Kbits/sec to 2.67 Mbits/sec
* iperf -s (mainly RX): 64.4 Mbits/sec to 69.2 Mbits/sec
Hi,
On 29-06-16 16:42, Jonas Gorski wrote:
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
Add a brcm,nvram_file_name dt property to allow overruling the default
nvram filename for sdio devices. The idea is that we can specify a
board specific nvram file, e.g. brcmfmac43362-ap6210.txt for
On 2016年06月22日 19:55, Masashi Honma wrote:
> Previously, the action frames to group address was not encrypted. But
> [1] "Table 8-38 Category values" indicates "Mesh" and "Multihop" category
> action frames should be encrypted (Group addressed privacy == yes). And the
> encyption key should be MGTK
Hi,
On 29 June 2016 at 16:04, Hans de Goede wrote:
> Add a brcm,nvram_file_name dt property to allow overruling the default
> nvram filename for sdio devices. The idea is that we can specify a
> board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards
> with an ap6210 wifi sdio module
The auxtek t004 uses a toc9002 sdio wifi module, the android nvram file
for this is for an older firmware which does not work with the mainline
kernel driver.
So we set brcm,nvram_file_name to brcmfmac43362-ap6210.txt which
works fine for this wifi module.
Setting brcm,nvram_file_name allows us t
The wits pro uses an ap6476 sdio wifi module, we do not have a nvram file
for this, so set brcm,nvram_file_name to brcmfmac43362-ap6210.txt which
works fine for this wifi module.
Setting brcm,nvram_file_name allows us to ship the ap6210 specific nvram
file in linux-firmware to get the wifi to work
Add a brcm,nvram_file_name dt property to allow overruling the default
nvram filename for sdio devices. The idea is that we can specify a
board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards
with an ap6210 wifi sdio module and ship this in linux-firmware, so
that wifi will work out o
The cubietruck uses an ap6210 sdio wifi module, set brcm,nvram_file_name
to brcmfmac43362-ap6210.txt so that we can ship the ap6210 specific
nvram file in linunx-firmware to get the wifi to work out of the box
without users needing to download and install the nvram file themselves.
Note a downside
From: Johannes Berg
Date: Wed, 29 Jun 2016 12:02:46 +0200
> Sorry to be sending a new pull request, but Felix had just submitted a
> fairly important fix and I decided I should send it on quickly.
>
> Now thus we have two fixes, one for the mesh refcounting issue and one
> for an issue with the
scan_block flag is used to block scan operation when 4 way handshake
is in progress. Sometimes it doesn't get cleared due to incomplete
association. An example is assoc request/response is done, but add key
operation get canceled in some corner cases. As a result, further
association/scan operation
Some lockdep assertions were not fulfilled and
resulted in a kernel warning/call trace if driver
used intermediate software queues (e.g. ath10k).
Existing code sequences should've guranteed safety
but it's always good to be extra careful.
The call trace could look like this:
[ 237.335805] -
Ideally wake_tx_queue should be used regardless as
it is a requirement for reducing bufferbloat and
implementing airtime fairness in the future.
However some setups (typically low-end platforms
hosting QCA988X) suffer performance regressions
with the current wake_tx_queue implementation.
Therefore
Hi Dave,
Sorry to be sending a new pull request, but Felix had just submitted a
fairly important fix and I decided I should send it on quickly.
Now thus we have two fixes, one for the mesh refcounting issue and one
for an issue with the ethertype/length field being too long when it's
used as a le
Hello Michal/ Kalle,
On Tue, Jun 28, 2016 at 08:48:38AM +0200, Michal Kazior wrote:
> On 27 June 2016 at 16:36, Mohammed Shafi Shajakhan
> wrote:
> > Hi Michal,
> >
> > thanks for the review ..
> >
> > On Mon, Jun 27, 2016 at 11:27:27AM +0200, Michal Kazior wrote:
> >> On 23 June 2016 at 18:40, M
> How do you want to proceed? Do you want to
> revert this patch and shall i send another patch?
>
I'll rebase the patch out.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http:
Roman Yeryomin writes:
> On 2 June 2016 at 16:14, Valo, Kalle wrote:
>> Michal Kazior writes:
>>
>>> Some setups suffer performance regressions with
>>> current wake_tx_queue implementation.
>>>
>>> Signed-off-by: Michal Kazior
>>> ---
>>> Hi Roman,
>>>
>>> Can you give this patch a try and se
On Wed, Jun 29, 2016 at 1:52 PM, Krishna Chaitanya
wrote:
> On Wed, Jun 29, 2016 at 1:50 PM, Krishna Chaitanya
> wrote:
>> On Wed, Jun 29, 2016 at 1:41 PM, Karl Beldan wrote:
>>> On Mon, Jun 27, 2016 at 9:53 AM, Chaitanya TK
>>> wrote:
From: Chaitanya T K
If peer support re
The PDU length of incoming LLC frames is set to the total skb payload size
in __ieee80211_data_to_8023() of net/wireless/util.c which incorrectly
includes the length of the IEEE 802.11 header.
The resulting LLC frame header has a too large PDU length, causing the
llc_fixup_skb() function of net/ll
Michal Kazior writes:
> Some lockdep assertions were not fulfilled and
> resulted in a kernel warning/call trace.
>
> Existing code sequences should've guranteed safety
> but it's always good to be extra careful.
>
> The call trace could look like this:
>
> [ 237.335805] [ cut here ]
On Wed, Jun 29, 2016 at 1:50 PM, Krishna Chaitanya
wrote:
> On Wed, Jun 29, 2016 at 1:41 PM, Karl Beldan wrote:
>> On Mon, Jun 27, 2016 at 9:53 AM, Chaitanya TK
>> wrote:
>>>
>>> From: Chaitanya T K
>>>
>>> If peer support reception of STBC and LDPC, enable them for better
>>> performance.
>>>
On Wed, Jun 29, 2016 at 1:41 PM, Karl Beldan wrote:
> On Mon, Jun 27, 2016 at 9:53 AM, Chaitanya TK
> wrote:
>>
>> From: Chaitanya T K
>>
>> If peer support reception of STBC and LDPC, enable them for better
>> performance.
>>
>> Signed-off-by: Chaitanya TK
>> ---
>> include/linux/ieee80211.h
On Mon, Jun 27, 2016 at 9:53 AM, Chaitanya TK wrote:
> From: Chaitanya T K
>
> If peer support reception of STBC and LDPC, enable them for better
> performance.
>
> Signed-off-by: Chaitanya TK
> ---
> include/linux/ieee80211.h |1 +
> net/mac80211/rc80211_minstrel_ht.c | 25 +
On Mon, 2016-06-27 at 15:23 +0530, Chaitanya TK wrote:
> From: Chaitanya T K
>
> If peer support reception of STBC and LDPC, enable them for better
> performance.
>
Applied.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord.
Also - your subject lines should explain the *fix*, not the *bug*
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 2016-06-28 at 14:15 +0300, Yaniv Machani wrote:
> From: Maital Hahn
>
> In the reconfigure process for mesh interface, moved the
> reconfiguration
> of the mesh peers to be done only after restarting the beacons,
> the same as it is done for AP.
>
> Signed-off-by: Maital Hahn
> Acked-by
On Tue, 2016-06-28 at 14:15 +0300, Yaniv Machani wrote:
> From: Meirav Kama
>
> MP received data frames from another MP. Frames are forwarded
> from Rx to Tx to be transmitted to a third MP.
> Upon cloning the skb, the tx_info was zeroed, and the
> hw_queue wasn't set correctly, causing frames to
On Tue, 2016-06-28 at 14:13 +0300, Yaniv Machani wrote:
>
> net/mac80211/mesh.c | 33 -
> net/mac80211/util.c | 3 ---
> net/wireless/mesh.c | 2 +-
That's not a good patch - one change is mac80211 and the other
cfg80211.
> - .ht_opmode = IEEE80211_HT_OP_MOD
On Tue, 2016-06-28 at 14:13 +0300, Yaniv Machani wrote:
> From: Maital Hahn
>
> Some drivers (e.g. wl18xx) expect that the last stage in the
> de-initialization process will be stopping the beacons, similar to
> ap. Update ieee80211_stop_mesh() flow accordingly.
>
How well have you tested that w
Hi Dave,
Another (pretty old) bug showed up, and I have a single fix for it
from Jouni; would be nice to still get it in, but it's in mesh which
seems to mostly have users who integrate everything themselves.
Let me know if there's any problem.
Thanks,
johannes
The following changes since com
61 matches
Mail list logo
