On Tue, Jul 7, 2015 at 8:21 AM, SF Markus Elfring
wrote:
>>> From: Markus Elfring
>>> Date: Sat, 27 Jun 2015 15:56:57 +0200
>>
>> Why is this in the body of the email?
>
> Does the canonical patch format support to preserve
> specific details about a shown commit by specification
> of fields like
>> From: Markus Elfring
>> Date: Sat, 27 Jun 2015 15:56:57 +0200
>
> Why is this in the body of the email?
Does the canonical patch format support to preserve
specific details about a shown commit by specification
of fields like "Date" and "From" in the message body?
Regards,
Markus
--
To unsub
AR_PHY_TST_ADC is BB ADC sample register, it doesn't depend on other BB
registers. Get non zero data if it has the ADC values.
Thanks,
Miaoqing
-Original Message-
From: Felix Fietkau [mailto:n...@openwrt.org]
Sent: Monday, July 06, 2015 6:32 PM
To: Pan, Miaoqing; linvi...@tuxdriver.c
On Tue, Jun 30, 2015 at 05:34:38PM +0900, Dean Lee wrote:
> Signed-off-by: Dean Lee
delete what unused value? And why?
Please rework this whole series and resend.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord..
On Tue, Jun 30, 2015 at 05:34:37PM +0900, Dean Lee wrote:
> modify it
modify what?
--
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
On Fri, Jun 26, 2015 at 04:43:44PM +0200, Luis de Bethencourt wrote:
> Patches to be applied on top of
> https://patchwork.kernel.org/patch/6655831/
I don't use patchwork, and when on an airplane with no internet access
(like right now), a url provides no context at all. Always use email
subject
On Sat, Jun 27, 2015 at 04:36:14PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 27 Jun 2015 15:56:57 +0200
Why is this in the body of the email? Please fix your email client or
just use git send-email properly.
--
To unsubscribe from this list: send the line "unsubscribe
On Sat, Jun 27, 2015 at 04:37:24PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sat, 27 Jun 2015 16:00:59 +0200
Again, please fix.
>
> The kfree() function was called in two cases by the mac_ioctl() function
> during error handling even if the passed variable did not contain a
On Tue, Jun 30, 2015 at 05:34:34PM +0900, Dean Lee wrote:
> delete odd structure and rework it.
what do you mean by "rework it"? It looks like you just made it a void
* everywhere, which is what I explicitly said to not do.
sorry, can't take this.
greg k-h
--
To unsubscribe from this list: send
>Jonas Gorski wrote:
>
> Hi,
>
> On Fri, Jul 3, 2015 at 8:10 AM, David Lin wrote:
> > The Linux driver for WRT1900AC. The work was initially developed as
> > part of openwrt effort and maintained on https://github.com/kaloz/mwlwifi.
> >
> > This is still work in progress, with 8864 chipset more
On Mon, 6 Jul 2015 20:37:38 +0200
Salvatore De Paolis wrote:
> Hi all,
>
> after updating the kernel and udev plus other packages I am not able anymore
> to let my PCI wireless card works.
>
> The device is listed as RT2561/RT61 (no rev. B)
>
> After the update when issuing a "up" I get an err
On 07/06/2015 11:46 AM, Richard Palethorpe wrote:
> Bruno, that surprises me somewhat because I have got IBSS mode to work
> on kernel 4.0+. Are you using a slightly older kernel?
I'm using kernel 3.18 with wireless drivers from backports in OpenWRT
CC, so it should be pretty recent...
I wonder t
Hi all,
after updating the kernel and udev plus other packages I am not able anymore to
let my PCI wireless card
works.
The device is listed as RT2561/RT61 (no rev. B)
After the update when issuing a "up" I get an error like: rt61pci agent aborted
rt2561s (not found?)
I have the firmware-rali
Fixed explicit initialization of global pointer variable.
Signed-off-by: Daniel Machon
---
drivers/staging/wilc1000/host_interface.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wilc1000/host_interface.c
b/drivers/staging/wilc1000/host_interface.c
inde
I have applied more restrictive rule for (5490-5590) and allowed 80Mhz
for (5650 - 5730).
The patch has been uploaded in another thread.
http://lists.infradead.org/pipermail/wireless-regdb/2015-July/000858.html
Thanks.
On Mon, Jul 6, 2015 at 7:40 AM, Zefir Kurtisi wrote:
> On 07/06/2015 03:27 P
Related regulation:
http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10971.html#s6.2.3
Frequency Bands 5470-5600 MHz and 5650-5725 MHz
Until further notice, devices subject to this section [i.e. Wifi device
supporting 5 GHz bands] shall not be capable of transmitting in the band
5600-5650 MHz. This
Subject says it all...
--
John W. LinvilleSomeday the world will need a hero, and you
linvi...@tuxdriver.com might be all we have. Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.ke
On 07/06/2015 03:27 PM, Seth Forshee wrote:
> On Fri, Jul 03, 2015 at 05:01:20PM +0200, Zefir Kurtisi wrote:
>> On 07/03/2015 04:20 PM, Wei Zhong wrote:
>> [...]
>> From your other post:
>
> - (5490 - 5730 @ 160), (24), DFS
> + (5490 - 5590 @ 80), (24), DFS
On Fri, Jul 03, 2015 at 05:01:20PM +0200, Zefir Kurtisi wrote:
> On 07/03/2015 04:20 PM, Wei Zhong wrote:
> > On Fri, Jul 3, 2015 at 4:08 AM, Zefir Kurtisi
> > wrote:
> >>
> >> On 07/02/2015 07:44 AM, Wei Zhong wrote:
> >>> commit 2fef4cad8a1bd9cbbf178e59a1b3ca672b057095
> >>> Author: Wei Zhong
> > struct wireless_dev *wdev;
> > - struct wiphy *wiphy = wiphy_idx_to_wiphy(rdev->wiphy_idx);
> > + struct cfg80211_registered_device *rdev = wiphy_to_rdev(wiphy);
> >
> > ASSERT_RTNL();
> >
> Seems after this patch we hit ASSERT_RTNL() when setup ibss (seems
> same fo
On 6 May 2015 at 15:28, Arik Nemtsov wrote:
> The GO_CONCURRENT regulatory definition can be extended to station
> interfaces requesting to IR as part of TDLS off-channel operations.
> Rename the GO_CONCURRENT flag to IR_CONCURRENT and allow the added
> use-case.
>
> Change internal users of GO_CO
On Sat, Jul 4, 2015 at 3:15 AM, Taehee Yoo wrote:
> 2015-07-03 18:59 GMT+09:00 Bruno Randolf :
>> On 07/03/2015 10:34 AM, Richard Palethorpe wrote:
>>> Hello Taehee,
>>>
>>> I have been experimenting with MESH mode on kernel 4.0.7. It is
>>> sending beacons out, but is unable to establish a connec
On 2015-07-03 10:28, miaoq...@qti.qualcomm.com wrote:
> From: Miaoqing Pan
>
> We measured the ADC-based entropy in 3 ways, Shannon entropy,
> collision entropy, and directly measured min-entropy. Entropy is
> in bits per 16 bit value,
>---
>Shannon | collision | m
On 07/03/2015 08:38 PM, Johannes Berg wrote:
> On Fri, 2015-07-03 at 18:51 +0200, Zefir Kurtisi wrote:
>> Folks,
>>
>> I have difficulties using iw for a specific use case or fail to
>> understand the documentation correctly.
>>
>> My platform is a recent OpenWRT, running ath9k.
>>
>> First use ca
linux/device.h should be included using <>, not ""
since it is not local include
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/wil_platform.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/wil6210/wil_platform.c
b/drivers/n
Use function wil_fw_error_recovery() instead of inline equivalent code
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/main.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ath/wil6210/main.c
b/drivers/net/wireless/ath/wil6210/
Driver report supported TSO (v4 & v6) offload
in addition to previously supported features. In data path
skbs are checked for non-zero gso_size, and when detected sent
to additional function for processing TSO SKBs. Since HW does not
fully support TSO, additional effort is required from the driver.
There are 2 versions of boot loader struct: v0 and v1.
In the v1, boot loader build version added; as well as
RF status.
Support both versions.
Boot loader structure v1 has RF status; ignore RF error if firmware
not going to be loaded; driver can still be used to interact with the HW
Signed-off-
Print channel survey results on the debugfs. New entry
named "survey"
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/debugfs.c | 60 ++
1 file changed, 60 insertions(+)
diff --git a/drivers/net/wireless/ath/wil6210/debugfs.c
b/drivers/net/wi
Multiple del_station requests may be sent to the driver by the
supplicant when turning down AP. This may overflow mailbox
between the FW and ucode
Wait till disconnect of one STA completed before sending next command.
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/wmi.c
From: Dedy Lansky
FW is allowed to generate WMI events that are not handled by this driver.
Treat such case as warning instead of error.
Signed-off-by: Dedy Lansky
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/wmi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
When performing Rx reordering, count skb's dropped
per reorder buffer; and print dropped packets count
on the "stations" debugfs entry
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/debugfs.c| 2 +-
drivers/net/wireless/ath/wil6210/rx_reorder.c | 2 ++
drivers/net/wi
Check event length;
hex dump both Rx and Tx frames
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/wmi.c | 54 +++---
1 file changed, 44 insertions(+), 10 deletions(-)
diff --git a/drivers/net/wireless/ath/wil6210/wmi.c
b/drivers/net/wireless
ACS is implemented by registering to QCA vendor ACS sub command.
On receive of the command from hostapd, driver issues passive
scan command and block until scan results are available.
When received, the results are sent up using QCA vendor ACS
results event
Signed-off-by: Vladimir Shulman
Signed-
When loading with debug_fw flag, do not bail out on
unknown chipId
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/main.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wireless/ath/wil6210/main.c
b/drivers/net/wireless/ath/wil6210/
To prevent race when connect flow may run in parallel with
the disconnect event.
Scenario leading to the bug is: while running connect flow on the AP,
STA sends disconnect. log follows.
<7>[ 668.736269] wil6210 :01:00.0: wlan0: DBG[ WMI]Configure for
connection CID 1
<7>[ 668.736269] wil62
In the debugfs, there is "ulong" attribute printing. It is used for
bitmap printing, and more appropriate format would be hexadecimal,
not decimal.
Signed-off-by: Vladimir Kondratiev
---
drivers/net/wireless/ath/wil6210/debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Several new features introduced:
- TSO improves throughput on Tx side on systems with weak CPU
- ACS chooses best channel automatically when starting AP
- support for the new boot loader
Bug fixes:
- "wait for del_station to complete"
- "hold wil->mutex while managing vrings"
The rest are small f
38 matches
Mail list logo
