From: Christian Lamparter <chunkeey@web.de>
To: "Alina Friedrichsen" <x-alina@gmx.net>
Cc: greg@kroah.com, otus-devel@lists.madwifi-project.org,
linville@tuxdriver.com, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org
Subject: Re: [RFC][RFT][PATCH 0/5 v5] ar9170: ar9170 driver (aka mac80211's otus)
Date: Sat, 21 Mar 2009 01:59:44 +0100 [thread overview]
Message-ID: <200903210159.44733.chunkeey@web.de> (raw)
In-Reply-To: <20090320224920.261010@gmx.net>
On Friday 20 March 2009 23:49:20 Alina Friedrichsen wrote:
> > Well, a few features that the vendors uses to encourage potential buyers:
> > - HT ( 802.11n - aka 300mbps )
>
> Hopefully someone can implement it.
Well, first the rate control algorithm needs to support it ;-).
so there's plenty of time to theorize what to do.
> > - AP/AD-Hoc
>
> Ad-Hoc mode with fixed BSSIDs works absolutely fine with this driver. I only didn't find a way to reset the TSF, so that IBSS merges works standard compliant.
>
> In the praxis all mesh networks uses fixed BSSIDs.
Thanks for confirming!
Regards,
Chr
next prev parent reply other threads:[~2009-03-21 0:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 3:08 [RFC][RFT][PATCH 0/5] ar9170: ar9170 driver Christian Lamparter
2009-03-20 19:36 ` [RFC][RFT][PATCH 0/5 v5] ar9170: ar9170 driver (aka mac80211's otus) Christian Lamparter
2009-03-20 20:07 ` Alina Friedrichsen
2009-03-20 20:59 ` Christian Lamparter
2009-03-20 23:04 ` Alina Friedrichsen
2009-03-21 14:59 ` Alina Friedrichsen
2009-03-21 15:09 ` Johannes Berg
2009-03-21 15:22 ` Alina Friedrichsen
2009-03-20 20:13 ` Greg KH
2009-03-20 21:14 ` Christian Lamparter
2009-03-20 21:25 ` Greg KH
2009-03-20 22:12 ` Christian Lamparter
2009-03-20 22:41 ` Greg KH
2009-03-20 22:49 ` Alina Friedrichsen
2009-03-21 0:59 ` Christian Lamparter [this message]
2009-03-21 19:12 ` Alina Friedrichsen
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=200903210159.44733.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=otus-devel@lists.madwifi-project.org \
--cc=x-alina@gmx.net \
/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.