If rt2800usb is loaded with nohwcrypt=1, mac80211 takes
care of the crypto with software encryption/decryption
and thus, MFP can be used.
Tested for secured mesh using ath9k_htc and ath9k.
Signed-off-by: Chun-Yeow Yeoh
---
drivers/net/wireless/ralink/rt2x00/rt2800usb.c | 1 +
1 file changed, 1
Hi,
I've successfully managed to get this driver working in adhoc with
olsrd on mlan0 interface, now I'm trying to add a uap0 working at the
same time, with all this command:
rfkill unblock wlan
ip link set uap0 down
ip link set mlan0 down
iw dev mlan0 set type ibss
ip link set mlan0 up
iw dev mla
tx_packets counter is incremented for aggregated packets, when it had
already been incremented for the aggregated packet's constituent
parts. Removing the extra count.
Signed-off-by: Marty Faltesek
---
drivers/net/wireless/marvell/mwifiex/txrx.c | 13 +++--
1 file changed, 7 insertions(+
Signed-off-by: Marty Faltesek
---
drivers/net/wireless/marvell/mwifiex/sdio.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/wireless/marvell/mwifiex/sdio.c
b/drivers/net/wireless/marvell/mwifiex/sdio.c
index 4c8cae6..d6ef34f 100644
--- a/drivers/net/wireless/m
When a packet is queued from the bridge, wmm_tx_pending is not
incremented, but when the packet is dequeued the counter is decremented.
Signed-off-by: Marty Faltesek
---
drivers/net/wireless/marvell/mwifiex/uap_txrx.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/net/wireless/m
As Julian suggests, this is handled by the cs-gpios property, so we will
drop this patch, but keep the other three active.
Thanks for the suggestion.
On Mon, Apr 18, 2016 at 8:07 PM, Julian Calaby
mailto:julian.cal...@gmail.com>> wrote:
Hi Geoff,
On Tue, Apr 19, 2016 at 5:48 AM, Ge
On Tue, 19 Apr 2016 23:11:58 +0300,
Bjørn Mork wrote:
> Anyway, 300 674 is for vehicle transponder systems. I.e. electronic
> toll collection etc. I don't think it's relevant to the regdb in any
> way.
Thanks for the response! I'll be sure to ask the CRC why do they reference 300
674 in the _Gen
Petko Bordjukov writes:
> Hello,
>
> Just to add my input to this thread. I've previously contributed the SRD
> ranges
> for Bulgaria, hopefully this info will provide pointers for research in other
> EU
> countries. Since then I've doublechecked the standards situation for Wi-Fi
> with
> the
Over in https://bugs.debian.org/821400, Ben Hutchings makes the
reasonable suggestion that where possible, when
brcm/brcmfmac43340-sdio.txt (or configuration file for other brcm
chipsets) is not available, brcmfmac_sdio should try looking for
configuration in the efi variables directly.
That would
Hello,
Just to add my input to this thread. I've previously contributed the SRD ranges
for Bulgaria, hopefully this info will provide pointers for research in other EU
countries. Since then I've doublechecked the standards situation for Wi-Fi with
the local communications regulation commission and
On Tue, Apr 19, 2016 at 06:04:49PM +, Reizer, Eyal wrote:
> Thanks! Glad the illustration helped.
> I will try it out again as if i recall cotrectly, i did try that l, and it
> didnt produce the correct waveform, but perhaps i didnt understand the usage
> of .cs_change correctly.
> Will doub
Kalle Valo writes:
> Jes Sorensen writes:
>
>> Arnd Bergmann writes:
>>> The references to some arrays in the rtl8xxxu driver were moved inside
>>> of an #ifdef, but the symbols remain outside, resulting in build warnings:
>>>
>>> rtl8xxxu/rtl8xxxu.c:1506:33: error:
>>> 'rtl8188ru_radioa_1t_high
Hi,
In Europe ETSI standardized the used for short range devices (SRD) [1] in ETSI
EN 300 440-1 [2].
According to this standard generic use equipment is allowed to transmit in the
frequency range form 5725 MHz to 5875 MHz with a maximum output power of
25 mW e.i.r.p. This generic allocation als
On Tue, Apr 19, 2016 at 05:38:02PM +, Reizer, Eyal wrote:
> Hi Mark,
>
> Hope you can see the attached picture that illustrates what need to sent for
> sucesfull SPI init.
I think what the picture shows is that you just need to send at least
one byte at the end of the transfer *after* deasse
On Tue, Apr 19, 2016 at 05:21:01PM +, Reizer, Eyal wrote:
> The main quirk here is that i need to send extra clocks after the spi init
> command while the CS pin is "high" in order to put the wilink chip into SPI
> mode.
> So just sending an empty transfer wouldnt do the trick here.
A singl
On Tue, Apr 19, 2016 at 09:05:45AM +, Reizer, Eyal wrote:
> Understood. As this special CS manipulation is unique to wspi (wilink spi) I
> think the
> best option is to move this gpio allocation into wlcore_spi as a new device
> tree entry
> used only by this driver.
That sounds like it i
On Mon, Apr 18, 2016 at 05:55:51AM +, Reizer, Eyal wrote:
> > I would suggest fixing this using a new API function from the SPI core, if
> > we
> > don't already have a generic way to do it.
> Originally this is what I have done until I was pointed to the generic
> cs-gpio mechanism
> in t
Zefir Kurtisi writes:
> Tx power limitations at upper layers are interpreted in
> the EIRP domain. When the user requests a given maximum
> txpower, e.g. with: 'iw phy0 set txpower fixed 1500',
> he expects the EIRP to be at or below 15dBm.
>
> In ath9k_hw_apply_txpower(), the interpretation is
>
Julian Calaby writes:
> On Sat, Jan 2, 2016 at 5:25 AM, SF Markus Elfring
> wrote:
>> From: Markus Elfring
>> Date: Fri, 1 Jan 2016 19:09:32 +0100
>>
>> Replace an explicit initialisation for one local variable at the beginning
>> by a conditional assignment.
>>
>> Signed-off-by: Markus Elfring
Colin King writes:
> From: Colin Ian King
>
> ah is written twice with the same value, remove one of the
> redundant assignments to ah.
>
> Signed-off-by: Colin Ian King
Applied, thanks.
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of
Jes Sorensen writes:
> Arnd Bergmann writes:
>> The references to some arrays in the rtl8xxxu driver were moved inside
>> of an #ifdef, but the symbols remain outside, resulting in build warnings:
>>
>> rtl8xxxu/rtl8xxxu.c:1506:33: error: 'rtl8188ru_radioa_1t_highpa_table'
>> defined but not us
Applied, thanks.
I removed the line wrapping from "Fixes:" lines.
[shafi] thank you Kalle.
--
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
writes:
> From: Raja Mani
>
> push-pull mode needs certain amount the host driver involvement for
> managing queues in the host memory and packet delivery to firmware.
> qca4019 wifi firmware has an option to stay in push mode for less
> number of active traffic flow and then switch to push-pull
Dan Carpenter writes:
> Smatch complains that since "ev->peer_id" comes from skb->data that
> means we can't trust it and have to do a bounds check on it to prevent
> an array overflow.
>
> Fixes: 6942726f7f7b ('ath10k: add fast peer_map lookup')
> Signed-off-by: Dan Carpenter
Applied, thanks.
Rajkumar Manoharan writes:
> Upon firmware assert, restart work will be triggered so that mac80211
> will reconfigure the driver. An issue is reported that after restart
> work, survey dump data do not contain in-use (SURVEY_INFO_IN_USE) info
> for operating channel. During reconfigure, since mac
Mohammed Shafi Shajakhan writes:
> From: Mohammed Shafi Shajakhan
>
> Return value is incorrect for btcoex and peer stats debugfs
> 'write' entries if the user provides a value that matches with
> the already available debugfs entry, this results in the debugfs
> entry getting stuck and the oper
Kalle Valo writes:
> I updated checkpatch and noticed that there are few new warnings.
>
> v2:
>
> * fix tests in patch 3
> * add patch 5 to fix a new warning in mac.c
>
> ---
>
> Kalle Valo (5):
> ath10k: fix checkpatch warnings related to spaces
> ath10k: prefer kernel type 'u64' ov
Arnd Bergmann writes:
> The references to some arrays in the rtl8xxxu driver were moved inside
> of an #ifdef, but the symbols remain outside, resulting in build warnings:
>
> rtl8xxxu/rtl8xxxu.c:1506:33: error: 'rtl8188ru_radioa_1t_highpa_table'
> defined but not used
> rtl8xxxu/rtl8xxxu.c:1431:
> > > > It is also part of the generic spi.h (include/Linux/spi/spi.h),
> > > > already part of " struct spi_device" So it seemed redundant adding
> > > > another mechanism for implementing the same.
> > > > Platform that interact with a wilink need to use it, and platforms
> > > > that don't have
Smatch complains about this code:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/core.c:335
brcmf_rx_hdrpull()
error: we previously assumed '*ifp' could be null (see line 333)
The problem is that we recently changed these from "ifp" to "*ifp" but
there was one that we didn't update.
-
USB8XXX_FW_MAX_RETRY is 3. We were using a post-op loop
"while (retries--) {" but then the lines after that assume the loop
exits with retries set to zero.
I've fixed this by changing to a pre-op loop. I started with retries
set to 4 instead of 3 so that we still go through the loop the same
num
We accidentally return success instead of -ENOMEM.
Signed-off-by: Dan Carpenter
diff --git a/drivers/net/wireless/marvell/mwifiex/usb.c
b/drivers/net/wireless/marvell/mwifiex/usb.c
index 0510861..cdd8f9a 100644
--- a/drivers/net/wireless/marvell/mwifiex/usb.c
+++ b/drivers/net/wireless/marvell/
On Tuesday 19 April 2016 09:05:45 Reizer, Eyal wrote:
> > > It is also part of the generic spi.h (include/Linux/spi/spi.h),
> > > already part of " struct spi_device" So it seemed redundant adding
> > > another mechanism for implementing the same.
> > > Platform that interact with a wilink need to
Steve deRosier writes:
> On Sun, Apr 17, 2016 at 5:07 PM, Julian Calaby
> wrote:
>> Hi Steve,
>>
>> This looks like it's using standard serial rates. Does it accept
>> non-standard rates? If not, should this be checked before being passed
>> to the hardware?
>>
>
> It should use standard serial
On 19 April 2016 at 13:02, Johannes Berg wrote:
>> > How much of that could be done with nftables btw?
>
>> I'm not sure if I follow. Do you mean what I've been able to do with
>> relayd until now? Without link-local ipv6 routing DHCPv6 is broken
>> (could probably addressed with DHCPv6 Relay to a
> > How much of that could be done with nftables btw?
> I'm not sure if I follow. Do you mean what I've been able to do with
> relayd until now? Without link-local ipv6 routing DHCPv6 is broken
> (could probably addressed with DHCPv6 Relay to a certain degree) and
> RS/RA may not work (if it pro
On 19 April 2016 at 11:11, Johannes Berg wrote:
> On Mon, 2016-04-18 at 13:23 +0200, Michal Kazior wrote:
>
>> You can't really implement complete IPv6 support in relayd though.
>> Link-local routing is forbidden by the spec explicitly and a patch
>> I've cooked up was rejected[1].
>>
>> I guess t
On Tue, 2016-04-19 at 11:31 +0200, Michal Kazior wrote:
> > We should just get rid of all the rate stuff and convert everything
> > to use rate tables, but ... :)
> I'm guessing it's not trivial either and you risk breaking a lot of
> stuff? :)
It's not "tricky" in the same sense - but we'd have
On 19 April 2016 at 11:06, Johannes Berg wrote:
> On Mon, 2016-04-18 at 14:38 +0200, Michal Kazior wrote:
>> On 18 April 2016 at 07:31, Michal Kazior
>> wrote:
>> >
>> > On 17 April 2016 at 00:29, Johannes Berg > > > wrote:
>> > >
>> > > On Thu, 2016-04-14 at 14:18 +0200, Michal Kazior wrote:
>>
On Mon, 2016-04-18 at 13:23 +0200, Michal Kazior wrote:
> You can't really implement complete IPv6 support in relayd though.
> Link-local routing is forbidden by the spec explicitly and a patch
> I've cooked up was rejected[1].
>
> I guess this leaves either the kernel's wireless stack to take up
On Mon, 2016-04-18 at 15:36 +0200, Michal Kazior wrote:
> FWIW cfg80211 drivers might become another user of the fq/codel stuff
> in the future.
>
> Arguably I should make include/net/codel.h not be qdisc specific as
> it is now (and hence re-usable by mac80211) and submit fq.h to
> include/net/.
On Mon, 2016-04-18 at 14:38 +0200, Michal Kazior wrote:
> On 18 April 2016 at 07:31, Michal Kazior
> wrote:
> >
> > On 17 April 2016 at 00:29, Johannes Berg > > wrote:
> > >
> > > On Thu, 2016-04-14 at 14:18 +0200, Michal Kazior wrote:
> > > >
> > > >
> > > > + str
Arnd,
> > > >
> > > > - all wilink family needs special init command for entering wspi mode.
> > > > extra clock cycles should be sent after the spi init command while the
> > > > cs pin is high.
> > > > - switch to controling the cs pin from the spi driver for achieveing the
> > > > above.
On Mon, 2016-04-18 at 00:10 +0200, Arnd Bergmann wrote:
> On Sunday 17 April 2016 14:42:33 Johannes Berg wrote:
> >
> >
> > I was thinking more restrictively of just the stuff that can't even
> > be
> > built without modifying the sources - like the "#if VERBOSE" thing.
> All the DEBUG() statemen
On Mon, 2016-04-18 at 22:00 -0700, Bjorn Andersson wrote:
> From: Pontus Fuchs
>
> While poking at this I also change two related things. I rename one
> variable to make the names consistent. I also move one assignment of
> priv_sta to the declaration to save a few lines.
trivia:
The commit sub
45 matches
Mail list logo