From: Greg KH <greg@kroah.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: proski@gnu.org, linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: at76_usb driver status
Date: Sat, 4 Oct 2008 23:16:03 -0700 [thread overview]
Message-ID: <20081005061603.GB28533@kroah.com> (raw)
In-Reply-To: <87y713y48r.fsf@nokia.com>
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 :)
See my previous posts on lkml for details on the staging tree if you
have questions about it.
So for now, if no one really screams, I'll put Pavel's driver into the
drivers/staging/ tree so that users can use their devices. When your
driver is merged, we can merely delete this driver instead.
Sound good?
> > And, did you merge the USB DFU code into the driver itself?
>
> Yes, someone implemented it in driver.
>
> > Having that kind of functionality in the USB core is fine with me if
> > you want me to add that portion there, no reason it needs to be
> > burried in individual drivers.
>
> USB DFU is a standard? So it seems:
>
> http://wiki.openmoko.org/wiki/USB_DFU
>
> Heh, I didn't know this. I though it was some Atmel proprietary
> interface :)
Oh yeah, I wrote portions of that spec, oh so long ago :)
> I might be interested in getting DFU into USB core, because I would
> like to learn more about USB. But first I need to get at76_usb stable.
Fair enough, patches are always welcome.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-05 6:17 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 [this message]
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
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=20081005061603.GB28533@kroah.com \
--to=greg@kroah.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).