From: Christian Lamparter <chunkeey@web.de>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
Greg KH <greg@kroah.com>,
otus-devel@lists.madwifi-project.org
Subject: [RFC][RFT][PATCH 0/5 v5] ar9170: ar9170 driver (aka mac80211's otus)
Date: Fri, 20 Mar 2009 20:36:08 +0100 [thread overview]
Message-ID: <200903202036.09255.chunkeey@web.de> (raw)
In-Reply-To: <200903170408.12626.chunkeey@web.de>
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.)
Changes:
- enabled HW crypto acceleration (on by default)
- report noise and signal levels in dBm
- sniffer/promiscouous mode now works in BSS
- LED code rework
- fixed last remaining checkpatch.pl ERRORs
Features:
- managed and (full) monitor mode
(other modes may work too... but were not tested)
- QoS
- tx status => automatic rate control
- offload for ccmp, tkip & wep
- programmable LEDs
Note: The whole patch series can be found in the linux-wireless archive.
e.g: http://marc.info/?l=linux-wireless&r=1&b=200903&w=2
Regards,
Chr
---
John what's your verdict? would you accept the driver in its current state?
next prev parent reply other threads:[~2009-03-20 19:36 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 ` Christian Lamparter [this message]
2009-03-20 20:07 ` [RFC][RFT][PATCH 0/5 v5] ar9170: ar9170 driver (aka mac80211's otus) 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
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=200903202036.09255.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).