linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-wireless@vger.kernel.org
Subject: ath5k AP support?
Date: Tue, 16 Jun 2009 23:40:41 +0200	[thread overview]
Message-ID: <4A381159.70301@wpkg.org> (raw)

According to http://linuxwireless.org/en/users/Drivers/ath5k, AP mode is 
"reported to work, we just need some further tests on all cards to be sure".

I just tried it with 2.6.30 kernel with this card:

00:02.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 
Multiprotocol MAC/baseband processor (rev 01)

And it doesn't work:

1245188059.756414: Configuration file: /etc/hostapd/hostapd-wlan0.conf
1245188059.766698: nl80211: Add own interface ifindex 6
1245188059.768470: nl80211: Add own interface ifindex 5
1245188059.770822: nl80211: Failed to set interface 5 to mode 3: -122 
(Operation not supported)
1245188059.772627: nl80211: Failed to set interface wlan1 into AP mode
1245188059.774811: nl80211 driver initialization failed.
1245188059.776564: wlan1: Unable to setup interface.
1245188059.778342: Flushing old station entries
1245188059.780055: Deauthenticate all stations
rmdir[ctrl_interface]: No such file or directory
ELOOP: remaining socket: sock=3 eloop_data=0x47b860 user_data=0x47bda0 
handler=0x43929c


Is there anything more needed for ath5k to work (some external patches, 
git tree etc.)?

I tested it on ASUS WL-500gP (BCM47XX mips platform).

-- 
Tomasz Chmielewski
http://wpkg.org

             reply	other threads:[~2009-06-16 21:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 21:40 Tomasz Chmielewski [this message]
2009-06-16 21:51 ` ath5k AP support? Pavel Roskin
2009-06-16 21:54 ` Bob Copeland
2009-06-18 20:16   ` Tomasz Chmielewski
2009-06-18 20:22     ` Tomasz Chmielewski
2009-07-05 12:02       ` Bob Copeland
2009-07-11 16:20         ` Tomasz Chmielewski

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=4A381159.70301@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).