From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
Kalle Valo <kalle.valo@iki.fi>
Subject: Re: Staging tree status for the .32 kernel merge
Date: Thu, 3 Sep 2009 14:48:43 +0200 [thread overview]
Message-ID: <200909031448.46943.s.L-H@gmx.de> (raw)
In-Reply-To: <1251967786.3336.19.camel@johannes.local>
Hi
On Thursday 03 September 2009, Johannes Berg wrote:
> Hi Greg,
[...]
> > - at76_usb wireless driver. Again, no one working on it, it
> > will be dropped in .33.
>
> There's at76c...something...-usb now, with a situation similar to the
> ar9170/otus one.
[...]
at76c50x-usb, the mac80211 port of at76_usb, has been merged mainline in
2.6.30, it works well on two at76c503a devices for me.
Performance and features are comparable (there were WPA patches[1] around,
CCMP for at76c505 devices only, but due to stability issues with the newer
firmware, they weren't merged in staging or at76c50x-usb); both drivers
sport an identical device coverage. The 802.11b chipsets themselves are
no longer in production, but were rather common (also in handhelds) around
6-9 years ago. In their current state, at76_usb and at76c50x-usb are
restricted to WEP64/ 128 or unencrypted networks and work equally well
(at76c50x-usb without the strange quirks that happen with at76_usb).
AT76C503A specification summary:
http://www.atmel.com/dyn/resources/prod_documents/1949S.PDF
AT76C505 specification summary:
http://www.atmel.com/atmel/acrobat/2364s.pdf
[1] Original WPA patches:
https://lists.berlios.de/pipermail/at76c503a-develop/2008-May/000240.html
Regards
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2009-09-03 12:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 4:14 Staging tree status for the .32 kernel merge Greg KH
2009-09-03 8:49 ` Johannes Berg
2009-09-03 12:48 ` Stefan Lippers-Hollmann [this message]
2009-09-03 17:57 ` Greg KH
2009-09-03 18:35 ` Kalle Valo
2009-09-03 19:01 ` Greg KH
2009-09-03 13:14 ` Bartlomiej Zolnierkiewicz
2009-09-03 16:17 ` Christoph Hellwig
2009-09-03 17:55 ` Greg KH
2009-09-03 18:40 ` Christoph Hellwig
2009-09-03 18:55 ` Greg KH
2009-09-03 19:16 ` Christoph Hellwig
2009-09-05 0:16 ` Marcel Holtmann
2009-09-05 0:29 ` Greg KH
2009-09-03 19:35 ` Luis R. Rodriguez
2009-09-03 19:41 ` Greg KH
2009-09-04 10:20 ` Wolfram Sang
2009-09-04 18:25 ` Belisko Marek
2009-09-05 12:39 ` Willy Tarreau
2009-09-05 14:50 ` Greg KH
2009-09-10 21:57 ` Peter Huewe
2009-09-06 5:28 ` Pavel Machek
2009-09-07 15:55 ` Daniel Walker
2009-09-09 9:57 ` Pavel Machek
2009-09-09 14:19 ` Daniel Walker
2009-09-09 8:01 ` Pavel Machek
2009-09-09 21:47 ` Pavel Machek
2009-09-09 21:53 ` Brian Swetland
2009-09-09 22:25 ` Huntsman, Bryan
2009-09-07 23:12 ` Mauro Carvalho Chehab
2009-09-09 8:10 ` Pavel Machek
2009-09-07 23:21 ` Mauro Carvalho Chehab
2009-09-08 1:14 ` Greg KH
2009-09-12 19:40 ` Frontier USB Drivers (Was: Staging tree status for the .32 kernel merge) Dave Taht
2009-09-14 17:35 ` Greg KH
2009-09-15 9:29 ` Clemens Ladisch
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=200909031448.46943.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-kernel@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