"Raja, Tamizh Chelvam" writes:
>>> From: Tamizh chelvam
>>>
>>> Set peer's management frame protection flag in peer assoc command,
>>> this setting will enable/disable encrytion of management frames in fw.
>>>
>>> Setting of this flag is based on whether MFP is enabled/disabled at
>>> STA and
The addresses are not properly aglined for using ether_addr_copy function.
I revert this as author agree to drop this patch.
This reverts commit d4622f68db8095dd54179e3134e97812727f6b89.
Signed-off-by: Glen Lee
---
drivers/staging/wilc1000/coreconfigurator.c | 48 +++--
On Tue, 2015-11-03 at 09:43 -0800, Tim Harvey wrote:
> No surprise that its sold outside the US, but why should that mean it
> should exclude 5GHz support? They all have their regulatory domains
> and my understanding is that the intersection of the reg domain rules
> and card capabilities should
On Wed, 2015-11-04 at 08:31 +0200, Dima Krasner wrote:
> Hi,
>
> Recent libnl-tiny revisions do not specify a version in the pkg
> -config data. This patch corrects libnl-tiny support added in the
> previous patch in the series, so it works with the latest revision
> too.
You need to resend the
Hi,
Recent libnl-tiny revisions do not specify a version in the pkg-config data.
This patch corrects libnl-tiny support added in the previous patch in the
series, so it works with the latest revision too.
Cheers,
Dima
>From 84f4fbf5e9f765dafbb436b2593f13d1326a27ea Mon Sep 17 00:00:00 2001
From
[fixed ath9k list address. sorry for the spam]
Hi all,
I have a pretty weird problem I've been chasing for a few weeks and
have narrowed it down, but not quite solved it. It may be caused by
bugs in aggregation-related code.
Steps:
- Set up an ath9k-based Linux AP on an ARM processor (currentl
>> From: Tamizh chelvam
>>
>> Set peer's management frame protection flag in peer assoc command,
>> this setting will enable/disable encrytion of management frames in fw.
>>
>> Setting of this flag is based on whether MFP is enabled/disabled at
>> STA and a firmware feature flag ATH10K_FW_FEATUR
>> From: Tamizh chelvam
>>
>> This patch enables thermal throttling support for 10.4 firmware.
>>
>> Signed-off-by: Tamizh chelvam
>There was a trivial conflict, please check my conflict resolution in the
>pending branch:
>https://git.kernel.org/cgit/linux/kernel/git/kvalo/ath.git/commit/?h=pe
Hi all,
I have a pretty weird problem I've been chasing for a few weeks and
have narrowed it down, but not quite solved it. It may be caused by
bugs in aggregation-related code.
Steps:
- Set up an ath9k-based Linux AP on an ARM processor (currently using
this version of backports, though I've tr
On Fri, Oct 23, 2015 at 11:21:46AM +0200, Arend van Spriel wrote:
> One firmware file update and firmware for a new supported device.
>
> The patches are for the master branch of the linux-firmware repository
> and apply on top of commit 66d3d8d7607c ("Add FW binary used by mwlwifi
> driver.").
>
On Tue, Oct 20, 2015 at 06:13:29PM +0300, Kalle Valo wrote:
> This is to make sure that the notice files get automatically included.
>
> Signed-off-by: Kalle Valo
applied.
> ---
> WHENCE |5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/WHENCE b/WHENCE
> index 9b7e8e8526aa..ded
Hi Arnd,
On Tue, Nov 03, 2015 at 03:03:33PM +0100, Arnd Bergmann wrote:
> The newly added nfcmrvl_spi driver uses the spi_nci
> infrastructure, but does not have a Kconfig dependency on
> that, so we can get a link-time error:
>
> drivers/built-in.o: In function `nfcmrvl_spi_nci_send':
> (.text+0
I've been digging in the guts of ath10k rate-ctrl, and I notice that if
I tell the chip to do NSS of 1 without STBC or LDPC, then it works as I expect
(single stream, MCS-1 encoding).
But, if I do NSS of 1 and STBC and LDPC enabled (VHT-MCS-0, for instance), then
wireshark shows the frame as bein
Hi,
I'd like to upstream this patch, which adds libnl-tiny support to iw, as a
smaller alternative to libnl 2.0. It's great for static builds against musl.
Cheers,
Dima
>From 88ad01745f6f8b2d5fcc066d18dba9dce21609fd Mon Sep 17 00:00:00 2001
From: Dima Krasner
Date: Wed, 4 Nov 2015 00:04:44 +0
OK. Too bad.
Anyway, this EEPROM RF chipset detection is the part where needs to be
looked at. At least that's where rt2x00 is deciding that the HW doesn't
support 5GHz.
On 11/03/15 22:44, Alberto Mattea wrote:
> Hey,
>
> I didn't have to, it was recognized this way out of the box.
> I had to in
In data mar 3 novembre 2015 22:44:00, Alberto Mattea ha scritto:
> Hey,
>
> I didn't have to, it was recognized this way out of the box.
> I had to install an eeprom for the other onboard chip though (5390).
Oh and I just found this in lsmod:
eeprom_93cx61616 1 rt2800pci
So it seem
Hey,
I didn't have to, it was recognized this way out of the box.
I had to install an eeprom for the other onboard chip though (5390).
In data mar 3 novembre 2015 22:33:19, Gertjan van Wingerde ha scritto:
> Did you have to install an eeprom file for the RT5592 PCI device?
>
> If yes, this eepro
Did you have to install an eeprom file for the RT5592 PCI device?
If yes, this eeprom file could be the problem. As far as I can tell the
rt2x00 driver only enables the 2.4 GHz band because it determines that
the RF chip doesn't support the 5GHz band. The RF chip is determined
from the EEPROM, and
I found the FCC photos for the RP-N53:
https://apps.fcc.gov/eas/GetApplicationAttachment.html?id=2001985
On page 9 there is a photo of the ralink chip, unfortunately very blurred. But
I also found the photos for the Buffalo WHR-600D (which exhibits the same
behaviour):
https://apps.fcc.gov/eas/G
On 11/03/2015 07:10 PM, Alberto Mattea wrote:
> Hey, thanks for your answer. The device definitely isn't a RT3091, so do you
> think it's some sort of an OEM hybrid?
I don't know. Open the device or look for photos at FCC site.
wikidevi.com usually has links to it.
> Do you think it would be be
All signs point to RT5592 not supported by rt2x00 driver... I'm
guessing they fudged pci id for some internal reasons (maybe even to
mess with OpenWRT people).
On Tue, Nov 3, 2015 at 11:09 AM, Alberto Mattea wrote:
> My device (the RP-N53) has 2 chips too: the other is integrated in the mt7620
>
My device (the RP-N53) has 2 chips too: the other is integrated in the mt7620
soc and reports itself as
[ 14.12] ieee80211 phy1: rt2x00lib_request_eeprom_file: Info - Loading
EEPROM data from 'soc_wmac.eeprom'.
[ 14.14] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 5390, rev 0500
This is so strange. Asus RT-N56U you mentioned earlier as one of the
examples actually has two separate chips for each band (and one of
them is RT3091) - https://wikidevi.com/wiki/ASUS_RT-N56U
Are you able to take a picture of the chip?
On Tue, Nov 3, 2015 at 10:10 AM, Alberto Mattea wrote:
> Hey
Hey, thanks for your answer. The device definitely isn't a RT3091, so do you
think it's some sort of an OEM hybrid? Do you think it would be better to
report this to the openwrt bugzilla?
Thanks
In data mar 3 novembre 2015 14:41:35, Xose Vazquez Perez ha scritto:
> Alberto Mattea wrote:
> > th
On Tue, Nov 3, 2015 at 8:27 AM, Johannes Berg wrote:
> On Tue, 2015-11-03 at 08:08 -0800, Tim Harvey wrote:
>>
>> Out of curiosity, can you explain what you mean about 'regulatory
>> concerns'? There are channels in the 5GHz band that can be used in
>> FCC
>> with and without DFS. Is it that certi
When channel context is enabled, we could be
stopping/awakening an incorrect queue.
---
drivers/net/wireless/ath/ath9k/xmit.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/ath/ath9k/xmit.c
b/drivers/net/wireless/ath/ath9k/xmit.c
From: Johannes Berg
Date: Tue, 03 Nov 2015 15:40:02 +0100
> After the travel I got a whole bunch of things in - I've sorted through
> and taken the fix-like things.
>
> Note that this is in the mac80211 tree, but based on net-next, since I
> thought you might decide to pull this in before you se
On Tue, 2015-11-03 at 08:08 -0800, Tim Harvey wrote:
>
> Out of curiosity, can you explain what you mean about 'regulatory
> concerns'? There are channels in the 5GHz band that can be used in
> FCC
> with and without DFS. Is it that certification in the 5GHz band is
> optional and Intel didn't wa
On Sat, Oct 31, 2015 at 12:12 PM, Grumbach, Emmanuel
wrote:
> Hi,
>
> On 10/30/2015 06:37 PM, Pushpal Sidhu wrote:
>> Hi,
>>
>> I've been working with the Intel 7260 card which advertises itself as
>> dual band wireless AC card. However, I cannot get it working in AP
>> mode in the 5GHz range. An
On Mon, Nov 2, 2015 at 8:40 PM, Chaitanya T K wrote:
> From: tkc
>
> Before the tx_status is received for the action frame, if we
> get another request, we respond to that by freeing the memory
> for pending_action_tx, but we don't cancel the TX wait, so
> in the kernel the ROC will not be cancel
Hi all,
I hope this is the right place to ask for help.
I am experiencing problems when I try to create a IBSS netwoork with
wpa_supplicant.
The drivers used for the wifi hardware are the "libertas" and the
wireles adapter is a Marvell WLAN 802.11.
What happens is that when I create the network
On Tue, Nov 03, 2015 at 07:05:11PM +0900, Glen Lee wrote:
> The addresses are not properly aglined for using ether_addr_copy function.
> I revert this as author agree to drop this patch.
>
> This reverts commit d4622f68db8095dd54179e3134e97812727f6b89.
> ---
> drivers/staging/wilc1000/coreconfigu
Hi,
After the travel I got a whole bunch of things in - I've sorted through
and taken the fix-like things.
Note that this is in the mac80211 tree, but based on net-next, since I
thought you might decide to pull this in before you send a pull request
to Linus.
However, the content is only things I
Hello Christophe Ricard,
The patch a1b0b9415817: "NFC: nci: Create pipe on specific gate in
nci_hci_connect_gate" from Oct 25, 2015, leads to the following
static checker warning:
net/nfc/nci/hci.c:679 nci_hci_connect_gate()
warn: impossible condition '(pipe < 0) => (0-255 < 0)'
The newly added nfcmrvl_spi driver uses the spi_nci
infrastructure, but does not have a Kconfig dependency on
that, so we can get a link-time error:
drivers/built-in.o: In function `nfcmrvl_spi_nci_send':
(.text+0x1428dc): undefined reference to `nci_spi_send'
drivers/built-in.o: In function `nfcm
Alberto Mattea wrote:
> this is about the mini-pcie version used in some embedded products
> (for example the Buffalo WHR-600D and the Asus RP-N53).
> It has an RT5592 chip and the hardware supports both 2.4 and 5Ghz
> (5Ghz works with the proprietary driver supplied with the devices),
> but rt280
Dan Carpenter reported the following:
"The patch a06347c04c13: "NFC: Add Intel Fields Peak NFC solution
driver" from Oct 22, 2015, leads to the following Smatch complaint:
drivers/nfc/fdp/i2c.c:216 fdp_nci_i2c_irq_thread_fn()
warn: variable dereferenced before check 'phy' (see line 213)
Hello Robert Dolca,
This is a semi-automatic email about new static checker warnings.
The patch a06347c04c13: "NFC: Add Intel Fields Peak NFC solution
driver" from Oct 22, 2015, leads to the following Smatch complaint:
drivers/nfc/fdp/i2c.c:216 fdp_nci_i2c_irq_thread_fn()
warn: variabl
Hello, thanks for your answer. I'm completely sure the hardware supports 5Ghz:
with the proprietary ralink driver it works. As you can see from the dmesg,
the board actually has a RT5592, not a RT3091. So I think the board has only
the pci device id of the RT3091, and that is confusing the rt280
On Sat, 2015-10-24 at 00:33 +0200, Ola Olsson wrote:
> The NLA_PUT macro will automatically goto nla_put_failure if
> the underlying nla_put fails. This will in turn leak our malloced
> memory in both the scan and wowlan commands.
> Fix that by not using the macro in the cases where we have
> alloc
On Fri, 2015-10-23 at 11:20 +0300, Emmanuel Grumbach wrote:
> From: Ayala Beker
>
> Currently, cfg80211 rejects updates of AID and listen interval
> parameters
> for existing entries. This information is known only at association
> stage,
> and as a result it's impossible to update entries that
On Fri, 2015-10-30 at 23:16 +0530, Chaitanya T K wrote:
> From: Chaitanya T K
>
> Channel context OPs can sleep, so add might_sleep() and
> also document sleep requirements for those OPs.
>
Applied.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the bod
The addresses are not properly aglined for using ether_addr_copy function.
I revert this as author agree to drop this patch.
This reverts commit d4622f68db8095dd54179e3134e97812727f6b89.
---
drivers/staging/wilc1000/coreconfigurator.c | 48 +++--
1 file changed, 25 inserti
On Sun, 2015-10-25 at 10:59 +0200, Emmanuel Grumbach wrote:
> From: Arik Nemtsov
>
> When 11n peers performs a TDLS connection on a legacy BSS, the HT
> operation IE must be specified according to IEEE802.11-2012 section
> 9.23.3.2. Otherwise HT-protection is compromised and the medium
> becomes
On Sun, 2015-10-25 at 10:59 +0200, Emmanuel Grumbach wrote:
> From: Eliad Peller
>
> If drv_start() fails during hw_restart, all the running
> interfaces are being closed/stopped, which results in
> drv_stop() being called, although the driver was never
> started successfully.
>
Applied.
johann
On Sat, 2015-10-24 at 21:25 +0200, Matthias Schiffer wrote:
> llid_in_use needs to be limited to stations of the same VIF,
> otherwise it
> will cause a NULL deref as the sta_info of non-mesh-VIFs don't have
> sta->mesh set.
>
Applied, thanks.
johannes
--
To unsubscribe from this list: send the
On Sun, 2015-10-25 at 10:59 +0200, Emmanuel Grumbach wrote:
> From: Eliad Peller
>
> Scheduled scan has to be reconfigured only if wowlan wasn't
> configured, since otherwise it should continue to run (with
> the 'any' trigger) or be aborted.
>
> The current code will end up asking the driver to
On 2 November 2015 at 15:03, Michal Kazior wrote:
> This prepares the driver for future ieee80211_txq
> and wake_tx_queue() support.
I think I've found a regression and bisect blames this patch. Do not
apply this yet, please.
Michał
--
To unsubscribe from this list: send the line "unsubscribe l
On Sun, 2015-10-25 at 10:59 +0200, Emmanuel Grumbach wrote:
> From: Andrei Otcheretianski
>
> The recalc_smps work can run after the station disassociates.
> At this stage we already released the channel, but the work
> will be cancelled only when the interface stops.
> In this scenario we can hi
On Sun, 2015-10-25 at 10:59 +0200, Emmanuel Grumbach wrote:
> From: Arik Nemtsov
>
> In TDLS channel-switch operations the chandef can sometimes be NULL.
> Avoid an oops in the trace code for these cases and just print a
> chandef full of zeros.
>
Applied, thanks.
johannes
--
To unsubscribe fro
On Tue, 2015-10-27 at 08:35 +0100, Janusz Dziedzic wrote:
> In case of one shot NOA the interval could be 0.
>
Applied, thanks!
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:
On Sun, 2015-10-25 at 10:59 +0200, Emmanuel Grumbach wrote:
> From: Eliad Peller
>
> Requesting hw restart during suspend might result
> in the restart work being executed after mac80211
> and the hw are suspended.
>
Applied.
johannes
--
To unsubscribe from this list: send the line "unsubscribe
On Sun, 2015-10-25 at 10:59 +0200, Emmanuel Grumbach wrote:
> From: Andrei Otcheretianski
>
> Local request to deauthenticate wasn't handled while associating,
> thus
> the association could continue even when the user space required to
> disconnect.
>
Applied.
johannes
--
To unsubscribe from
On Thu, 2015-10-29 at 07:04 +0100, Ola Olsson wrote:
> If parse_acl_data succeeds but the subsequent parsing of smps
> attributes fails, there will be a memory leak due to early returns.
> Fix that.
>
Applied, thanks!
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wir
Hi Shivani,
I will revert as you said, I always appreciate all the effort and your time to
help.
Regards,
glen lee.
On 2015년 11월 03일 17:26, Shivani Bhardwaj wrote:
On Mon, Nov 2, 2015 at 7:13 AM, glen lee wrote:
Hi Shivani Bhardwaj,
Thank you for the patches.
I am writing this new mail t
On Mon, Nov 2, 2015 at 7:13 AM, glen lee wrote:
> Hi Shivani Bhardwaj,
>
> Thank you for the patches.
>
> I am writing this new mail thread since I didn't received about following
> patch which is applied recently.
>
> https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/patch/drivers/s
56 matches
Mail list logo
