a bunch more info about the actual
rates instead of just the rate idx?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord
On 03/11/2015 02:31 PM, Arend van Spriel wrote:
On 03/11/15 22:07, Ben Greear wrote:
When using the user-space transport, the netlink frame sent to user-space
has a rate index and retry count, and nothing else. Is there a
reliable way to know in user-space what index maps to what actual rate
;
u32 flags = 0;
+ /* this one needs to be done in software */
+ if (key-cipher == WLAN_CIPHER_SUITE_AES_CMAC)
+ return 1;
+
if (key-keyidx WMI_MAX_KEY_INDEX)
return -ENOSPC;
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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
with 16 retries each', so that users know
what
number is what?
Thanks,
Ben
/*
* Use insanely high numbers to make sure that the firmware implementation
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send
?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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 02/25/2015 11:10 AM, Johannes Berg wrote:
On Wed, 2015-02-25 at 10:51 -0800, Ben Greear wrote:
Is there a table somewhere that explains how many chains are used by each
rate?
mcsindex.com?
What about OFDM and CCK. Are those always 1 chain?
Thanks,
Ben
--
Ben Greear gree
,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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 02/24/2015 02:14 AM, Johannes Berg wrote:
On Mon, 2015-02-23 at 09:38 -0800, Ben Greear wrote:
This doesn't really seem right - essentially it means that whatever you
just gave to userspace is now completely useless?
It seems skb_orphan() could/should be put here.
I don't understand
On 02/24/2015 06:34 AM, Johannes Berg wrote:
On Tue, 2015-02-24 at 06:28 -0800, Ben Greear wrote:
If there is no status to return, then why would user-space call back at all?
Should user-space *always* return a status even when not requested to?
I'd certainly expect so from hwsim.
I
On 02/24/2015 02:11 AM, Johannes Berg wrote:
On Mon, 2015-02-23 at 09:43 -0800, Ben Greear wrote:
This seems a bit strange - don't we already tag packets with the
frequency? Why would you need the channel change separately? What does
that even mean? Depending on how you use this it could
On 02/23/2015 08:08 AM, Johannes Berg wrote:
On Tue, 2015-02-10 at 10:25 -0800, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
Otherwise, skb is not cleaned up until there is some timeout
and the tx-queue quickly becomes overly full.
+++ b/drivers/net/wireless
:00 wlan1: STA 00:21:6a:5f:3f:c2 IEEE 802.11: authenticated
Feb 18 09:31:00 hostapd: wlan1: STA 00:21:6a:5f:3f:c2 IEEE 802.11:
authenticated
Feb 18 09:31:00 wlan1: STA 00:1f:3b:11:b1:25 IEEE 802.11: associated (aid 8)
Feb 18 09:31:00 wlan1: AP-STA-CONNECTED 00:1f:3b:11:b1:25
Thanks,
Ben
--
Ben
) + \
(TARGET_10X_NUM_VDEVS))
--
1.9.1
--
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
--
Ben Greear gree
On 02/15/2015 05:40 AM, Kalle Valo wrote:
(Adding linux-wireless)
Ben Greear gree...@candelatech.com writes:
In AP mode, it seems that 3.17-ish kernels (at least) always set station kickout
to hard-coded value of 50.
Is this something that should be configurable? Maybe a module parameter
);
config.rx_timeout_pri_vo = __cpu_to_le32(TARGET_10X_RX_TIMEOUT_LO_PRI);
--
1.9.1
--
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
--
Ben Greear gree
On 02/11/2015 10:55 PM, Michal Kazior wrote:
On 11 February 2015 at 23:25, Ben Greear gree...@candelatech.com wrote:
On 02/10/2015 09:01 AM, Ben Greear wrote:
I've hacked CT firmware to do a flush of all vdevs itself when it detects WMI
hang.
I don't have a good test bed to reproduce
On 02/10/2015 09:01 AM, Ben Greear wrote:
I've hacked CT firmware to do a flush of all vdevs itself when it detects WMI
hang.
I don't have a good test bed to reproduce the problem reliably, but I should
know
after a few days if the flush works at all. If not, then it's a moot point
On 02/09/2015 10:09 PM, Michal Kazior wrote:
On 9 February 2015 at 17:03, Ben Greear gree...@candelatech.com wrote:
On 02/08/2015 10:24 PM, Michal Kazior wrote:
On 6 February 2015 at 17:15, Ben Greear gree...@candelatech.com wrote:
[...]
At least in my tests, I could continue
to receive
On 02/08/2015 10:24 PM, Michal Kazior wrote:
On 6 February 2015 at 17:15, Ben Greear gree...@candelatech.com wrote:
On 02/06/2015 04:05 AM, Michal Kazior wrote:
It makes little sense to continue and let
firmware-host state become inconsistent if a WMI
command can't be submitted to firmware
it is properly going to the
netlink socket and user-space app.
If not this, any other ideas what I might be missing?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line unsubscribe linux-wireless
unresponsive,
restarting..\n);
+ queue_work(ar-workqueue, ar-restart_work);
+ }
+ }
+
return ret;
}
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line
how to go about it?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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
On 02/04/2015 12:37 AM, Kalle Valo wrote:
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
In case firmware fails to start the scan, then complete
the start condition and clean up so that driver does not
block on timeout.
Signed-off-by: Ben Greear gree
. Is there anything
we could improve so that we can have fewer acks and still get
good tcp stack behaviour?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body
change the
'wait-for-3-seconds' timeout to 3 1-second timeouts, and
on second timeout force a flush, ignoring tx-credits if
required? That may not be pretty, but seems better than resetting
firmware if it works.
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http
this firmware.
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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
Sorry about the resends...had mail-server issue, should be resolved now.
Thanks,
Ben
On 01/12/2015 11:29 AM, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
In case firmware fails to start the scan, then complete
the start condition and clean up so that driver does
wonder if similar wb() is needed in the firmware somewhere?
Thanks,
Ben
On 01/09/2015 04:36 PM, Ben Greear wrote:
I added this to my tree (and a bunch more debug stuff to track
CE transport-ids), and I've done about 4500 station reconnects over
the last 2 hours and no tx-credits hang issue so far
;
}
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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 12/10/2014 10:33 AM, poh wrote:
On 12/05/2014 07:59 PM, Ben Greear wrote:
On 12/05/2014 09:16 AM, Peter Oh wrote:
Setting fragmentation threshold has not been supported by
any of firmware versions, hence unregister the callback and
remove the function.
How hard is it to just fix
worried.
Johannes mentioned me that this is not supported so I am reluctant to
take these. Unless I'm missing something, of course.
I did test the code, and it seems to work fine. But, I could
be missing some subtle issues.
Any idea how this is supposed to be done?
Thanks,
Ben
--
Ben
On 11/22/2014 07:28 AM, Kalle Valo wrote:
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
There are not many of these messages producted by the
firmware, but they are generally fairly useful, so print
them at info level.
Signed-off-by: Ben Greear gree
at least some of this,
but it's a bit free-form to program against...
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord...@vger.kernel.org
On 11/06/2014 04:47 PM, Ben Greear wrote:
On 11/06/2014 11:57 AM, Ben Greear wrote:
I have uploaded the latest CT version of the ath10k firmware.
http://www.candelatech.com/ath10k.php
This firmware fixes bugs in raw-tx mode, though probably only
non-encrypted frames can be sent
and putting everything else into the skb-data.
^^ typo?
I didn't look at the rest...
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord
: 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
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send
On 09/23/2014 02:17 PM, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
When re-associating a station, the nss was set back to
maximum value even if user had configured small number
of tx chains. So, pay attention to user's config in
this case as well.
Looks like
they be mentioned in the policy struct like the other attributes?
Thanks for fixing that!
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line unsubscribe linux-wireless in
the body of a message to majord
tool is creating the phys, then it can know ahead of time the
names
and match the events that way.
I'm not taking sides on your particular patch, but those features made my
tool a lot easier to write and more efficient.
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc
:
* #{ IBSS } = 1, #{ managed, AP, mesh point, P2P-client,
P2P-GO } = 2048,
total = 2048, #channels = 1
* #{ AP } = 8,
total = 8, #channels = 1, radar detect widths: { 20 MHz
(no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }
Thanks,
Ben
--
Ben Greear
From what I can tell, when hwsim sends frames to wmediumd using netlink
sockets,
it does not include any channel/frequency information in the netlink packet.
Any reason not to add that?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
On 10/23/2014 10:19 AM, Johannes Berg wrote:
On Thu, 2014-10-23 at 09:53 -0700, Ben Greear wrote:
From what I can tell, when hwsim sends frames to wmediumd using netlink
sockets,
it does not include any channel/frequency information in the netlink packet.
Any reason not to add that?
I
On 10/21/2014 01:10 PM, Ben Greear wrote:
On 10/21/2014 12:31 PM, Johannes Berg wrote:
/* give it a proper name */
- dev_set_name(rdev-wiphy.dev, PHY_NAME %d, rdev-wiphy_idx);
+ if (requested_name requested_name[0]) {
+ struct cfg80211_registered_device *rdev2
, digits;
+
+/* Code below is from cfg80211_dev_rename */
can you refactor this then please?
I'll see what I can do on this, as well as take care of
the rest of the comments.
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
) */
ATH10K_FW_FEATURE_CT_RXSWCRYPT = 6,
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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
On 10/17/2014 11:53 PM, Johannes Berg wrote:
On Fri, 2014-10-17 at 13:12 -0700, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
Otherwise, it can be very difficult to know which is which
if you are trying to do detailed testing.
Having just implemented something
aa6eab9d17a0b3468075ff7c1abfee2ccfcb521e
e15af8b46ce047c8b46177e2d4cf74a4590a2181 M drivers
I will be happy to test patches if anyone has a suggested fix or needs
debug output...
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from
.
I do not see that whitespace problem in the patch I posted.
I will change it to is_valid_ether_addr as you suggested.
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line unsubscribe linux
() is to determine
whether iw provided a mac address or not.
Well, I guess either way is fine with me. Might be nice to apply v2
just in case that code is ever called by something that is not validating
the address.
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http
I tried this on a 3.17.0-rc7+ kernel, but reported tx-rate stays at 54Mbps
iw dev sta1 set bitrates legacy-5 24
Driver is ath9k, but wpa_supplicant is configured to disable HT.
I'm going to go dig into this, but if someone has any suggestions,
please let me know.
Thanks,
Ben
--
Ben Greear
On 10/01/2014 04:00 PM, Ben Greear wrote:
I tried this on a 3.17.0-rc7+ kernel, but reported tx-rate stays at 54Mbps
iw dev sta1 set bitrates legacy-5 24
Driver is ath9k, but wpa_supplicant is configured to disable HT.
I'm going to go dig into this, but if someone has any suggestions
On 09/30/2014 05:27 AM, Michal Kazior wrote:
On 29 September 2014 18:05, Ben Greear gree...@candelatech.com wrote:
On 09/29/2014 01:24 AM, Kalle Valo wrote:
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
This gives user-space a normal-ish way to detect
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
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 09/29/2014 01:24 AM, Kalle Valo wrote:
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
This gives user-space a normal-ish way to detect that
firmware has failed to start and that a reboot is
probably required.
Signed-off-by: Ben Greear gree...@candelatech.com
As far as I can tell, the .h file is not installed anywhere
in a normal OS.
What is the proper method to get this file sanitized and put
into a more common location?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from
On 09/25/2014 04:59 PM, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
This will let hw-sim create wiphy objects with a specific
name.
This has an added whitespace that should not have been included,
and next patch does not take rtnl before doing the rename
On 09/24/2014 11:23 PM, Michal Kazior wrote:
On 24 September 2014 18:30, Ben Greear gree...@candelatech.com wrote:
On 09/24/2014 08:05 AM, Michal Kazior wrote:
On 24 September 2014 16:35, Ben Greear gree...@candelatech.com wrote:
On 09/24/2014 12:51 AM, Michal Kazior wrote:
On 24 September
(data-pending) = MAX_QUEUE) {
/* Droping until WARN_QUEUE level */
while (skb_queue_len(data-pending) = WARN_QUEUE)
skb_dequeue(data-pending);
}
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http
make any sense at all? Shouldn't we deny it or make it fallback to
the supported tx/rx chainmask values?
It would cause the logic to flip back to the defaults, so seems mildly useful.
I'm not sure
upper layers would ever let it be 1 though.
Thanks,
Ben
Michał
--
Ben Greear gree
stats between the above mutex_unlock() and
following spin_lock_bh().
That makes no difference at all to the user though, and it is one less
set of nested locks to worry about.
I'd prefer to leave it as is.
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http
Michał
--
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
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
On 09/24/2014 08:05 AM, Michal Kazior wrote:
On 24 September 2014 16:35, Ben Greear gree...@candelatech.com wrote:
On 09/24/2014 12:51 AM, Michal Kazior wrote:
On 24 September 2014 02:26, gree...@candelatech.com wrote:
[...]
+static struct ieee80211_sta_vht_cap ath10k_create_vht_cap
On 09/24/2014 12:09 AM, Michal Kazior wrote:
On 23 September 2014 18:48, Ben Greear gree...@candelatech.com wrote:
On 09/23/2014 01:59 AM, Michal Kazior wrote:
On 23 September 2014 01:00, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
[...]
@@ -4086,6 +4086,10
On 09/23/2014 11:50 PM, Michal Kazior wrote:
On 23 September 2014 16:19, Ben Greear gree...@candelatech.com wrote:
On 09/23/2014 02:16 AM, Michal Kazior wrote:
On 19 September 2014 20:28, gree...@candelatech.com wrote:
[...]
+ /* If we are CT firmware, ask it to flush all tids on all
kernel: cfg80211: Setting DFS Master region in
update_regulatory, was: unset, new: FCC lr: 8802208ba280 regdom:
8800c72a6300
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line
On 09/23/2014 05:54 AM, Kalle Valo wrote:
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
This can allow more than 32 stations to be supported
without over-running the bitmap.
Signed-off-by: Ben Greear gree...@candelatech.com
[...]
- ar-monitor_vdev_id
On 09/23/2014 05:59 AM, Kalle Valo wrote:
gree...@candelatech.com writes:
From: Ben Greear gree...@candelatech.com
Support up to 32 stations when using CT firmware.
Signed-off-by: Ben Greear gree...@candelatech.com
[...]
- if (test_bit(ATH10K_FW_FEATURE_WMI_10X, ar-fw_features
On 09/23/2014 01:53 AM, Michal Kazior wrote:
On 22 September 2014 22:54, gree...@candelatech.com wrote:
From: Ben Greear gree...@candelatech.com
It appears it takes more than just setting the
hardware's chainmask to make things work well. Without
this patch, a vdev would only use 1x1 rates
-num_rf_chains = WMI_MAX_SPATIAL_STREAM;
}
+ ar-supp_tx_chainmask = (1 ar-num_rf_chains) - 1;
+ ar-supp_rx_chainmask = (1 ar-num_rf_chains) - 1;
Are there are no chips that support a different number
of tx and rx chains?
Thanks,
Ben
--
Ben Greear gree...@candelatech.com
Candela
On 09/10/2014 08:59 AM, Kalle Valo wrote:
From: Ben Greear gree...@candelatech.com
10.1 firmware does not have an official way to
cause assert on purpose, but it can be done with
carefully crafted WMI command. This is a different
kind of crash from the 'hard' crash, which is
a bad memory
501 - 571 of 571 matches
Mail list logo
