All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Plzik <milan.plzik@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: AP mode support requirements for iwlagn driver
Date: Mon, 09 Feb 2009 23:15:11 +0100	[thread overview]
Message-ID: <1234217712.6695.51.camel@localhost> (raw)
In-Reply-To: <1233953240.4175.29.camel@johannes.local>

V Piatok, 6. febru=C3=A1r 2009 o 21:47 +0100, Johannes Berg nap=C3=ADsa=
l(a):
> On Fri, 2009-02-06 at 16:16 +0100, Milan Plzik wrote:
> > Hello,
> >=20
> >   what are the exact requirements for AP mode support in iwlagn dri=
ver?
> > Is there any change neccessary in card's firmware, or the only miss=
ing
> > code is in mac80211/iwlagn itself? Also, there was sort-of support =
for
> > AP, but it was disabled in later versions -- what were the exact
> > problems with this implementation?
>=20
> One major issue was getting multicast frames out at the right time, b=
ut
> also look at
> http://wireless.kernel.org/en/developers/Documentation/mac80211/API

  Ok, so from what I understand to get AP mode fully working, firmware
has to adjust TSF -- this seems to be what TX_CMD_FLG_TSF_MSK does;
everything other should be manageable by software.=20

  Btw, the URL unfortunately doesn't mention anything about multicast
frames;  if there something describing this more in detail?

>=20
> johannes

	Milan

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-02-10 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 15:16 AP mode support requirements for iwlagn driver Milan Plzik
2009-02-06 20:47 ` Johannes Berg
2009-02-09 22:15   ` Milan Plzik [this message]
2009-02-10 15:40     ` Johannes Berg

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=1234217712.6695.51.camel@localhost \
    --to=milan.plzik@gmail.com \
    --cc=johannes@sipsolutions.net \
    --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 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.