From: Jiri Slaby <jirislaby@gmail.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Gregory Nietsky <gregory@dnstelecom.co.za>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, ath5k-devel@venema.h4ckr.net,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [PATCH 1/1] Ath5k: add AP mode
Date: Wed, 22 Oct 2008 16:19:34 +0200 [thread overview]
Message-ID: <48FF3676.1060909@gmail.com> (raw)
In-Reply-To: <40f31dec0810211108l6700d806o4804b43d9fe47bf7@mail.gmail.com>
On 10/21/2008 08:08 PM, Nick Kossifidis wrote:
> 2008/10/12 Jiri Slaby <jirislaby@gmail.com>:
>> Add support for AP mode. This involves:
>> - enablement in ath5k_beacon_config -- initialize beacon timer
>> - add AP to the supported modes in ath5k_add_interface
>> - handle beacon change even for AP in ath5k_config_interface
>> - remove useless test for IBSS in ath5k_beacon_update
>>
>> Note that it doesn't enable the AP mode for the driver. It must
>> be enabled by NL80211_IFTYPE_AP bit added to interface_modes.
[...]
> a) It won't work without the following as Gregory pointed out
This was intentional, see the changelog.
> b) For some reason it only works with 5212/5213 cards, i tested it on
> a 5413 and an 2425 and it didn't work (hostapd seems to hang).
I've ordered 5413 ;), will come with updates.
Thanks for testing, Nick.
next prev parent reply other threads:[~2008-10-22 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 20:54 [PATCH 1/1] Ath5k: add AP mode Jiri Slaby
2008-10-21 18:08 ` Nick Kossifidis
2008-10-22 14:19 ` Jiri Slaby [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-27 12:48 Jiri Slaby
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=48FF3676.1060909@gmail.com \
--to=jirislaby@gmail.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=gregory@dnstelecom.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
/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).