From: "John W. Linville" <linville@tuxdriver.com>
To: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
Cc: Johannes Berg
<public-johannes-cdvu00un1VgdHxzADdlk8Q@hugh.gmane.org>,
"otus-devel-qhrM8SXbD5K0lq1k9DReS6gKWPgB4RSr2LY78lusg7I@public.gmane.org"
<public-otus-devel-qhrM8SXbD5K0lq1k9DReS6gKWPgB4RSr2LY78lusg7I@hugh.gmane.org>,
linux-wireless
<public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org>,
Greg KH <greg@kroah.com>
Subject: Re: [FYI] ar9170 driver
Date: Fri, 14 Nov 2008 08:26:46 -0500 [thread overview]
Message-ID: <20081114132645.GA3443@tuxdriver.com> (raw)
In-Reply-To: <491D380D.7050707@teltonika.lt>
On Fri, Nov 14, 2008 at 10:34:21AM +0200, Paulius Zaleckas wrote:
>
>
> Johannes Berg wrote:
> > This patch adds the ar9170 driver for Atheros 802.11n
> > USB hardware ("otus").
> >
> > NOTES/TODO
> > * locks up RX part of the device after a while and the device
> > starts messing with the USB bus
> > (message will be "complete rx %p (0b, -75)")
> > * need to implement RF, TX power calibration based on EEPROM
> > values (maybe causing the RX hangs? doubt it)
> > * already needs some code cleanups
> > * use rate hw_value instead of huge switch statement
> > * implement configure_filter
> > * implement bss_config call
> > * implement beaconing
> > * implement hardware crypto
> > * implement AP mode
> > * implement mesh mode
>
> If this driver is not going in through wireless or any other tree, because it
> still needs some work, maybe it is worth to get it to staging tree maintained
> by Greg?
I really don't think that is necessary. I don't forsee any problem w/
Johannes getting his driver merged.
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
prev parent reply other threads:[~2008-11-14 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 23:03 [FYI] ar9170 driver Johannes Berg
2008-11-12 23:16 ` Johannes Berg
2008-11-13 0:45 ` Johannes Berg
2008-11-13 1:42 ` Johannes Berg
2008-11-13 2:24 ` [otus-devel] " Luis R. Rodriguez
2008-11-13 2:25 ` Luis R. Rodriguez
2008-11-13 2:25 ` Johannes Berg
2008-11-13 19:11 ` Johannes Berg
2008-11-13 19:57 ` Johannes Berg
2008-11-13 20:08 ` Johannes Berg
2008-11-13 23:53 ` Johannes Berg
2008-11-14 8:34 ` Paulius Zaleckas
2008-11-14 10:53 ` Johannes Berg
2008-11-14 17:30 ` Greg KH
2008-11-14 13:26 ` John W. Linville [this message]
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=20081114132645.GA3443@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=greg@kroah.com \
--cc=paulius.zaleckas@teltonika.lt \
--cc=public-johannes-cdvu00un1VgdHxzADdlk8Q@hugh.gmane.org \
--cc=public-linux-wireless-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
--cc=public-otus-devel-qhrM8SXbD5K0lq1k9DReS6gKWPgB4RSr2LY78lusg7I@hugh.gmane.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).