Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@bigfootnetworks.com>
To: linux-wireless@vger.kernel.org
Subject: ar9170 vs otus advice?
Date: Mon, 01 Jun 2009 17:07:00 -0500	[thread overview]
Message-ID: <1243894020.1559.22.camel@bigfoot-m4a75t> (raw)

> > mac80211 drivers:
> > 
> > agnx	-> http://git.sipsolutions.net/agnx.git
> > at76_usb	-> replacement already in kernel.org code at drivers/net/wireless/at76c50x-usb.[ch]
> > otus	-> replacement already in kernel.org code at drivers/net/wireless/ar9170/
> 
> Thanks for the summary.
> 
> Note, whenever a "real" wireless driver goes into the tree that
> obsoletes any of the staging drivers, please let me know and I'll
> instantly remove it.
> 
> Right now the otus code is staying because the ar9170 developers want it
> to.


So, I'm trying to understand the current state of the ar9170 and otus
drivers so that I may know where to direction some effort.  I'd like to
get an WN111v2 running with 11n support, and am willing to start with
either the ar9170 or otus drivers as needed.  But I've not been following
along in too much detail so far.

Advice on where I should start, what's working, what's not working,
what needs help, etc?  And should I start with one of the linville Git
trees?  Or wireless-everything?

Thanks,
jdl



             reply	other threads:[~2009-06-01 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 22:07 Jon Loeliger [this message]
2009-06-03  1:37 ` ar9170 vs otus advice? Christian Lamparter
2009-06-03 15:59   ` Jon Loeliger
2009-06-03 18:32     ` Christian Lamparter
2009-06-03 18:09       ` Jon Loeliger

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=1243894020.1559.22.camel@bigfoot-m4a75t \
    --to=jdl@bigfootnetworks.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox