linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <fedora@leemhuis.info>
To: Luis Correia <luis.f.correia@gmail.com>
Cc: Thorsten Leemhuis <fedora@leemhuis.info>,
	Greg KH <greg@kroah.com>,
	rt2400-devel@lists.sourceforge.net,
	linux-wireless@vger.kernel.org
Subject: Re: rtl2860 driver in mainline?
Date: Tue, 28 Oct 2008 09:06:18 +0100	[thread overview]
Message-ID: <4906C7FA.8040804@leemhuis.info> (raw)
In-Reply-To: <efe7343f0810280048j57158020n67176d7a56f0bbea@mail.gmail.com>

On 28.10.2008 08:48, Luis Correia wrote:
> On Tue, Oct 28, 2008 at 07:03, Thorsten Leemhuis <fedora@leemhuis.info> wrote:
>> On 28.10.2008 01:49, Greg KH wrote:
>>> 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.
>> Does it really make sense to include a driver when a different one for
>> mainline inclusion is being actively developed? It might give some
>> developers the impression that it's worth spending time improving the
>> rtl2860/2870 drivers -- which might be wasted time in the end.
> 
> Is it just me or you are suggesting we use the Ralink supplied driver,
> with its own wireless stack, rather then work with the rt2x00 team?

No, I'm definitely not suggesting that! In fact it's the other way 
around: I wondering if it's more harm- than helpful to include the 
current Ralink supplied driver as staging driver.

Or, to say it more directly: I think the Ralink drivers should not get 
included as staging driver, as that might track away resources from the 
rt2x00 effort (just my 2 cent as LKML and linux-wlan lurker of course).

 > [...]
>>> 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.
>>>
>>> Any pointers are appreciated.
>> You can find a few patches (needed for 2.6.26 and 2.6.27 iirc; not sure if
>> they are enough to make it work on current mainline) for both rt2860 and
>> rt2870 in CVS for RPM Fusion:
>>
>> http://cvs.rpmfusion.org/viewvc/rpms/rt2860-kmod/devel/?root=free
>> http://cvs.rpmfusion.org/viewvc/rpms/rt2870-kmod/devel/?root=free
> 
> This seems to be only a set of 'mixed-up-lets-just-use-ralink-code' patchset.

Sure -- nevertheless those patches might be helpful for Greg, that's why 
I pointed him there.

BTW, RPM Fusion provides the drivers just as a interim solution for 
Fedora users, as there was quite some demand for it (even from one well 
known kernel developer who actually created the initial rt2860 package 
for Livna/RPM Fusion); soon after a working and stable driver with a 
similar featureset is in mainline and shipped as update by Fedora we'll 
stop providing those drivers from Ralink.

> p.s. I apologize in advance if I misunderstood the meaning of the
> original reply.

np ;-)

CU
knurd

  parent reply	other threads:[~2008-10-28  8:06 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
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 [this message]
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=4906C7FA.8040804@leemhuis.info \
    --to=fedora@leemhuis.info \
    --cc=greg@kroah.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luis.f.correia@gmail.com \
    --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 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).