Hi Johannes,
On Wed, Aug 12, 2015 at 2:08 PM, Johannes Berg
johan...@sipsolutions.net wrote:
On Wed, 2015-08-12 at 11:36 -0700, Kobi Cohen-Arazi wrote:
Hi,
When loading a wifi driver that supports set_coalesce and running iw
show command:
$ iw ... coalesce show
It would always show
On 08/12/2015 10:51 PM, Sean Richards wrote:
On Aug 12, 2015, at 4:42 PM, Larry Finger larry.fin...@lwfinger.net wrote:
On 08/12/2015 02:15 PM, Richards, Sean wrote:
No I am sorry it's not obvious. I was told to report the bug to you. I did
so. I honestly don't know much about Linux. I
On Wed, 2015-08-12 at 11:36 -0700, Kobi Cohen-Arazi wrote:
Hi,
When loading a wifi driver that supports set_coalesce and running iw
show command:
$ iw ... coalesce show
It would always show coalesce as disabled.
I think the reason for this is that there are no coalesce rules
cached
in
(Resending because it failed to deliver to linux-wireless)
Hi,
This is the set up on my laptop:
- AR9565 wireless network adapter
- Acer Aspire V5-122P laptop - AMD A6-1450M
- Linux kernel built from sources v4.1.0-rc8
In config I changed CONFIG_ATH9K to be built as module. Here's the
snippet
On 08/12/2015 03:51 PM, Sean Richards wrote:
I was wondering if you could answer one more question for me. Would you mind
expanding on this comment??
It will taint your kernel
I am curious what you mean by that.
When you load a driver that is not open source with the corresponding GPL
On 08/12/2015 02:15 PM, Richards, Sean wrote:
No I am sorry it's not obvious. I was told to report the bug to you. I did
so. I honestly don't know much about Linux. I like using it and reported the
bug to help the community. I am sure I won't be the only one to purchase this
device and
On Aug 12, 2015, at 4:42 PM, Larry Finger larry.fin...@lwfinger.net wrote:
On 08/12/2015 02:15 PM, Richards, Sean wrote:
No I am sorry it's not obvious. I was told to report the bug to you. I did
so. I honestly don't know much about Linux. I like using it and reported
the bug to help
On Wed, 2015-08-12 at 14:13 -0700, Kobi Cohen-Arazi wrote:
So what you're saying is that at startup, drivers should have
coalesce _disabled_ (i.e. no rules for coalesce) ?
I think so, yes. It's a service that should be actively enabled, with
user-configured rules. Mechanism vs. policy, and
From: Johnny Kim johnny@atmel.com
This patch changes the type of gu8FlushedJoinReqDrvHandler with his real
data type becasue typecasting is not necessary. In result, typecasting
which is not necessary and some building warnings is removed.
Signed-off-by: Johnny Kim johnny@atmel.com
From: Johnny Kim johnny@atmel.com
The driver communicates with the chipset via the address of handlers
to distinguish async data frame. The SendConfigPkt function gets the
pointer address indicating the handlers as the last argument, but this
requires redundant typecasting and does not
From: Johnny Kim johnny@atmel.com
This patch replaces the void pointer type in the host interface
functions which process the message from host thread by the real data
type, tstrWILC_WFIDrv because the void pointer type as the arguments
is not clear and concise. In addition, typecasting to
This series of patch includes new design for 64 bits. The driver uses the
redundant typecasting to communicate with the chipset, which causes several
compile warnings.
However, this patch uses the real data type and removes unnecessary typecasting.
Also, the driver allocates the ID value to the
From: Johnny Kim johnny@atmel.com
The structure, WILC_WFIDrvHandle is used to save the pointer address
for the driver handler which is used throughout the driver but it's
not easy to understand what it means. In addition, it doesn't support
the 64 bit machine and also causes the warnings for
From: Johnny Kim johnny@atmel.com
This patch changes the void pointer member of the tstrHostIFmsg to the
real data type because the void pointer type is ambiguous and not
readable.
Signed-off-by: Johnny Kim johnny@atmel.com
Signed-off-by: Tony Cho tony@atmel.com
---
From: Miaoqing Pan miaoq...@qca.qualcomm.com
MAC/BB name is if the MAC/BB is unknown.
Signed-off-by: Miaoqing Pan miaoq...@qca.qualcomm.com
---
drivers/net/wireless/ath/ath9k/hw.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath9k/hw.c
On 07/26/2015 05:40 PM, Rafał Miłecki wrote:
On 20 July 2015 at 19:14, Arend van Spriel ar...@broadcom.com wrote:
On 07/19/2015 05:05 PM, Rafał Miłecki wrote:
On 10 July 2015 at 20:31, Arend van Spriel ar...@broadcom.com wrote:
This series comprises of following changes:
- support NVRAM
I am currently trying to stop packets for specific vifs.
This can easily be done if the IEEE80211_HW_QUEUE_CONTROL flag is set and using
ieee80211_stop_vif_queues and ieee80211_wake_vif_queues from util.c. But some
drivers/cards do not have this capability.
Currently, all vif queues map to the
There are three WMI_CHAN_INFO events reported per channel
in QCA99X0 firmware. First one is a notification at the begining
of the channel dwell time with cmd_flag as CHAN_INFO_START(cmd_flag = 0),
second one is a notification at the end of the dwell time with cmd_flag
CHAN_INFO_PRE_COMPLETE
The frequency at which cycle/rx_clear counters are running might
change from one target type to another. QCA99X0 is running the
counters at 150Mhz while QCA9888X and QCA6174 are running at 88Mhz.
Add a new entry to hw_params to store the target specific frequency
and use it in msecs conversion.
On Tue, Aug 11, 2015 at 12:25:53AM +0200, Adrien Schildknecht wrote:
rt2500usb_validate_eeprom() read data up to 0x6e (EEPROM_CALIBRATE_OFFSET)
but only 0x6a bytes has been allocated and read from the eeprom.
This lead to out-of-bound accesses and invalid values for
EEPROM_BBPTUNE_R17 and
Header format of 10.4 firmware phyerr event is not alligned
with pre 10.4 firmware. Introduce new wmi handlers to parse
10.4 firmware specific phyerror event header.
With changes covered in this patch, radar detection works on
qca99x0 hw 2.0 which uses 10.4 firmware.
Signed-off-by: Raja Mani
Existing phyerr event handlers directly uses phyerr header format
(ie, struct wmi_phyerr and struct wmi_phyerr_event) in the code
exactly on how firmware packs it. This is the problem in 10.4 fw
specific phyerr event handling where it uses different phyerror
header format. Before adding 10.4
On 12 August 2015 at 10:58, Arend van Spriel ar...@broadcom.com wrote:
On 07/26/2015 05:40 PM, Rafał Miłecki wrote:
On 20 July 2015 at 19:14, Arend van Spriel ar...@broadcom.com wrote:
On 07/19/2015 05:05 PM, Rafał Miłecki wrote:
On 10 July 2015 at 20:31, Arend van Spriel
No I am sorry it's not obvious. I was told to report the bug to you. I did
so. I honestly don't know much about Linux. I like using it and reported the
bug to help the community. I am sure I won't be the only one to purchase this
device and Put RedHat / Fedora on it.
Sean Richards
https://bugzilla.redhat.com/show_bug.cgi?id=1239050
Here is some of the information I copied from bugzilla
Product version: Lenovo Yoga 3 Pro-1370
Vendor: Lenovo
# rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Hi,
When loading a wifi driver that supports set_coalesce and running iw
show command:
$ iw ... coalesce show
It would always show coalesce as disabled.
I think the reason for this is that there are no coalesce rules cached
in cfg/netlink layers yet. (empty set of rules).
Is my understanding
This patch enables setting the module's debug options WARN and INFO in the
debugfs file 'wilc_debug_level'. This enables the user to enable logging
of warning and other information. Before this change writes to this debugfs
file sets only one option DGB. This is additional to the default option
On 08/12/2015 12:05 PM, Richards, Sean wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1239050
Here is some of the information I copied from bugzilla
Product version: Lenovo Yoga 3 Pro-1370
Vendor: Lenovo
# rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard
28 matches
Mail list logo
