Since we had some discussions concerning multicast and wireless
regarding "multicast-to-unicast" just recently, maybe this draft
is of interest to some people here, too.
Regards, Linus
- Forwarded message from "Alvaro Retana (aretana)" -
Date: Fri, 31 Mar 2017
From: Tamizh chelvam
This patch introduces NL80211_CMD_SET_BTCOEX command and
NL80211_ATTR_BTCOEX_OP attribute to enable or disable btcoex.
And this change enables user to set btcoex priority by using
NL80211_ATTR_BTCOEX_PRIORITY attribute for the driver which
has the
From: Tamizh chelvam
This patch introduces a new driver call back drv_set_btcoex.
This API will pass user space value to driver to
enable or disabe btcoex and set or modify the btcoex priority value.
Signed-off-by: Tamizh chelvam
---
From: Tamizh chelvam
This patchset add support for BTCOEX feature to enable/disable and
modifying btcoex priority value via nl80211
Tamizh chelvam (2):
cfg80211: Add support to enable or disable btcoex and set
btcoex_priority
mac80211: Add support to enable or
This fixes following WARNing:
usb 3-2.4.1: NFC: Exchanging data failed (error 0x13)
llcp: nfc_llcp_recv: err -5
llcp: nfc_llcp_symm_timer: SYMM timeout
[ cut here ]
WARNING: CPU: 1 PID: 26397 at .../drivers/usb/core/hcd.c:1584
usb_hcd_map_urb_for_dma+0x370/0x550
transfer
Older firmware loading method is not being used by any RSI
module. Hence removing that part of code doesn't impact.
Signed-off-by: Prameela Rani Garnepudi
---
drivers/net/wireless/rsi/rsi_91x_sdio_ops.c | 187
The older firmware loading method has been deprecated and not
in use with the current RS9113 modules. The newer method uses
soft boot loader to load the functional firmware.
In this method complete RAM image and FLASH image are present
in the flash. Before loading the functional firmware, host
The file rsi_91x_hal.c will contain new firmware loading method for
RSI 9113 chipset. So this file will have device specific operations.
As the file 'rsi_91x_pkt.c' contains code for preparing device
(frimware understandable) specific descriptors for the transmit frames,
it is moved to
We have to use start port, for TX/RX of single packet,
instead of current aggregating port. This will fix SDIO
CMD53(TX/RX) returning -ETIMEDOUT and halting the data path.
fixes: 0cb52aac4 ('mwifiex: do not set multiport flag for tx/rx single packet')
Signed-off-by: Ganapathi Bhat
[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at
driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote:
> Hi Paul,
>
> On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote:
> > Currently ia64 fails building allmodconfig with variations of:
> >
> >In
On Mon, Apr 03, 2017 at 12:15:15PM +0200, Arend Van Spriel wrote:
> seems we are missing out again?
Sorry, I don't understand what this comment means?
> On 3-4-2017 11:50, Toke Høiland-Jørgensen wrote:
> > "Tobin C. Harding" writes:
> >
> >> Except one: do you know off the top
From: David Binderman [mailto:dcb...@hotmail.com]
Sent: Monday, April 3, 2017 2:16 PM
>
> Hello there,
>
> 1.
>
> linux-4.11-rc5/drivers/net/wireless/ath/wil6210/pmc.c:188]: (style) Array
> index 'i' is used before limits check.
Thanks for letting us know.
We'll upload a fix soon.
Thanks,
On Fri, Mar 31, 2017 at 03:50:27PM -0700, Dmitry Torokhov wrote:
> That said, I consider the whole wifi-only firmware business is quite
> fragile. Can we have unified firmware and have driver figure out what
> part shoudl be [re]loaded?
+1. I think we should really give a stab at this first, and
From: Yan-Hsuan Chuang
The larger the bt a2dp bit pool is, the more time bt needs to receive
them. If we do not adjust the wifi duration, the voice quality will be
low. Hence we reduce the time that wifi holds, to improve the a2dp
service.
Signed-off-by: Yan-Hsuan Chuang
From: Yan-Hsuan Chuang
modify h2c parameter so that the rate suffers less penalty from retry
Signed-off-by: Yan-Hsuan Chuang
Signed-off-by: Larry Finger
Cc: Pkshih
Cc: Birming Chiu
From: Yan-Hsuan Chuang
set coex table fine tune, for register settings
Signed-off-by: Yan-Hsuan Chuang
Signed-off-by: Larry Finger
Cc: Pkshih
Cc: Birming Chiu
Cc: Shaofu
From: Yan-Hsuan Chuang
The bt can specify a power level to decrease. Rather than decreasing by a
fixed value (usually 2), this change makes the driver fit to the
environment more quickly.
Signed-off-by: Yan-Hsuan Chuang
Signed-off-by: Larry Finger
From: Yan-Hsuan Chuang
Earlier versions of the FW did not support h2c to set GNT_BT, but later
versions have that capability. Hence we check the FW version and decide
whether to use h2c or just write to the register.
Signed-off-by: Yan-Hsuan Chuang
On Fri, Mar 31, 2017 at 03:46:58PM -0700, Dmitry Torokhov wrote:
> On Thu, Mar 30, 2017 at 2:19 AM, Xinming Hu wrote:
> > From: Xinming Hu
> >
> > adapter->dev is initialized after mwifiex_register done, before that
> > print message by general pr_*
From: Yan-Hsuan Chuang
Since btcoex uses static variables to store the cumulative information
on the wifi status, some tricks are used that are a bit obscure. We add
some comments about the criteria we use to adjust wifi duration.
Signed-off-by: Yan-Hsuan Chuang
From: Yan-Hsuan Chuang
New ICs have hardware mailbox to deliver bt information instead of doing
it by driver itself, so remove them.
Signed-off-by: Yan-Hsuan Chuang
Signed-off-by: Larry Finger
Cc: Pkshih
From: Yan-Hsuan Chuang
if the bt is slave, it may receive packet at any time, so we
need to mark them as high priority packets to avoid packet loss.
Signed-off-by: Yan-Hsuan Chuang
Signed-off-by: Larry Finger
Cc: Pkshih
From: Yan-Hsuan Chuang
For wifi and bt coexistence, if the aggregation size of wifi is too
large, the transmission time of the aggregated packet could be too long
and the bt packets might "cut off" the wifi packet. We need to reduce
the aggregation size to improve wifi
From: Yan-Hsuan Chuang
A number of functions in the Bluetooth Coexistence routines are not used,
and can be removed.
Signed-off-by: Yan-Hsuan Chuang
Signed-off-by: Larry Finger
Cc: Pkshih
Cc: Birming
On Fri, Mar 31, 2017 at 03:37:01PM -0700, Dmitry Torokhov wrote:
> On Thu, Mar 30, 2017 at 2:19 AM, Xinming Hu wrote:
> > From: Xinming Hu
> >
> > Sanity check of interrupt number in interrupt handler is unnecessary and
> > confusion, remove it.
>
> I'd
[Re: [PATCH v2] nfc: don't be making arch specific unaligned decisions at
driver level.] On 02/04/2017 (Sun 00:22) Samuel Ortiz wrote:
> Hi Paul,
>
> On Mon, Jan 09, 2017 at 12:52:22PM -0500, Paul Gortmaker wrote:
> > Currently ia64 fails building allmodconfig with variations of:
> >
[...]
>
From: Karthik Ananthapadmanabha
In mwifiex,IEs such as supported channels, supported operating classes
20/40 BSS COexistence are missing and also extra QOS capabilities IE
is added during TDLS discovery response, TDLS setup request and
TDLS setupresponse.
This patch adds
On Mon, Apr 03, 2017 at 01:21:08PM +, Kalle Valo wrote:
> Johan Hovold writes:
>
> > On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote:
> >> Kalle Valo writes:
> >>
> >> > Johan Hovold writes:
> >> >
> >> >> On Mon, Mar
Johan Hovold writes:
> On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote:
>> Kalle Valo writes:
>>
>> > Johan Hovold writes:
>> >
>> >> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote:
>> >>> Make sure to check
On Mon, Apr 03, 2017 at 01:02:28PM +, Kalle Valo wrote:
> Kalle Valo writes:
>
> > Johan Hovold writes:
> >
> >> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote:
> >>> Make sure to check the number of endpoints to avoid dereferencing a
>
Kalle Valo writes:
> Johan Hovold writes:
>
>> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote:
>>> Make sure to check the number of endpoints to avoid dereferencing a
>>> NULL-pointer or accessing memory beyond the endpoint array should a
Hi Yan-Hsuan,
[auto build test WARNING on wireless-drivers-next/master]
[also build test WARNING on v4.11-rc5 next-20170403]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Larry-Finger/rtlwifi
On Mon, Apr 03, 2017 at 07:03:59PM +1000, Tobin C. Harding wrote:
> On Mon, Apr 03, 2017 at 08:19:40AM +0300, Kalle Valo wrote:
> > + linux-wireless
> >
> > "Tobin C. Harding" writes:
> >
> > > On Fri, Mar 31, 2017 at 09:58:51AM +0200, Wolfram Sang wrote:
> > >>
> > >> > The
+ linux-wireless
Prameela Rani Garnepudi writes:
> The file rsi_91x_hal.c will contain new firmware loading method for
> RSI 9113 chipset. So this file will have device specific operations.
> As the file 'rsi_91x_pkt.c' contains code for preparing device
> (frimware
Arend Van Spriel writes:
> On 29-3-2017 13:18, Rafał Miłecki wrote:
>> On 03/28/2017 12:43 PM, Arend van Spriel wrote:
>>> From: Franky Lin
>>>
>>> Create a new protocol layer interface brcmf_proto_init_cb for protocol
>>> layer to finish
Elena Reshetova writes:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
>
Elena Reshetova writes:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
>
Hi Dave,
here few really small fixes. I'm hoping this to be the last pull request
for 4.11.
Please let me if there are any problems.
Kalle
The following changes since commit 6be3b6cce1e225f189b68b4e84fc711d19b4277b:
ath10k: fix incorrect wlan_mac_base in qca6174_regs (2017-03-20 17:11:31
seems we are missing out again?
On 3-4-2017 11:50, Toke Høiland-Jørgensen wrote:
> "Tobin C. Harding" writes:
>
>> Except one: do you know off the top of your head of a canonical
>> implementation of a softmac wi-fi driver.
>
> I'll suggest taking a look at the ath9k driver :)
"Tobin C. Harding" writes:
> Except one: do you know off the top of your head of a canonical
> implementation of a softmac wi-fi driver.
I'll suggest taking a look at the ath9k driver :)
-Toke
"Tobin C. Harding" writes:
>> >> But if you want a clean WEXT driver first, this is a step in the right
>> >> direction.
>> >
>> > Let's go for a CFG80211 driver and get out of staging :) So next step
>> > is I guess study the ath6kl driver, learn how CFG80211 is done and
>> >
From: Colin Ian King
trivial fix to spelling mistakes in wl1271_warning error message, change
iligal to invalid and opperation to operation.
Signed-off-by: Colin Ian King
---
drivers/net/wireless/ti/wlcore/debugfs.c | 2 +-
1 file changed, 1
On 03/04/17 10:20, Joe Perches wrote:
> On Mon, 2017-04-03 at 10:15 +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> trivial fix to spelling mistake in wl1271_warning error message
>>
>> Signed-off-by: Colin Ian King
>> ---
>>
Johan Hovold writes:
> On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote:
>> Make sure to check the number of endpoints to avoid dereferencing a
>> NULL-pointer or accessing memory beyond the endpoint array should a
>> malicious device lack the expected endpoints.
>>
On Mon, 2017-04-03 at 10:15 +0100, Colin King wrote:
> From: Colin Ian King
>
> trivial fix to spelling mistake in wl1271_warning error message
>
> Signed-off-by: Colin Ian King
> ---
> drivers/net/wireless/ti/wlcore/debugfs.c | 2 +-
> 1
From: Colin Ian King
trivial fix to spelling mistake in wl1271_warning error message
Signed-off-by: Colin Ian King
---
drivers/net/wireless/ti/wlcore/debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, Apr 03, 2017 at 08:19:40AM +0300, Kalle Valo wrote:
> + linux-wireless
>
> "Tobin C. Harding" writes:
>
> > On Fri, Mar 31, 2017 at 09:58:51AM +0200, Wolfram Sang wrote:
> >>
> >> > The code is untested, I have hardware in the mail.
> >>
> >> Cool!
> >
> > The card I
Dear all,
ETSI is publishing in the coming months an update of the EN 301 893
standard with major changes on the adaptivity and receiver blocking
tests behavior
(https://www.nts.com/ntsblog/upcoming-changes-for-wireless-equipment-in-the-5-ghz-band-en-301-893/).
The adaptivity test requirements
On Mon, Mar 13, 2017 at 01:44:20PM +0100, Johan Hovold wrote:
> Make sure to check the number of endpoints to avoid dereferencing a
> NULL-pointer or accessing memory beyond the endpoint array should a
> malicious device lack the expected endpoints.
>
> Fixes: 36bcce430657 ("ath9k_htc: Handle
49 matches
Mail list logo