From: Christian Lamparter <chunkeey@web.de>
To: Greg KH <greg@kroah.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
otus-devel@lists.madwifi-project.org
Subject: Re: [RFC][RFT][PATCH 0/5 v5] ar9170: ar9170 driver (aka mac80211's otus)
Date: Fri, 20 Mar 2009 23:12:57 +0100 [thread overview]
Message-ID: <200903202312.57737.chunkeey@web.de> (raw)
In-Reply-To: <20090320212515.GA12078@kroah.com>
On Friday 20 March 2009 22:25:15 Greg KH wrote:
> On Fri, Mar 20, 2009 at 10:14:51PM +0100, Christian Lamparter wrote:
> > On Friday 20 March 2009 21:13:26 Greg KH wrote:
> > > On Fri, Mar 20, 2009 at 08:36:08PM +0100, Christian Lamparter wrote:
> > > > Based on the number of mails I got, this driver should be ready for inclusion.
> > > > So, this is probably the last RFC and the official patches will follow on
> > > > sunday (only if no one finds a bug that needs to be fixed ASAP.)
> > >
> > > Wonderful!
> > :-)
> >
> > > When the driver goes into the "real" portion of drivers/net please let
> > > me know and I'll drop the otus driver from the drivers/staging/
> > > location.
> > Well, I doubt that we can replace Otus, ever...
>
> Why, what is lacking in the version you have that is in the otus driver?
>
Well, a few features that the vendors uses to encourage potential buyers:
- HT ( 802.11n - aka 300mbps )
- ANI (ambient noise immunity - so it works in noisy environments),
- TPC/DFS (802.11h - crucial if you want to "blast" the 5GHz band
in most countries)
- AP/AD-Hoc
comes to my mind. That said I didn't really look into otus to see which
of these feature actually works as advertised
Nevertheless ar9170 should fit the bill for users with 802.11b/g
accesspoint just fine.
and of course one could always argue that 802.11n is !still! a draft,
5GHz is not very widespread yet, and ANI only helps on very weak links...
However, I suggest that we wait and see what's the situation when
the first ar9170 bits are about to enter vanilla... deal?
Regards,
Chr
next prev parent reply other threads:[~2009-03-20 22:13 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 [this message]
2009-03-20 22:41 ` Greg KH
2009-03-20 22:49 ` Alina Friedrichsen
2009-03-21 0:59 ` Christian Lamparter
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=200903202312.57737.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 \
/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).