From: Greg KH <greg@kroah.com>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: rt2400-devel@lists.sourceforge.net, linux-wireless@vger.kernel.org
Subject: Re: rtl2860 driver in mainline?
Date: Mon, 27 Oct 2008 23:10:23 -0700 [thread overview]
Message-ID: <20081028061023.GA6568@kroah.com> (raw)
In-Reply-To: <a32f33a40810272248j5ee755ccoc8f6a8c8d5338cb8@mail.gmail.com>
On Tue, Oct 28, 2008 at 06:48:31AM +0100, Ivo Van Doorn wrote:
> Hi,
>
> > So, on my quest to suck up every out-of-tree driver and get it into the
> > main kernel tree (drivers/staging/ to start with), I've been pointed at
> > the rtl2860 driver.
>
> in that case make sure you include rt2870 on your list as well then. ;)
Do you have a pointer to it?
> > Does anyone know of a "cleaned up" version of this driver that is
> > newer/better than the one on ralink's web site? I found the
> > 2008_0918_RT2860_Linux_STA_v1.8.0.0.tar.bz2 version there, and will
> > start with that if no one else has yet.
>
> rt2800pci/rt2800usb development is in progress in the rt2x00.git
> experimental branch:
> http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=shortlog;h=experimental
>
> The current status is that rt2800usb has working RX with some warnings
> regarding the
> RX signal, and a non functional TX. rt2800pci isn't complete yet.
>
> So far progress has been very slow because of lack of time, so any help with the
> development of the drivers is welcome.
Is this a port of the tarball driver to the in-kernel wireless stack, or
starting over from scratch?
As it's not really working, do you mind if I just dump the tarball
driver into the staging tree for users to use now (hint, they already
are, the distros are shipping that driver as a kernel module package),
and then when this "real" driver is up and working properly, we can drop
the staging version?
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-28 6:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 0:49 rtl2860 driver in mainline? Greg KH
2008-10-28 5:48 ` Ivo Van Doorn
2008-10-28 6:10 ` Greg KH [this message]
2008-10-28 6:23 ` Ivo Van Doorn
2008-10-28 14:59 ` Dan Williams
2008-10-28 17:24 ` Luis R. Rodriguez
2008-10-28 7:03 ` Thorsten Leemhuis
2008-10-28 7:48 ` Luis Correia
2008-10-28 8:01 ` Luis R. Rodriguez
2008-10-28 8:06 ` Thorsten Leemhuis
2008-10-28 17:10 ` Greg KH
2008-10-28 7:56 ` Johannes Berg
2008-10-28 8:02 ` Luis R. Rodriguez
2008-10-28 8:06 ` Luis Correia
2008-10-28 17:09 ` Greg KH
2008-10-28 8:12 ` Johannes Berg
2008-10-28 8:17 ` Luis R. Rodriguez
2008-10-28 8:19 ` Johannes Berg
2008-10-28 17:08 ` Greg KH
2008-10-28 18:35 ` Johannes Berg
2008-10-28 22:45 ` Greg KH
2008-10-29 10:13 ` Dan Williams
2008-10-29 16:30 ` Greg KH
2008-10-30 4:02 ` Dan Williams
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=20081028061023.GA6568@kroah.com \
--to=greg@kroah.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.