From: Johannes Berg <johannes@sipsolutions.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: Staging tree status for the .32 kernel merge
Date: Thu, 03 Sep 2009 10:49:46 +0200 [thread overview]
Message-ID: <1251967786.3336.19.camel@johannes.local> (raw)
In-Reply-To: <20090903041429.GA29875@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
Hi Greg,
> - rt* wireless drivers. Bart has done amazing work merging all
> of these together into something much better than they
> originally were. And even better, they still work! Great
> job Bart!
Work on the rt2x00 project has also progressed to a point where the
drivers are getting much closer to being useful, so eventually all this
work will have been in vain.
> - vt66* wireless drivers. These VIA drivers are being actively
> worked on to get into a much better shape. Nice job.
And do they come with their own wireless stack too?
> - otus. This is sitting here until a "real" wireless driver
> will be merged through the wireless tree. Hopefully that
> happens soon.
ar9170 has been in for a while now, it's just not quite at feature
parity yet -- however that also means otus will get no work whatsoever
from any of the wireless folks. Draw your own conclusions. Personally, I
would drop it and let the users figure out whether they can live with
ar9170 or need to support work on it.
> - agnx wireless driver. No one seems to care about it. If no
> one steps up soon, it will be removed in .33.
Never really worked and the reverse engineered (!) hardware specs are
incomplete, with the main developer having given up. I think it's fair
to say that this is a dead end. I suspect the hardware isn't even
manufactured any more, at least I haven't recently seen it.
> - 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.
> - stlc45xx. Another wireless driver that no one seems to care
> about. So sad. I guess no one will miss it when it goes away
> in .33.
p54spi has gotten probably 95% of the functionality of this, so it's
only really useful for looking at the calibration data loading on the
N800/N810 platform...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-09-03 8:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 4:14 Greg KH
2009-09-03 8:49 ` Johannes Berg [this message]
2009-09-03 12:48 ` Stefan Lippers-Hollmann
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=1251967786.3336.19.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®