From: Greg KH <greg@kroah.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Kalle Valo <kalle.valo@iki.fi>,
proski@gnu.org, linville@tuxdriver.com,
linux-wireless@vger.kernel.org
Subject: Re: at76_usb driver status
Date: Mon, 6 Oct 2008 11:35:20 -0700 [thread overview]
Message-ID: <20081006183520.GA17647@kroah.com> (raw)
In-Reply-To: <1223306593.31040.33.camel@dhcp-100-3-195.bos.redhat.com>
On Mon, Oct 06, 2008 at 11:23:13AM -0400, Dan Williams wrote:
> On Sat, 2008-10-04 at 23:16 -0700, Greg KH wrote:
> > On Sun, Oct 05, 2008 at 08:56:20AM +0300, Kalle Valo wrote:
> > > Greg KH <greg@kroah.com> writes:
> > > > In my quest to suck drivers into drivers/staging/ I noticed that the
> > > > at76_usb driver is being shipped by both Fedora and Ubuntu in their
> > > > kernels.
> > >
> > > Yes, that's the original at76_usb driver which has it's own 802.11
> > > stack. Pavel Rosking was the maintainer of that driver. Based on the
> > > feedback in linux-wireless I then started porting the driver to use
> > > mac80211.
> > >
> > > (Maybe I should have renamed the port to something else than at76_usb
> > > because having two different drivers with the same name creates
> > > confusion.)
> > >
> > > > So I was wondering what the status of this driver is, and if I
> > > > could/should add it to drivers/staging/?
> > >
> > > The original at76_usb is working quite well, but it's unacceptable for
> > > the mainline because we cannot have two 802.11 stacks in kernel.
> >
> > I understand this, but for the issue of the drivers/staging/ tree, it's
> > ok for us to have as many 802.11 stacks in the kernel as we can cram in
> > there :)
>
> Well, you have to ask yourself then, what's the point of putting that
> driver with it's own 802.11 stack into staging when it's never going to
> go into the mainline kernel until it uses mac80211?
Because at least 2 distros currently ship their kernels with it (Fedora
and Ubuntu), and people have that hardware today and want to use it with
Linux.
> Doesn't that direct effort away from porting the driver to mac80211,
> giving legitimacy to code that will never, ever get upstream until
> it's substantially rewritten anyway? Ideally we put Kalle's 802.11
> port in staging and then people can actually move things forward.
>
> Same thing for linux-wlan-ng really; if people just keep fixing bugs and
> keep improving p80211 without porting it to the standard kernel wireless
> bits, what's the point of having it in staging?
Users using their hardware with Linux today.
I'll gladly drop it from drivers/staging when the "real" version hits
mainline, until then, it should stay in staging, as that is the whole
point of it.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-06 18:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 21:07 at76_usb driver status Greg KH
2008-10-02 16:20 ` Luis R. Rodriguez
2008-10-05 6:32 ` Kalle Valo
2008-10-05 5:56 ` Kalle Valo
2008-10-05 6:13 ` Marcel Holtmann
2008-10-05 6:22 ` Kalle Valo
2008-10-05 6:14 ` Kalle Valo
2008-10-05 6:16 ` Greg KH
2008-10-05 6:29 ` Kalle Valo
2008-10-05 15:14 ` Greg KH
2008-10-06 5:28 ` Pavel Roskin
2008-10-06 5:39 ` Kalle Valo
2008-10-06 5:42 ` Pavel Roskin
2008-10-06 6:10 ` Kalle Valo
2008-10-06 6:26 ` Pavel Roskin
2008-10-05 6:41 ` Marcel Holtmann
2008-10-05 15:14 ` Greg KH
2008-10-05 16:17 ` Marcel Holtmann
2008-10-05 22:57 ` Greg KH
2008-10-06 15:23 ` Dan Williams
2008-10-06 10:23 ` Luis R. Rodriguez
2008-10-06 18:21 ` Marcel Holtmann
2008-10-06 18:35 ` Greg KH [this message]
2008-10-06 20:12 ` Dan Williams
2008-10-06 20:31 ` John W. Linville
2008-10-06 20:42 ` Johannes Berg
2008-10-06 21:39 ` John W. Linville
2008-10-06 22:54 ` Greg KH
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=20081006183520.GA17647@kroah.com \
--to=greg@kroah.com \
--cc=dcbw@redhat.com \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.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).