On 19-9-2016 8:36, Jörg Krause wrote:
> Hi Arend,
>
> On Wed, 2016-09-14 at 20:13 +0200, Arend Van Spriel wrote:
>> On 14-9-2016 15:41, Jörg Krause wrote:
>>>
>>> Hi,
>>>
>>> On Mon, 2016-08-29 at 23:15 +0200, Jörg Krause wrote:
On Mi, 2016-08-24 at 20:35 +0200, Arend Van Spriel wrote:
>
Hello,
I bought an Asus PCE-N10 PCIe Wi-Fi N card to install in my wife's
computer. This morning it stopped working suddenly. Investigating the
kernel logs, the following error message caught my eye:
rtl8192ce:rtl92ce_get_hw_reg():<0-0> switch case not processed
It was printed twice, 3.5 hours a
And again...
I decided to focus on brcmf_flowring_delete a bit more.
As I can see flowrings are created and removed from time to time, in most cases
they are empty when being deleted. When they are not, things go wrong. In below
log you can see brcmfmac removing flowring that got 8 skb packets.
On 09/22/2016 01:59 PM, Rafał Miłecki wrote:
And again...
I decided to focus on brcmf_flowring_delete a bit more.
As I can see flowrings are created and removed from time to time, in most cases
they are empty when being deleted. When they are not, things go wrong. In below
log you can see brcmf
>-Original Message-
>From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
>Sent: Monday, September 19, 2016 7:12 PM
>To: Nicolas Ferre
>Cc: linux-wireless@vger.kernel.org; Aditya Shankar - I16078; Ganesh Krishna -
>I00112; lui...@osg.samsung.com
>Subject: Re: staging: wilc1000: ke
On 09/21/2016 09:53 PM, bruce m beach wrote:
memory will be very tight. There is 160k or known ram and bits and pieces
elsewhere. The rom is 24k (maximum). I currently am not to worried about
it. (although I am watching it)
bruce
Probably you know this...but check structs for memory holes, un
On 22 September 2016 at 14:24, Rafał Miłecki wrote:
> On 09/22/2016 01:59 PM, Rafał Miłecki wrote:
>>
>> And again...
>>
>> I decided to focus on brcmf_flowring_delete a bit more.
>>
>> As I can see flowrings are created and removed from time to time, in most
>> cases
>> they are empty when being
On 09/22/2016 04:51 AM, Jean Delvare wrote:
Hello,
I bought an Asus PCE-N10 PCIe Wi-Fi N card to install in my wife's
computer. This morning it stopped working suddenly. Investigating the
kernel logs, the following error message caught my eye:
rtl8192ce:rtl92ce_get_hw_reg():<0-0> switch case no
The TXQ path restructure requires ieee80211_tx_dequeue() to call TX
handlers and parts of the xmit_fast path. Move the function to later in
tx.c in preparation for this.
Signed-off-by: Toke Høiland-Jørgensen
---
net/mac80211/tx.c | 90 +++
1 fi
The TXQ intermediate queues can cause packet reordering when more than
one flow is active to a single station. Since some of the wifi-specific
packet handling (notably sequence number and encryption handling) is
sensitive to re-ordering, things break if they are applied before the
TXQ.
This splits
This is the ninth iteration of my attempts to reorder the TXQ dequeue
path to avoid issues with reorder-sensitive operations. This version is
split into two patches; the first one moves ieee80211_tx_dequeue() to
avoid adding function stubs at the top of tx.c.
Changes since v8:
- Don't add function
On Thu, 22 Sep 2016 10:09:58 -0500, Larry Finger wrote:
> On 09/22/2016 04:51 AM, Jean Delvare wrote:
> > Hello,
> >
> > I bought an Asus PCE-N10 PCIe Wi-Fi N card to install in my wife's
> > computer. This morning it stopped working suddenly. Investigating the
> > kernel logs, the following error
Am 22.09.2016 um 05:34 schrieb bruce m beach:
>> We recently updated FW to GCC 6.2 which can detect more problems. So it
>> will be probably interesting for you to pick this patch out.
>
> Yes I saw the message by Adrian Chadd and tried tried to git clone the link
> he gave but that clearly wasn't
From: David Spinadel
Add support for drivers that implement static WEP internally, i.e.
expose connection keys to the driver in connect flow and don't
upload the keys after the connection.
Signed-off-by: David Spinadel
Signed-off-by: Johannes Berg
Signed-off-by: Luca Coelho
---
include/net/c
From: Oren Givon
Add two new PCI IDs for the 9560 series.
Signed-off-by: Oren Givon
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/pcie/drv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/drv.c
b/drivers/net/wireless/intel/iw
From: Johannes Berg
The upper bound IWL_RATE_COUNT_LEGACY should be used
with a >= check, rejecting the value itself; fix that.
Signed-off-by: Johannes Berg
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/mvm/tx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
From: Sara Sharon
The firmware has a new smart linker, and this table can now be
in ICCM or in SMEM. It is not hardcoded, but depends on code
size. Allow the full range.
Signed-off-by: Sara Sharon
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/mvm/utils.c | 2 +-
1 file cha
From: Emmanuel Grumbach
When we unshare a queue, the ADD_STA was not properly
initialised.
Signed-off-by: Emmanuel Grumbach
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/mvm/sta.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/inte
From: Luca Coelho
Hi,
Here's a series of patches that were pending in our internal tree.
I'm changing the process a bit. From now on I'll send the patches out
first for review and only later apply them on iwlwifi-next/master and
send a pull request. This will make reviews easier and will also
From: Luca Coelho
FW versions older than -17 for 3160 and 7260 and older than -22 for
newer NICs are not supported anymore. Don't load these versions
and remove code that handles them.
Signed-off-by: Luca Coelho
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/iwl-7000.c
From: Emmanuel Grumbach
This define should really be TX_CMD_SEC_KEY_FROM_TABLE
Signed-off-by: Emmanuel Grumbach
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/mvm/fw-api-tx.h | 4 ++--
drivers/net/wireless/intel/iwlwifi/mvm/tx.c| 2 +-
2 files changed, 3 insertions(
From: Johannes Berg
The various TFD/TB helpers have two code paths depending on the
type of TFD supported, with variable shadowing due to the new if
branches. Move the fall-through code into else branches to avoid
variable shadowing. While doing so, rename some of the variables
and do some other
From: Luca Coelho
We were assigning the return value of iwl_mvm_ctdp_command() to a
variable, but never checking it. If this command fails, we should not
allow the interface up process to proceed, since it is potentially
dangerous to ignore thermal management requirements.
Fixes: commit 5c89e7b
From: Sara Sharon
This is never really used anymore.
Signed-off-by: Sara Sharon
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/iwl-config.h | 1 -
drivers/net/wireless/intel/iwlwifi/mvm/ops.c| 46 -
2 files changed, 15 insertions(+), 32 deletion
From: Sara Sharon
Move the init_dbg check to earlier in the function to simplify the
code.
Signed-off-by: Sara Sharon
Signed-off-by: Luca Coelho
---
drivers/net/wireless/intel/iwlwifi/mvm/fw.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/d
Hi Larry,
On Thu, 22 Sep 2016 10:09:58 -0500, Larry Finger wrote:
> Do you build your own kernel, or are you using openSUSE's supplied version?
> If
> the latter, I will need to think how we might debug the issue. If the former,
> please add the attached patch.
The debug module is in place. Th
Hi all,
I'm having issues with broadcom's latest firmware / driver, version
6.30.163.46. Wireless is solid for about a minute, and then drops
completely. My research has led me to believe my chip (BCM4331) is no
longer supported under 6.30.X.X, or has a bug somewhere. I want to
roll back to the fi
On 23 September 2016 at 04:43, David Petrizze wrote:
> I'm having issues with broadcom's latest firmware / driver, version
> 6.30.163.46. Wireless is solid for about a minute, and then drops
> completely. My research has led me to believe my chip (BCM4331) is no
> longer supported under 6.30.X.X,
On 22 September 2016 at 16:09, Rafał Miłecki wrote:
> On 22 September 2016 at 14:24, Rafał Miłecki wrote:
>> I got the same problem again, but this time there was only 1 skb in my
>> flowring.
>> That resulted in less serial console messages and no reboot.
>>
>> It doesn't look good. brcmf_txfina
29 matches
Mail list logo