Stephen Gutknecht (hilltx) wrote:
The ping time climbing seems fixed. Thank you. I assume it was this
change related to the RTC clock of AR9100. Reference change:
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=commitdiff;h=0cee9809976b35d7bd9eeb6bb7f32b8ac3fcd86d
On Mon, Feb 23, 2009 at 7:40 AM, Sujith m.suj...@gmail.com wrote:
Stephen Gutknecht (hilltx) wrote:
The ping time climbing seems fixed. Thank you. I assume it was this
change related to the RTC clock of AR9100. Reference change:
Can someone please try client (station) mode on an AHB bus AP81
router? The slower MIPS CPU or even how we initialize the
ar9102/ar9103 chips could be factors.
if you are a serious ath9k developer (the ones with the Linux Kernel
skills) and need a router, please contact me I will personally
The post at pastebin has expired...
Sujith
Yha, sorry about that; Ok, I'm going to start this over and focus on
the retrain and rate issues. Both routers are running the same
chipset with an ar9102, the AP using proprietary madwifi and the
client running ath9k.
Router / AP: D-Link DIR-615
Stephen Gutknecht (hilltx) wrote:
Using the latest OpenWRT trunk with kernel 2.6.28.2 and
compat-wireless ath9k 2009-02-02. This is a real time session log,
from cold boot of the hardware with wireless off, then starting a ping
and enabling the driver. see here: http://pastebin.com/d5334f384
Howdy.
This is talking to a WDNR3300 second interface, which is a G only
broadcom chip, using wpa2 encryption. I have seem similar problems
with an Atheros AP too... but wanted to document the AP in question.
I do not believe the encryption is a factor, I've seen similar
problems with no
