On Wed, 2014-11-26 at 11:07 +0200, Jukka Rissanen wrote:
An attribute NL80211_ATTR_SOCKET_OWNER can be set by the scan initiator.
If present, the attribute will cause the scan to be stopped if the client
dies.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
Hi,
v7:
-
I'm sorry this took so long - I was AFK during weekend and had
to deal with a huge backlog after that. Now it is all sorted.
23.11.2014 12:43, Arend van Spriel wrote:
On 19-11-14 22:00, Michael Tokarev wrote:
[]
Well, it shows tx looks ok, but with download there is not much of that
going on.
On Wed, 2014-11-26 at 12:30 +0200, Jukka Rissanen wrote:
Just some examples:
* don't synchronize_rcu() after assignment - what did you do that for?
Following the examples described in Documentation/RCU/whatisRCU.txt
Hmm, I don't think that documentation says that - was where you took it
On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez mcg...@suse.com wrote:
Please rename to REGULATORY_IGNORE_STALE_KICKOFF, also please add
some information about the amount current of grace period used,
and types of interfaces supported. Since this is a regulatory flag
this information will
Hello!
I installed Linux Mint Quiana in my computer.
My computer is old and it have D-link DWL-G132 (wireless) to navigate at
internet, ready as research, it use driver ar5523.
I saw the log archive (Kernel, dmesg) and all second I receive the message:
[ 38.094218] usb 2-8: RX: wrong xfer
On Tue, Nov 25, 2014 at 10:28 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov 23, 2014 at 05:02:21PM +0200, Arik Nemtsov wrote:
From: Jonathan Doron j...@wizery.com
Allow usermode to query wiphy-specific regd info, for drivers that use
wiphy-specific regulatory management.
Use the
On 26 November 2014 at 12:07, Avinash Patil pat...@marvell.com wrote:
From: Bing Zhao bz...@marvell.com
This patch adds new API to handle scatter gather aggregation.
Why is this needed?
Signed-off-by: Bing Zhao bz...@marvell.com
Signed-off-by: Avinash Patil pat...@marvell.com
Use provided timeout value in rt2x00usb_vendor_request() instead
of iterating REGISTER_BUSY_COUNT times.
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
---
drivers/net/wireless/rt2x00/rt2x00usb.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git
Waiting 500ms for register access is too long, decrease this value
to 100ms.
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
---
drivers/net/wireless/rt2x00/rt2x00usb.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/rt2x00/rt2x00usb.h
This reverts commit 2ad69ac5976191e9bb7dc4044204a504653ad1bb. It
causes wireless device disappear when we get -EPROTO error form USB
request. I encounter such situation occasionally when resume form
suspend with RT3070 adapter:
[ 289.619985] ieee80211 phy0: rt2x00usb_vendor_request: Error -
Because of delays on USB we do not have to iterate so many times on
USB hardware when waiting for H/W register become valid.
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
---
drivers/net/wireless/rt2x00/rt2500usb.c | 8
drivers/net/wireless/rt2x00/rt2x00.h| 5 -
On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov 23, 2014 at 05:02:19PM +0200, Arik Nemtsov wrote:
When the regulatory settings change, some channels might become invalid.
Disconnect interfaces acting on these channels, after giving userspace
code a grace
On Wed, Nov 26, 2014 at 05:06:37PM +0200, Arik Nemtsov wrote:
On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov 23, 2014 at 05:02:19PM +0200, Arik Nemtsov wrote:
When the regulatory settings change, some channels might become invalid.
Disconnect
On Wed, Nov 26, 2014 at 10:39 AM, Arik Nemtsov a...@wizery.com wrote:
On Wed, Nov 26, 2014 at 5:28 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Wed, Nov 26, 2014 at 05:06:37PM +0200, Arik Nemtsov wrote:
On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov
On Wed, Nov 26, 2014 at 11:43 AM, Arik Nemtsov a...@wizery.com wrote:
On Tue, Nov 25, 2014 at 10:28 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sun, Nov 23, 2014 at 05:02:21PM +0200, Arik Nemtsov wrote:
From: Jonathan Doron j...@wizery.com
Allow usermode to query wiphy-specific regd info,
On Wed, Nov 26, 2014 at 11:49 AM, Arik Nemtsov a...@wizery.com wrote:
On Wed, Nov 26, 2014 at 6:47 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Wed, Nov 26, 2014 at 11:43 AM, Arik Nemtsov a...@wizery.com wrote:
On Tue, Nov 25, 2014 at 10:28 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On
On 11/26/14 12:29 PM, Oleksij Rempel wrote:
Am 26.11.2014 um 01:28 schrieb David Lechner:
On 7 July 2014 17:08, Oleksij Rempel linux@ wrote:
/ Am 07.07.2014 15:40, schrieb Anders Darander:/
/ On 4 July 2014 18:54, Oleksij Rempel linux@ wrote:/
/ Am 04.07.2014
On Thu, Nov 20, 2014 at 11:34 PM, Larry Finger
larry.fin...@lwfinger.net wrote:
I have reproduced the problem, but I do not yet know the fix. Please file a
bug report at bugzilla.kernel.org on this problem. Be sure to mark it as a
regression, and assign it to me. When I find the fix, being able
On Tue, Nov 11, 2014 at 03:28:57PM +0530, Sanjeev Sharma wrote:
This is a patch to the rtw_cmd.c file that fixes following
Error.
ERROR: that open brace { should be on the previous line
This patch does much more than that :(
--
To unsubscribe from this list: send the line unsubscribe
I will be travelling for about 10 days starting tomorrow.
Email will be read and patches will be reviewed, but my response
time will be a little bit longer.
I've purged patchwork of every patch I can apply right now, the two in
there right now require either an expert review or a response to
When the regulatory settings change, some channels might become invalid.
Disconnect interfaces acting on these channels, after giving userspace
code a grace period to leave them.
This mode is currently opt-in, and not all interface operating modes are
supported for regulatory-enforcement checks.
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can distinguish
them as such.
Signed-off-by: Arik Nemtsov
From: Jonathan Doron j...@wizery.com
Add a new regulatory flag that allows a driver to manage regdomain
changes/updates for its own wiphy.
A self-managed wiphys only employs regulatory information obtained from
the FW and driver and does not use other cfg80211 sources like
beacon-hints,
If a wiphy-idx is specified, the kernel will return the wiphy specific
regdomain, if such exists. Otherwise return the global regdom.
When no wiphy-idx is specified, return the global regdomain as well as
all wiphy-specific regulatory domains in the system, via a new nested
list of attributes.
On Wed, Nov 26, 2014 at 10:56:25PM +0200, Arik Nemtsov wrote:
When the regulatory settings change, some channels might become invalid.
Disconnect interfaces acting on these channels, after giving userspace
code a grace period to leave them.
This mode is currently opt-in, and not all
Dave,
Please pull this little batch of fixes intended for the 3.18 stream...
For the iwlwifi one, Emmanuel says:
Not all the firmware know how to handle the HOT_SPOT_CMD.
Make sure that the firmware will know this command before
sending it. This avoids a firmware crash.
Along with that, Larry
On Wed, Nov 26, 2014 at 4:35 PM, Luis R. Rodriguez mcg...@suse.com wrote:
We're not checking here if this was a managed wiphy or not, we
want userspace to be able to tell if a wiphy was managed or not.
Ah I see what you did, yes that is what I wanted but since you allowed
for self managed
On 26 November 2014 at 00:12, Sergey Ryazanov ryazanov@gmail.com wrote:
Manufacturer of my device is Broadcom. It seems that either the hardware or
the driver doesn't support setting and getting sensitivity. I need to know
if there exists a device and/or device driver that support this
On Wed, Nov 26, 2014 at 11:43 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Wed, Nov 26, 2014 at 4:35 PM, Luis R. Rodriguez mcg...@suse.com wrote:
We're not checking here if this was a managed wiphy or not, we
want userspace to be able to tell if a wiphy was managed or not.
Ah I see what
Michal Kazior michal.kaz...@tieto.com writes:
2. Have a dedicatd pci-specific structure:
struct ath10k_pci_supported_chip {
u16 dev_id;
u32 chip_id;
};
struct ath10k_pci_supported_chip ath10k_pci_supported_chips[] = {
{ QCA988X_2_0_DEVICE_ID, QCA988X_HW_2_0_CHIP_ID_REV },
When the regulatory settings change, some channels might become invalid.
Disconnect interfaces acting on these channels, after giving userspace
code a grace period to leave them.
This mode is currently opt-in, and not all interface operating modes are
supported for regulatory-enforcement checks.
On 27 November 2014 at 08:30, Kalle Valo kv...@qca.qualcomm.com wrote:
Michal Kazior michal.kaz...@tieto.com writes:
2. Have a dedicatd pci-specific structure:
struct ath10k_pci_supported_chip {
u16 dev_id;
u32 chip_id;
};
struct ath10k_pci_supported_chip
If a device has self-managed regulatory, insist on returning the wiphy
specific regdomain if a wiphy-idx is specified. The global regdomain is
meaningless for such devices.
Also add an attribute for self-managed devices, so usermode can distinguish
them as such.
Signed-off-by: Arik Nemtsov
From: Jonathan Doron j...@wizery.com
Add a new regulatory flag that allows a driver to manage regdomain
changes/updates for its own wiphy.
A self-managed wiphys only employs regulatory information obtained from
the FW and driver and does not use other cfg80211 sources like
beacon-hints,
If a wiphy-idx is specified, the kernel will return the wiphy specific
regdomain, if such exists. Otherwise return the global regdom.
When no wiphy-idx is specified, return the global regdomain as well as
all wiphy-specific regulatory domains in the system, via a new nested
list of attributes.
35 matches
Mail list logo
