calibrated correctly in currently driver or there
is any other reason? I would like to do more test if it is helpful
for your work.
BR
Yanbo
Test environment:
wireless-testing tree( the 2.6.27-rc1)
The distance between the AP and station is about 1 meter.
Two testing cards's info:
[ 1090.9
I used two AR2413 card worked in mesh mode, and using the newest
wireless-testing tree, by disable the kernel debugging option to
avoid trigger some "Lock" problem will hang up the system, the two
AR2413 can find each other in mesh mode and connect to each other.
then I use iperf to test the perf
When I set two PC with Atheros AR2413 in mesh mode, they can find each
other, then I tried to ping each other, after send 10-12 ping packets,
the PC will hang up, below is the dmesg output, I suspicion this bug
is the same as this one
http://marc.info/?l=linux-wireless&m=121731102709834&w=2, but d
mp" it will trigger a lock
problem(attach is the warning info).
4: In my test after send 7 ping packets, the kernel will crash for
some reason. (After I get a serial console line, will report more
detail of it or send a patch if I can figure them out)
Signed-off-by: Li YanBo <[EMAIL PROTECTED]&
place to set the sc->opmode's
value to IEEE80211_IF_TYPE_MESH_POINT.
2. it also haven't found code to enable/trigger "beacon send" in
MESH_POINT mode.
So I think maybe this patch can make ath5k work in mesh mode if some
mesh point(with b43 or zd1211rw) has b
th5k, or was it found that atheros had
> produces a new generation of chips that required a rewrite?
>
For What Ｉknow Ath9K series chipsets support 11N but ath5k just
support a/b/g. Luis should know exactly about this :) CMIIW
yanbo
___
ath5k-dev
