Hi All,
I'm addressing to the maintainers of Ralink driver rt2800usb
(RT2870,RT3070) if still anybody alive.
To who can I send my inquiry?
Thanks
--
http://www.fastmail.com - Accessible with your email software
or over the web
Previously the meshcfg.rssi_threshold did not work with user_mpm=1.
Signed-off-by: Masashi Honma
---
net/mac80211/mesh.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/net/mac80211/mesh.c b/net/mac80211/mesh.c
index 6e7b6a0..281d834 100644
--- a/net/mac80211/mesh.
On 2017/03/16 19:03, Johannes Berg wrote:
I'm not really sure this is the right solution?
It seems to me that it should be a function of the path selection to
take this into account, not prohibiting the longer path entirely?
Right. To calculate metric with RSSI level is better solution than
th
Begin forwarded message:
Date: Fri, 17 Mar 2017 02:22:58 +
From: bugzilla-dae...@bugzilla.kernel.org
To: step...@networkplumber.org
Subject: [Bug 194903] New: After updating Kernel to 4.9.9 my wireless adapter
does not work
https://bugzilla.kernel.org/show_bug.cgi?id=194903
B
GAS_INTIAL_REQ should be GAS_INITIAL_REQ.
GAS_INTIAL_RSP should be GAS_INITIAL_RSP.
Improves readability of code.
Signed-off-by: Dylan Leggio
---
drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wil
GAS_INTIAL_REQ should be GAS_INITIAL_REQ.
GAS_INTIAL_RSP should be GAS_INITIAL_RSP.
Improves readability of code.
Signed-off-by: Dylan Leggio
---
drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wil
On Thu, Mar 16, 2017 at 05:51:12PM -0400, Dylan Leggio wrote:
> Signed-off-by: Dylan Leggio
I can't take patches without any changelog text at all, sorry.
greg k-h
From: Colin Ian King
The pmkid data is meant be be copied to the previous item in the
pmkidlist, however the code is just copying the data to itself because
the src index into pmkidlist is the same as the dst index into pmkidlist.
Fix this with i + 1 instead of i.
Detected by CoverityScan,CID#13
> Attach at just above the driver, before it ever gets to
> stations/vdevs, and ignore radiotap headers and/or add special
> processing for metadata like rx-info?
That'd be a different feature, perhaps more like XDP.
There anyway is no radiotap header at that point, but not changing
whether or n
On 03/16/2017 03:33 PM, Johannes Berg wrote:
Hi all,
Occasionally - we just had another case - people want to hook into
packets received and processed by the mac80211 stack, but because they
don't need all of them (e.g. not data packets), even adding a monitor
interface and bringing it up has to
Hi all,
Occasionally - we just had another case - people want to hook into
packets received and processed by the mac80211 stack, but because they
don't need all of them (e.g. not data packets), even adding a monitor
interface and bringing it up has too high a cost because SKBs need to
be prepared
Signed-off-by: Dylan Leggio
---
drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
index a37896fcd683..1bb63702c62
On Tuesday, March 14, 2017 9:51:52 PM EDT Arend van Spriel wrote:
> To support network namespace the driver must assure all created
> network interfaces are in the same namespace as the wiphy instance.
>
> Reported-by: Mark Asselstine
> Signed-off-by: Arend van Spriel
> ---
> Hi Mark,
>
> Pleas
We observed a SHUTDOWN command timeout during reboot stress test due to
a corner case firmware bug. It can lead to either a use-after-free +
OOPS (on either the adapter structure, or the 'card' structure) or an
abort (where, e.g., the PCI device is "disabled" before we're done
dumping the FW).
We
On 03/15/2017 08:46 AM, Kalle Valo wrote:
> From: Erik Stromdahl
>
> Since both SDIO and USB based chipsets will use different
nitpick, since the patch is separating the USB and SDIO support now, maybe you
want to remove the "USB" from the patch title?
> firmware from the PCIe and AHB chipsets
On Thu, Mar 16, 2017 at 12:38:57PM -0700, Brian Norris wrote:
> On Thu, Mar 16, 2017 at 11:41:15AM -0700, Brian Norris wrote:
> > On Thu, Mar 16, 2017 at 11:33:17AM -0700, Dmitry Torokhov wrote:
> > > You need to check this flag before queueing firmware dump work, and
> > > make sure it is not racy
Hi Dmitry and Amit,
On Thu, Mar 16, 2017 at 11:41:15AM -0700, Brian Norris wrote:
> On Thu, Mar 16, 2017 at 11:33:17AM -0700, Dmitry Torokhov wrote:
> > On Thu, Mar 16, 2017 at 03:58:52PM +0530, Amitkumar Karwar wrote:
> > > We observed a SHUTDOWN command timeout during reboot stress test
> > > du
Hi Dmitry,
On Thu, Mar 16, 2017 at 11:33:17AM -0700, Dmitry Torokhov wrote:
> On Thu, Mar 16, 2017 at 03:58:52PM +0530, Amitkumar Karwar wrote:
> > We observed a SHUTDOWN command timeout during reboot stress test
> > due to a corner case firmware bug. It leads to use-after-free on
> > adapter stru
On Thu, Mar 16, 2017 at 03:58:52PM +0530, Amitkumar Karwar wrote:
> We observed a SHUTDOWN command timeout during reboot stress test
> due to a corner case firmware bug. It leads to use-after-free on
> adapter structure pointer and crash.
>
> Let's add MWIFIEX_IFACE_WORK_DONT_RUN work flag to avoi
From: Johannes Berg
Date: Thu, 16 Mar 2017 10:51:55 +0100
> Here's the pull request you were waiting for. I went through all my
> pending patches but only this one is applicable for net.git at this
> time, so it's just a single one.
>
> Since I didn't have a current base, I forwarded to net.git
Hi All,
I'm addressing to the maintainers of Ralink driver rt2800usb (RT2870,
RT3070).
To who can I send my inquiry?
Thanks
--
Nikita N.
niki...@operamail.com
--
http://www.fastmail.com - Or how I learned to stop worrying and
love email again
The organizing committee would like to welcome back a repeat
platinum sponsor, Facebook!
Facebook has been a great supporter of the netdev community, we
thank them!
cheers,
jamal
On 2017-03-16 02:06, Ryan Hsu wrote:
On 03/15/2017 08:45 AM, Kalle Valo wrote:
From: Erik Stromdahl
This patch moves the HTC ctrl service connect from
htc_wait_target to htc_init.
This is done in order to make sure the htc ctrl service
is setup properly before hif_start is called.
The rea
Introduce a debugfs option to manually override the noise floor,
ignoring the automatically tuned noise floor of the driver/hw.
In my tests with a AR9580 based module and a tx99 5 MHz interferer,
I could tune the noisefloor to -95 dBm or above to allow communication
again. The automatic noise floo
This series contains two patches to enable channels in licensed bands.
Note that there are quite a few requirements to enable those:
* channels must be explicitly enabled using a licensed band kernel config
which contains a warning
* it depends on CFG80211_CERTIFICATION_ONUS
* users must ins
From: Ben Greear
Many chips support channels in licensed bands. Add support for those,
along with a corresponding kernel config option to disable them by
default. Note that these channels are not selectable even if the
option has been compiled unless the user modifies the regulatory
database to e
Many chips support channels in licensed bands. Add support for those,
along with a corresponding kernel config option to disable them by
default. Note that these channels are not selectable even if the
option has been compiled unless the user modifies the regulatory
database to explicitly enable th
On Thu, Mar 16, 2017 at 02:55:09PM +0100, Rafał Miłecki wrote:
> On 02/23/2017 07:30 PM, Rafał Miłecki wrote:
> > From: Rafał Miłecki
> >
> > So far we got only one function for loading firmware asynchronously:
> > request_firmware_nowait. It didn't allow much customization of firmware
> > loadin
Hello there,
I have the same problem as reported here.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627828
and here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629603
If I understood correctly (form 2nd link) the latest good kernel was 4.4.4
after 4.4.6 we have the problem.
On 02/23/2017 07:30 PM, Rafał Miłecki wrote:
From: Rafał Miłecki
So far we got only one function for loading firmware asynchronously:
request_firmware_nowait. It didn't allow much customization of firmware
loading process - there is only one bool uevent argument. Moreover this
bool also control
On Thu, Mar 16, 2017 at 10:57:00AM +0100, Rafał Miłecki wrote:
> On 23 February 2017 at 19:30, Rafał Miłecki wrote:
> > From: Rafał Miłecki
> >
> > So far we got only one function for loading firmware asynchronously:
> > request_firmware_nowait. It didn't allow much customization of firmware
> >
Application triggers periodic background scans when device is connected.
We will scan less number of channels per scan command so that data
traffic won't get affected.
Signed-off-by: Amitkumar Karwar
---
drivers/net/wireless/marvell/mwifiex/scan.c | 11 ---
1 file changed, 8 insertions(+
Sorry - this is the other half of my reply that I accidentally deleted
before sending...
> +static void flush_tx_skbs(struct ieee80211_sub_if_data *sdata)
> +{
> + struct ieee80211_if_mesh *ifmsh = &sdata->u.mesh;
> + struct mesh_tx_queue *tx_node;
> +
> + spin_lock_bh(&ifmsh->mesh_tx
We observed a SHUTDOWN command timeout during reboot stress test
due to a corner case firmware bug. It leads to use-after-free on
adapter structure pointer and crash.
Let's add MWIFIEX_IFACE_WORK_DONT_RUN work flag to avoid executing
any work scheduled after cancel_work_sync() call in teardown pat
Hi,
So I guess after all the discussion, you should amend the commit log a
bit, certainly at least to mention the hidden-node issue.
Regarding the patch itself, I'm not super happy with how big it is,
some additional comments below:
> +struct mesh_tx_queue {
> + struct list_head list;
> +
From: Johannes Berg
Add support for the HE MCSs in cfg80211 and also add userspace
API to nl80211 to send rate information out.
The bandwidth calculation is somewhat approximate to avoid all
the big tables that are otherwise necessary.
Signed-off-by: Johannes Berg
---
include/net/cfg80211.h
On Wed, 2017-03-15 at 16:25 +0800, Chun-Yeow Yeoh wrote:
> Yes, ath9k for mesh/AP running simultaneously in one single radio
> interface can do beaconing using different beacon interval. Mesh
> providing backhaul to user accessing via STA/AP mode.
Ok.
> > If that worked, then it'd be reasonable
Hi,
On Thu, 2017-03-16 at 10:57 +0900, Masashi Honma wrote:
> On some practical cases, it is useful to drop new node in the
> distance.
> Because mesh metric is calculated with hop count and without RSSI
> information, a node far from local peer and near to destination node
> could be used as best
On 23 February 2017 at 19:30, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> So far we got only one function for loading firmware asynchronously:
> request_firmware_nowait. It didn't allow much customization of firmware
> loading process - there is only one bool uevent argument. Moreover this
> b
On Thu, 2017-03-09 at 10:34 +0100, ondrej.lyso...@seznam.cz wrote:
> From: Ondřej Lysoněk
>
> Use setup_timer() and setup_deferrable_timer() to set the data and
> function timer fields. It makes the code cleaner and will allow for
> easier change of the timer struct internals.
>
Applied, thanks.
On Thu, 2017-03-16 at 10:57 +0900, Masashi Honma wrote:
> The rssi_threshold is defined as s32.
>
Doesn't really matter much, but does seem nicer - applied.
johannes
On 16 March 2017 at 10:36, Kalle Valo wrote:
> Rostyslav Khudolii wrote:
>> Channels 34/38/42/46 can only be used for compatibility with
>> old devices sold in Japan. Modern products, such as AR6003/AR6004
>> don't support these channels.
>> Keeping them in the upstream is error prone and require
Hi Dave,
Here's the pull request you were waiting for. I went through all my
pending patches but only this one is applicable for net.git at this
time, so it's just a single one.
Since I didn't have a current base, I forwarded to net.git first
and re-validated the patch there, but you might might
Rostyslav Khudolii wrote:
> Channels 34/38/42/46 can only be used for compatibility with
> old devices sold in Japan. Modern products, such as AR6003/AR6004
> don't support these channels.
> Keeping them in the upstream is error prone and requires full
> network stack support.
> A custom patch sho
Erik Stromdahl writes:
>> There seems to be same pattern for reading four bytes, what if we should
>> add a helper for that? Something like ath10k_sdio_read32()? It could
>> handle the kmalloc and switch endianess also.
>>
>> But please don't make any chances to sdio.c for the moment, let me
>> s
I failed to notice that commit 523f6701dbab ("ath10k: update available channel
list for 5G radio") added two new warnings:
drivers/net/wireless/ath/ath10k/mac.c:3129:6: warning: symbol
'ath10k_mac_update_channel_list' was not declared. Should it be static?
drivers/net/wireless/ath/ath10k/mac.c:31
Mohammed Shafi Shajakhan wrote:
> From: Mohammed Shafi Shajakhan
>
> Fetch target operating channel during potential radar detection when
> the interface is just brought up, but no channel is assigned from
> userspace. In this scenario rx_channel may not be having a valid pointer
> hence fetch t
Zefir Kurtisi wrote:
> Doing so enables the FFT generation without prior
> configuration, leading to an IRQ storm caused by
> invalid (or at least unwanted) PHY errors.
>
> Signed-off-by: Zefir Kurtisi
Patch applied to ath-next branch of ath.git, thanks.
45c3d550b068 ath9k: don't trigger spect
Colin Ian King wrote:
> From: Colin Ian King
>
> The check on ret for an error is redundant because it is already been
> checked for non-zero earlier on and ret is never non-zero at this point.
> Fix this by removing the redundant check and error message.
>
> Detected by CoverityScan, CID#13571
c_tr...@qti.qualcomm.com wrote:
> From: Tamizh chelvam
>
> If a 5 GHz radio is calibrated for operation in both
> the low band (channels 36 to 64) and high band(channels 100 to 169),
> hardware allows operations in all the listed channels. However,
> if the chip has been calibrated only for the l
Mohammed Shafi Shajakhan wrote:
> From: Mohammed Shafi Shajakhan
>
> If DFS is not enabled in hostapd (ieee80211h=0) DFS channels shall
> not be available for use even though the hardware may have the capability
> to support DFS. With this configuration (DFS disabled in hostapd) trying to
> brin
Amitkumar Karwar wrote:
> Ganapathi & Xinming are starting to take a more active role in the
> mwifiex driver maintainership here onwards on account of organizational
> changes.
>
> CC: Xinming Hu
> CC: Ganapathi Bhat
> Signed-off-by: Amitkumar Karwar
> Signed-off-by: Nishant Sarmukadam
> Sig
Brian Norris wrote:
> When PCIe FLR support was added, much of the remove/release code for
> PCIe was migrated to ->down_dev(), but ->down_dev() is never called for
> device removal. Let's refactor the cleanup to be done in both cases.
>
> Also, drop the comments above mwifiex_cleanup_pcie(), bec
Daniel Golle wrote:
> From: Roman Yeryomin
>
> Basic support for MT7620 built-in wireless radio was added to
> OpenWrt in r41441. It has seen some heavy cleaning and refactoring
> since in order to match the Kernel's code quality standards.
>
> Signed-off-by: Roman Yeryomin
> Signed-off-by: Da
Luciano Coelho wrote:
> From: Sara Sharon
>
> When a station is asleep, the fw will set it as "asleep".
> All queues that are used only by one station will be stopped by
> the fw.
>
> In pre-DQA mode this was relevant for aggregation queues. However,
> in DQA mode a queue is owned by one statio
Johannes Berg writes:
>> 1. Modify cfg80211 driver patch to introduce ability to boot from
>> card's internal flash rather then over PCIe only. This will hopefully
>> unblock driver itself.
>
> This is good, and I think that'll be OK for the driver.
I'm thinking the same.
>> 2. Work internally
56 matches
Mail list logo
