Hi,
I'd like this to be slightly different:
* Just ensure that the firmware is = 1.3
We'll make sure that the firmware doesn't break in a bad way. The
first set of really bad backwards compatible braking changes will kick
into whatever we eventually call 2.0..
That way we can release 1.4, 1.5,
Thanks Mr. Adrian. I will revert back to you after sometime. But are there any
documents/datasheets explaining on the BTCOEX mode registers, timing diagrams
for 2-wire/3-wire coexistence based on Atheros chipset?
I have already gone through the ath9k website; but does not contain these
details.
There's nothing public, no. Just the source code. :)
adrian
On 5 April 2013 01:00, sandeep suresh sandeep.sur...@yahoo.co.in wrote:
Thanks Mr. Adrian. I will revert back to you after sometime. But are there
any documents/datasheets explaining on the BTCOEX mode registers, timing
diagrams
Thanks Mr.Adrian for the information. I had a look at the source code for
Ath9k. For 2-wire coexistence, other than GPIO configuration (direction, Mux
etc) for WLAN_ACTIVE and BT_ACTIVITY, is there also weight register
configuration for BT and WLAN for 2-wire?
What exactly is the meaning of
On 5 April 2013 02:06, sandeep suresh sandeep.sur...@yahoo.co.in wrote:
Thanks Mr.Adrian for the information. I had a look at the source code for
Ath9k. For 2-wire coexistence, other than GPIO configuration (direction, Mux
etc) for WLAN_ACTIVE and BT_ACTIVITY, is there also weight register
sandeep suresh wrote:
I had a look at the source code for Ath9k. For 2-wire coexistence, other than
GPIO configuration (direction, Mux etc) for WLAN_ACTIVE and BT_ACTIVITY, is
there also weight register configuration for BT and WLAN for 2-wire? What
exactly is the meaning of these weight
Hi,
thanks a lot for your helpful mail. I made several tests and good
progress, thanks to you :)
* Holger Schurig [mailto:holgerschu...@gmail.com] wrote:
Hi, I wouldn't use iwconfig and link quality.
iwconfig is outdated and virtually unmaintained since years.
Ohh, good to know... it is
Hi Adrian,
Just to check firmware is = 1.3 is not enough because e.g. this driver
will try to run 3.0 firmware that is probably not compatible with this
driver that was intended for 1.3 fw.
Suggestion is to check only major version because major version is the one
who determines if driver and
Hello Mr.Sujith,
Thanks for the elaborate answer which helps a lot.
But the question is for 2-wire coexistence, are there any weight register?
Because I did not see the same in ath9k code base neither in btcoex.c, gpio.c
etc. The weight registers are only available for 3-wire. Please let me
...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath9k_htc_fw
--
Best regards,
Eugene
--
Best regards,
Eugene
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130405
On 5 April 2013 07:28, Eugene Krasnikov k.eugen...@gmail.com wrote:
Hi Adrian,
Just to check firmware is = 1.3 is not enough because e.g. this driver will
try to run 3.0 firmware that is probably not compatible with this driver
that was intended for 1.3 fw.
Suggestion is to check only major
On 5 April 2013 08:24, sandeep suresh sandeep.sur...@yahoo.co.in wrote:
Hello Mr.Sujith,
Thanks for the elaborate answer which helps a lot.
But the question is for 2-wire coexistence, are there any weight register?
Because I did not see the same in ath9k code base neither in btcoex.c,
Adrian,
By the way do you know if 1.1 and 1.3 are compatible?
If they not then more tricky logic is required. E.g. starting from 2.0
compare only major version but before 2.0 use old logic to compare if
driver and fw compatible.
2013/4/5 Adrian Chadd adr...@freebsd.org:
On 5 April 2013 07:28,
On 5 April 2013 09:50, Eugene Krasnikov k.eugen...@gmail.com wrote:
Adrian,
By the way do you know if 1.1 and 1.3 are compatible?
If they not then more tricky logic is required. E.g. starting from 2.0
compare only major version but before 2.0 use old logic to compare if
driver and fw
Ok, so what I've discovered:
The weight registers in pre-ar9300 chips are pairs of 2 bit registers
that map to some internal state inside the MAC.
Ie, if state is X, then weight is Y.
The MAC then compares the WLAN and BT weights; if WLAN = BT, WLAN wins.
I'll see if I can polish this up and
Right.
So the weight table for Kite/Kiwi:
wait_beacon | qcu_priority | rx_clear | wlan level
0 | 0 | 0 | wlan_weight[0:1]
0 | 0 | 1 | wlan_weight[3:2]
0 | 1 | 0 | wlan_weight[5:4]
0 | 1 | 1 | wlan_weight[7:6]
1 | 0 | 0 | wlan_weight[9:8]
1 | 0 | 1 | wlan_weight[11:10]
1 | 1 | 0 |
16 matches
Mail list logo
