From: Johannes Berg <johannes@sipsolutions.net>
To: Greg KH <greg@kroah.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jouni Malinen <j@w1.fi>, Sujith <m.sujith@gmail.com>,
Sujith <Sujith.Manoharan@atheros.com>,
Senthilkumar Balasubramanian
<Senthilkumar.Balasubramanian@atheros.com>,
"John W. Linville" <linville@tuxdriver.com>,
Christoph Hellwig <hch@infradead.org>,
Vasanthakumar Thiagarajan <vasanth@atheros.com>
Subject: Re: Staging, place holder for better company/community development model
Date: Wed, 11 Mar 2009 10:08:11 +0100 [thread overview]
Message-ID: <1236762491.9658.85.camel@johannes.local> (raw)
In-Reply-To: <20090311050018.GB26202@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
On Tue, 2009-03-10 at 22:00 -0700, Greg KH wrote:
> > Except it doesn't work for most of the wireless drivers you've sucked in
> > without asking any wireless developers whether that makes any sense or
> > not.
>
> Any specific examples?
wlan-ng is the largest example, it's a load of crap, much of it being a
driver for hardware we already have drivers for, and the remaining
hardware being mostly unavailable these days. The driver served it's
purpose at a time, but the authors had years and years of time to bring
it in and never bothered. It needs to be incorporated into a
rearchitectured orinoco driver, or so.
I also remember objecting to rt2860/rt2870, and the only good thing that
has come out of adding those is a spatch that might otherwise not have
been applied to those drivers. Afaict, no new people have helped with
rt2800, the rt2x00 based driver for this hardware, because they've come
in contact with rt2860/rt2870.
I don't remember any discussion about rtl8187se either.
All of those bring their own 802.11 stack, and changing to the Linux one
will /necessarily/ require an entire rewrite of the drivers because the
stacks operate /completely/ differently. Even the clean, in-kernel
bcm43xx driver was rewritten to b43 for mac80211, and rtl8187se ships
the old ieee80211_softmac code that I and a few others wrote...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-11 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 7:14 Luis R. Rodriguez
2009-03-03 7:30 ` Greg KH
2009-03-03 7:45 ` Luis R. Rodriguez
2009-03-03 15:56 ` Greg KH
2009-03-08 12:07 ` Johannes Berg
2009-03-08 22:33 ` Greg KH
2009-03-09 7:21 ` Johannes Berg
2009-03-09 19:41 ` Greg KH
2009-03-09 21:20 ` Johannes Berg
2009-03-11 5:00 ` Greg KH
2009-03-11 9:08 ` Johannes Berg [this message]
2009-03-11 16:02 ` Greg KH
2009-03-11 19:33 ` J.R. Mauro
2009-04-07 23:15 ` Greg KH
2009-03-08 23:02 ` Leon Woestenberg
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=1236762491.9658.85.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Senthilkumar.Balasubramanian@atheros.com \
--cc=Sujith.Manoharan@atheros.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=j@w1.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m.sujith@gmail.com \
--cc=mcgrof@gmail.com \
--cc=vasanth@atheros.com \
/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®