linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: What is needed to inplement a AP support in a driver?
Date: Tue, 07 Apr 2009 08:13:47 +0300	[thread overview]
Message-ID: <87k55xhwqc.fsf@litku.valot.fi> (raw)
In-Reply-To: <1239062777.4705.30.camel@maxim-laptop> (Maxim Levitsky's message of "Tue\, 07 Apr 2009 03\:06\:17 +0300")

Maxim Levitsky <maximlevitsky@gmail.com> writes:

> I recently found that now ath5k supports AP mode.
> I also found that most of the work is now done in userspace.
>
> Since many drivers including my IWL3945 support sending beacons for IBSS
> (strictly speaking userspace can send them too, but this is  sub
> optimal), what else driver must support for AP?
>
> Sending to several stations ? (IBSS already has this), have several
> virtual devices (this is optional feature), what else?

At least sending multicast/broadcast frames immediately after DTIM
beacons. This is needed for clients in power save mode.

> Why iwl3945 still doesn't support AP mode?

No idea. I recall Intel talking about having patches to support AP mode
for iwl3945, but quick googling didn't reveal anything. All I found was
this from Tomas:

"We've enabled only iwl4965, not so ever effort was done for iwl3945

[...]

In general there should not problem to extend AP mode also for 3945 on
PC platform"

http://osdir.com/ml/linux.drivers.ipw3945.devel/2007-11/msg00184.html

It would be really nice to get AP mode support for iwl3945.
Unfortunately I don't have any spare time to work on that, but if you
are planning to work on it I (and others) can give you email support via
this mailing list.

-- 
Kalle Valo

  reply	other threads:[~2009-04-07  5:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  0:06 What is needed to inplement a AP support in a driver? Maxim Levitsky
2009-04-07  5:13 ` Kalle Valo [this message]
2009-04-07  8:16 ` Johannes Berg
2009-04-07  9:25 ` Rami Rosen
2009-04-07 13:11   ` Maxim Levitsky
2009-04-09 12:08     ` Maxim Levitsky

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=87k55xhwqc.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maximlevitsky@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).