From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Fully supported chip/card with ath9k in AP mode (PCI and PCIe)
Date: Sat, 06 Nov 2010 13:27:40 +0100 [thread overview]
Message-ID: <4CD549BC.5050307@ionic.de> (raw)
Hello guys,
I'm searching for some by ath9k fully supported chipset/card for use in
AP mode, both for PCI and PCIe.
Currently, I do have two cards with the AR5008 chipset. Formally, it is
supported, but I've tried to get it running for three years without any
success and have lost the interest. As I'd though like to have wifi and
ath9k is a good choice, I'm looking for some replacement.
For those who may be interested: I can set my current cards into AP mode
and launch hostapd just fine. Clients can associate, but mostly are
disassociated within 5 minutes (or less, if "high" traffic occurs.) That
said, at this point, re-association may be possible again, but only for
some seconds. Mostly though, the clients can't even re-associate and I
have to restart the cards and hostapd in order to be able to associate
for another roughly 5 minutes.
I hope that somebody could point me to a better working (or actually,
indeed working) chipset. This said, I'm not overly interested in tables
containing chipsets/cards as the information there may be formally true,
but not so much applicable in real life. (Take my cards for instance,
though formally supported, I've been suffering from the same symptoms
for over three years now, both with in-kernel drivers, compat-wireless,
stable hostapd and hostapd-git.)
I'm looking forward to hear from you. :)
Best regards,
Mihai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6111 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20101106/b28cb330/attachment.bin
reply other threads:[~2010-11-06 12:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CD549BC.5050307@ionic.de \
--to=ionic@ionic.de \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.