r was written for the net80211 stack and is a completely
different beast
from ath9k. Please don't post issues that you find in Fusion in ath9k-devel.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
John,
A bunch of cleanups, removal of duplicate data structures and
unused macros.
Sujith
Sujith Manoharan (6):
ath9k: Cleanup data structures related to HW capabilities
ath9k: Remove redundant data structure ath9k_txq_info
ath9k: Use mac80211's band macros and remove enum hal_freq
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/ath9k.h | 191 +-
drivers/net/wireless/ath9k/beacon.c | 10 +-
drivers/net/wireless/ath9k/core.c | 58 +++---
drivers/net/wireless/ath9k/hw.c
Use ath9k_tx_queue_info which contains the same elements,
and merge get/set functions of tx queue properties.
Also, fix whitespace damage in struct ath_softc.
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/ath9k.h | 27 +
drivers/net/wireless
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/ath9k.h |5 -
drivers/net/wireless/ath9k/hw.c|8
2 files changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/net/wireless/ath9k/ath9k.h
b/drivers/net/wireless/ath9k/a
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/core.h | 275 +---
1 files changed, 130 insertions(+), 145 deletions(-)
diff --git a/drivers/net/wireless/ath9k/core.h
b/drivers/net/wireless/ath9k/core.h
index 903bd46..e
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/ath9k.h |6 --
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/drivers/net/wireless/ath9k/ath9k.h
b/drivers/net/wireless/ath9k/ath9k.h
index 9976406..82e71f9 100644
--- a/drive
Use a single enum for managing modes, store supported modes by
the HW in a bitmask.
Register legacy rates with mac80211 only at init.
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/ath9k.h | 48 +++---
drivers/net/wireless/ath9k/be
> themselves from the TODO list. Otherwise I don't see that community
> participation is easily possible.
Sorry about that, you are right, it is duplicated effort.
I'll update http://wireless.kernel.org/en/users/Drivers/ath9k to indicate
wha
John,
Another round of cleanups.
Sujith
Sujith Manoharan (10):
ath9k: Merge reset functions
ath9k: RX Filter cleanup
ath9k: Use bitfields for buffer type
ath9k: Remove a few unnecessary macros
ath9k: Remove ar5416hal and assign default values directly
ath9k: Unused macros, variables
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/beacon.c |2 +-
drivers/net/wireless/ath9k/core.c | 73 +++
drivers/net/wireless/ath9k/core.h |3 +-
drivers/net/wireless/ath9k/recv.c |2 +-
drivers/net/wi
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/core.c | 53 -
drivers/net/wireless/ath9k/core.h |5 ++-
drivers/net/wireless/ath9k/main.c | 19 +++--
drivers/net/wireless/ath9k/recv.c | 11 +--
4
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/core.h | 70
drivers/net/wireless/ath9k/xmit.c | 92 +
2 files changed, 83 insertions(+), 79 deletions(-)
diff --git a/drivers/net/wi
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/core.h | 15 +++
drivers/net/wireless/ath9k/xmit.c |2 +-
2 files changed, 4 insertions(+), 13 deletions(-)
diff --git a/drivers/net/wireless/ath9k/core.h
b/drivers/net/wireless/ath9k/
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/hw.c | 28 +++-
1 files changed, 3 insertions(+), 25 deletions(-)
diff --git a/drivers/net/wireless/ath9k/hw.c b/drivers/net/wireless/ath9k/hw.c
index bde162f..b294485 100644
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/ath9k.h | 18 +++---
drivers/net/wireless/ath9k/hw.h| 116 ---
2 files changed, 50 insertions(+), 84 deletions(-)
diff --git a/drivers/net/wireless/ath9k/ath9k.h
b/d
ah_opmode and sc_opmode are redundant.
This patch removes sc_opmode.
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/ath9k.h |2 +-
drivers/net/wireless/ath9k/beacon.c | 18 +-
drivers/net/wireless/ath9k/core.c
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/beacon.c |4 +-
drivers/net/wireless/ath9k/core.c | 45 ++-
drivers/net/wireless/ath9k/core.h | 24 ++
drivers/net/wireless/ath9k/main.c
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/core.c | 20 +---
drivers/net/wireless/ath9k/core.h |1 -
drivers/net/wireless/ath9k/rc.c |4 ++--
drivers/net/wireless/ath9k/xmit.c |2 +-
4 files changed, 12 insertions(
Add sc_rxflush and sc_noreset as bitfields to sc_flags.
Remove a few variables and function prototypes that are unused.
Signed-off-by: Sujith Manoharan <[EMAIL PROTECTED]>
---
drivers/net/wireless/ath9k/beacon.c |8 ++--
drivers/net/wireless/ath9k/core.c | 10 --
drivers/net/wi
> Do you have any suggestions how we can help to make the development
> > process shorter?
>
> Try ad-hoc with Jouni's beaconing (AP) patches posted.
Apparently, ad-hoc is broken.
Tomas sent an e-mail to linux-wireless mentioning this.
Check http://marc.info/?l=linux-wireless&
nux-wireless&m=121845260100807&w=2
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
development, please use the
wireless-testing
tree instead.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
posted earlier [1].
Please verify if the issue is still seen with that patch.
[1]: http://marc.info/?l=linux-wireless&m=122309915413328&w=2
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
2.6.26-ARCH.
> Any help will be Welcome.
>
Did you compile wireless-testing ?
How are you trying to connect to the AP, using wpa_supplicant ?
If so, can you post the config ?
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https
; The task is to make hostapd-0.6.4 work.
>
You need this patch to make AP mode work:
http://johannes.sipsolutions.net/patches/kernel/all/LATEST/004-allow-ap-vlan-modes.patch
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
a
use to connect ?
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
driver, and other surrounding wireless
> networks...
>
> Is anybody here who has also experienced this with rc2? (git version
> from the last week supported station mode at least)
You might want to check if you are using the proper regulatory domain.
Check http://wir
iver
is under heavy development.
> 2. Is this driver has been shipped with some linux distributions?
Yep, any distribution that carries kernel 2.6.27 or above will carry ath9k.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://l
send out a patch that fixes this.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
transmitted properly on
> the first try, will the node buffer these frames and wait till it can
> send the complete block up, or does it just forward up what it gets
> after the block-ack is sent each time?
>
ieee80211_sta_manage_reorder_buf() in net/mac80211/rx.c contains
the answers you
above will be greatly appreciated.
>
Nope, no documentation. :)
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
0.pid'
> Trying to connect to '/var/run/wpa_supplicant/wlan0.pid'
> Failed to open control connection to wpa_supplicant.
> PING failed - trying to reconnect
Can you show your wpa_supplicant config ?
Sujith
--
http://sujith-m.blogspot.com
___
1
> ssid="dlink"
> key_mgmt=WPA-PSK
> psk="secret"
> }
>
Does running wpa_supplicant manually connect to the network ?
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Tamas Selmeci wrote:
> 1) may I expect a working AP mode at the current state of ath9k? (I
> rememben formerly a few people reported that it works);
AP mode is under development, and getting it to work right now is not
possible.
Sujith
___
ath9k
tx_start().
And the queue is sent through txctl.txq, you don't have to calculate the queue
number again.
So, just stopping the queue and moving the buffer back to the free list would
be enough.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
from txctl, so that code can be removed.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
e with AP 00:11:95:9e:df:f6
> wlan0: authentication with AP 00:11:95:9e:df:f6 timed out
A number of updates have gone into the wireless-testing tree.
You can use that tree or compat-wireless to get the latest driver
and check if the problem persists.
Sujith
__
; or reasonable in other platform?
That address is used only in AP boards, it shouldn't matter for
a STA driver.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
next moment computer
> fully hangs.
> well, i have dmesg on screen in hanged state, fair enough, take my
> phone, and well, there are the photos of dmesg... Hope they can be usefull.
>
This should be fixed in the commit 6cc47a6f886f72d9d54a52a
happy to do) but is there a
> quicker/better way?
compat-wireless would be easier.
See: http://wireless.kernel.org/en/users/Download
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
the way..
>
> My accesspoint (D-Link DIR-855) is set to 802.11n network only, with wpa2
> and aes only, to get some more speed.
wireless-testing has a number of driver updates, please use that to check
if it improves the speed.
Alternatively, you can use compat-wireless:
http://wir
ut ?
(With the usual association, pinging etc ..)
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
#x27;
>
> Eirik
>
Sorry, this needs to be in your .config -
CONFIG_ATH9K_DEBUG=y
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
logs.
But rsync would show the actual throughput for transfers.
Can you check what this command shows ?
rsync -ahP /mnt/samba/othermachine/69MB-testfile .
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
inks to other common wifi setup gotchas would be nice.
>
2.6.26 is too old. 2.6.27.9 will have the ath9k driver, but plenty of updates
have gone into the
wireless-testing tree.
You can either use that tree, or use compat-wireless.
See: http://wireless.kernel.org/en/users/Download
Sujith
__
ATH9K_MODE_11NA_HT40PLUS];
> + else
> + sc->cur_rate_table =
> sc->hw_rate_table[ATH9K_MODE_11A];
> + break;
> + default:
> + break;
> + }
> }
We don't have separate rate tables for ht20, ht40+, ht40-.
Setting
EE80211_BAND_5GHZ &&
> + conf_is_ht20(conf))
> + return true;
> break;
> }
Why are the IS_CHAN_B() checks removed ?
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
solidate on the rate tables?
We have only 2 HT rate tables, ar5416_11na_ratetable and ar5416_11ng_ratetable.
The different HT modes point to the same tables, in ath_rate_attach().
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://
Luis R. Rodriguez wrote:
> Because 1) it will currently never happen 2) we need a better check for is
> CCK in mac80211, not
> an internal check.
>
Agreed, an internal check is hacky.
But hopefully, we'll remember this when adding 11B su
propriate ifdefs), instead
of pci.c and ahb.c ?
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Apart from this, if we will put the PCI and AHB stuff into one file,
> we could put it into main.c simply.
Your choice really, it doesn't matter much anyway. :)
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
__func__, off);
> + return false;
> + }
> +
> + *data = pdata->eeprom_data[off];
> + return true;
> +}
> +
Shouldn't pdev->dev.platform_data be initalized somewhere ?
Sujith
___
ath9k-
Gabor Juhos wrote:
> Convert to use bus-agnostic DMA routines to make it usable on AHB bus as well.
>
This pretty much makes the previous patch redundant.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/m
Gabor Juhos wrote:
> Sujith rta:
> > Gabor Juhos wrote:
> >> +static bool ath_ahb_eeprom_read(struct ath_hal *ah, u32 off, u16 *data)
> >> +{
> >> +struct ath_softc *sc = ah->ah_sc;
> >> +struct platform_device *pdev = to_platform_devic
Gabor Juhos wrote:
> Sujith rta:
> > Gabor Juhos wrote:
> >> Convert to use bus-agnostic DMA routines to make it usable on AHB bus as
> >> well.
> >>
> >
> > This pretty much makes the previous patch redundant.
>
> Yes. Although i can me
the numerous
fixes
that have gone into ath9k. Any kernel later than 2.6.27 would be a better
choice.
In that case you can use compat-wireless-2.6 to pull in the latest code.
See: http://wireless.kernel.org/en/users/Download
Sujith
--
http://sujith-m.blogspot.com
__
rnel/wireless-tools package to allow
> connections at a higher rate?
Please load ath9k with debugging enabled, as 'modprobe ath9k debug=0x2000'
and post the output here.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ated, and the led on the lapton is off.
> Any help?
What is the version of the kernel you are running ?
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
bug=0x2000' ?
Note: CONFIG_ATH9K_DEBUG=y has to be present in your .config
Also, this option is present in newer kernels, so 2.6.29-rc2 should do fine.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@li
sri ram wrote:
> Sorry I hadn't compiled debug mode support. After compiling the
> output looks as follows.
Please post the complete log (after association etc ..).
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
assuming this is a message that you have added ?
Anyway, I don't see any problem, but iwconfig doesn't report HT rates.
You can run iperf and see how the throughput is.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
ate that the TX descriptors are not being setup properly.
HTH.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Ciccio wrote:
> 2009/1/18 Sujith :
> > Ciccio wrote:
> >> The default opensuse 11.1 kernel, which is 2.6.27.7, but I also tried
> >> other kernels without success, including the latest 2.6.29-rc2
> >> compiled from source. All kernels are for x86_64 arch.
>
I am not sure if that is 0x201 or 0x208 or
> something else.. its not easy to determine from that picture. Anyway
> -- you want the line on the EIP.
>
Along with what Luis has described above, please load ath9k as
'modprobe ath9k deb
tp://wireless.kernel.org/en/users/Download
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Chris Kennedy wrote:
> I have gotten this twice now since the Jan 16th version of wireless-
> testing with my DWA-552 card (last update for ath9k listed)...
>
> commit 403c131be279d5390e8276e73500081d2595c8bf
> Author: Sujith
> Date: Fri Jan 16 21:38:56 2009 +0530
>
> I will recompile with the debugging and see when it happens again.
> It has
> happened twice now, seems like after I change the ht_capab settings in
> hostapd.conf (had added DSS_CCK-40 toit when this happened).
Oh, you are running in AP mode then.
Ok,
e has PCI/PCIe driver supporting any 802.11n chips for 2.6.21?
You can try compat-wireless-old. IIRC, it does support 2.6.21, but you would
not get the latest code present in wireless-testing.
See: http://wireless.kernel.org/en/users/Download
Sujith
--
http://
report the right MCS index through iw
> though. It seems this is due to the way our RC works... anyway this
> could use some love too. Sujith may be working on this, not sure,
> sujith?
>
> In the end it would be nice to see minstrel be used anyway so a good
> milestone is to allow
pastebin.com/d5334f384
The post at pastebin has expired...
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
get the latest code.
See: http://wireless.kernel.org/en/users/Download
Enable CONFIG_ATH9K_DEBUG=y in config.mk, load ath9k with the module parameter
debug=0x2000, and then reproduce the issue and post the log here please. Thanks.
Sujith
--
http://sujith-m.blogspot.com
__
and the channel is noisy. However, I never saw any
> rates > 54 Mbps. Are the 11n rates available in ad-hoc mode? Thx a lot.
Nope, 11n hasn't been implemented for Ad-Hoc.
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9
t in the driver
and see how it goes. (NL80211_IFTYPE_WDS in ath_attach() ).
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
nitialized to "1"?
You don't have to, 1x1 chainmask configuration will automatically be chosen
for legacy mode.
See ath_update_chainmask() in main.c
Sujith
--
http://sujith-m.blogspot.com
___
ath9k-devel mailing list
ath9k-devel@lists.ath
inmask/sc->sc_rx_chainmask be
> initialized to "1"?
The chainmasks would automatically be 1x1 in legacy mode, see
ath9k_config()@main.c
and ath_update_chainmask().
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
k with AR9260?
I haven't tried ath9k with any mini-PCI card so far, will dig around to see
if I can find one.
> 2) Where I can get documentation for AR5*** and AR9*** chipsets? Does
> it released for public access?
The code is the documentation. :)
Sujith
--
http://sujith-m.blogspot
lly developing... =)
>
AR9160 is supported by ath9k, so no worries here.
> How to enable additional debug info? Can I use KDBG + /dev/ttyS0 to
> search for the problem? :)
Search for serial console / netconsole debugging guides on the net.
> Please, give me a link to git tutorial
you
> could try using one of the non-DFS channels. Check 'iw list' for that.
>
> ath9k STA should work with DFS but I didn't work on that myself so
> will leave someone else to comment on that.
Yep, STA mode should work fine, since 802.11h CSA support was added to
ma
Steve Brown wrote:
> For me, the ASSERT at rc.c:745 goes off.
>
> I instrumented it. The results are attached.
Thanks for the trace. We'll work on this.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath
commitdiff;h=0cee9809976b35d7bd9eeb6bb7f32b8ac3fcd86d
>
> On kernel 2.6.28.6 with compat-wireless 2009-02-19. All who have put
> the AR9102 in client-mode seem to watch it quickly degrade to 0 or
> 1Mbps rate... which I do not see on a laptop with AR5418 MiniPCI card
> using same compat-wireless.
>
> Sujith
AP advertises 20/40, but sets the operating channel to 20
Mhz,
but ath9k chooses the wrong rate table since it doesn't honor the AP's current
channel width.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Steve Brown wrote:
> > This is the bug, the AP advertises 20/40, but sets the operating channel to
> > 20 Mhz,
> > but ath9k chooses the wrong rate table since it doesn't honor the AP's
> > current channel width.
> >
Can you try this patch ? This will apply on top of today's wireless-testing.
Th
MCS set: ff ff 00 00 00 00 00 00 00 00 00 00 01 00 00 00
>
Ah, are you using ath9k as the AP ?
Can you paste the hostapd log ? (hostapd -dd)
>From your other mail, the chosen rate table is completely wrong,
am not sure if this is related to AP mode in ath9k.
Sujith
Gabor Juhos wrote:
> 1. In some cases the ethernet interface goes down for a short time
> after'ifconfig wlan0 up'.
> 2. Sometimes the device simply reboots itself after 'ifconfig wlan0 up'.
>
> After I have added some printk statements into the code, I noticed that the
> ar5416 and ar9100 devices
Sujith Manoharan wrote:
> I'll check the initval arrays and update.
>
Does this patch help ? I haven't tested on 9100, but 5416 works fine.
diff --git a/drivers/net/wireless/ath9k/hw.c b/drivers/net/wireless/ath9k/hw.c
index eb750a5..d7b3c44 100644
--- a/drivers/net/wireless/
opy of the latest initvals. :-)
Figured this would also make it easier to roll out future updates.
> > +#define AR_SREV_VERSION_9100 0x014
>
> 0x14?
Yep, this can be fixed.
Sujith
___
ath9k-devel mailing list
ath9
be useful. The
> _V20_OR_LATER
> and the _V22_OR_LATER macro I proposed above will cover the 9100 and 9160
> chips.
>
I meant the AR_SREV_5416_V20_OR_LATER and AR_SREV_5416_V22_OR_LATER macros.
Yes, the naming implies that they are meant for AR5416 chipsets only, but they
R_SREV_VERSION_9100 0x014
> >> 0x14?
> >
> > Yep, this can be fixed.
>
> I have to send a new patch, or you will take care of it?
Feel free to send a patch fixing this, and the macro cleanup.
I'll just update the initvals, fix the check for AR9100 in HW
#define AR_SREV_5416_V22_OR_LATER(_ah) \
> (((AR_SREV_5416(_ah)) && \
>((_ah)->hw_version.macRev >= AR_SREV_REVISION_5416_22)) || \
>((_ah)->hw_version.macVersion >= AR_SREV_VERSION_9100))
Agreed, this is cleaner.
Sujith
___
his, and the macro cleanup.
> > I'll just update the initvals, fix the check for AR9100 in HW attach
>
> Well, the _AR9100_OR_LATER would be the right one, simply the macro itself is
> wrong. According to Luis' request, I would send a new patchset, then we can
> discuss
* support 802.11n and I need to do a project with drivers that
> support AMSDU and AMPDU packet aggregation. AFAK, ath9k (in the
> wireless-testing
> tree) supports this AMSDU and AMPDU packet aggregation. Is it true?
ath9k supports only AMPDU
wn would cause a NULL
pointer dereference. Will send out a patch fixing this.
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Gabor Juhos wrote:
> According to Luis request, here is the new patch-set with detailed
> explanations.
Series looks good, but it doesn't apply on current wireless-testing.
A rebase is needed ?
Sujith
___
ath9k-devel mailing list
Gabor Juhos wrote:
> According to Luis request, here is the new patch-set with detailed
> explanations.
>
> Changes since v1:
> * rebased against master-2009-03-04 of wireless-testing
>
Tested on AR5416, works fine.
Sujith
___
a
->flags |= IEEE80211_TX_RC_MCS;
> + if (is_probe)
> + rate->flags |= IEEE80211_TX_CTL_RATE_CTRL_PROBE;
> }
>
IEEE80211_TX_CTL_RATE_CTRL_PROBE is to be used with fl...@ieee80211_tx_info
and is not a per-rate flag.
Sujith
___
:883:6: warning: symbol 'ar9285_clc'
> was not declared. Should it be static?
Commit 93f726a90d1446c9e5a40fe8f88086542b273e7c in net-next-2.6 fixes a couple
of warnings (in eeprom.c).
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
http://wireless.kernel.org/en/users/Download
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
side
Also, can you paste your hostapd.conf and wpa_supplicant's configuration file
here ?
Sujith
___
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Vladimir Senkov wrote:
> On Mon, Mar 16, 2009 at 2:03 AM, Sujith wrote:
> > handle_assoc STA 00:23:4d:b7:98:e8 - no HT, num of non-HT stations 1
> > hostapd_ht_operation_update current operation mode=0x0
> > hostapd_ht_operation_update new operation mode=0x13 changes=2
>
1 - 100 of 876 matches
Mail list logo
