mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Roland Dreier <roland@kernel.org>,
	linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.38: rt2800usb: driver is crashing the kernel
Date: Mon, 2 May 2011 19:46:49 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1105021944560.14515@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1104261923390.3894@p34.internal.lan>



On Tue, 26 Apr 2011, Justin Piszcz wrote:

>
>
> On Tue, 26 Apr 2011, Larry Finger wrote:
>
>>> 
>>> I am trying a different driver now: rt2870sta
>>> I've read a few reports this may be the 'proper' one to use.
>>> So far so good, no lag or anything and I did not have to set power off
>>> either.
>> 
>> Driver rtl2870sta is not the proper one to use. In fact, a patch to delete 
>> rt2860sta and rt2870sta from the kernel was queued yesterday, and they will 
>> be gone by the time 2.6.40 is released.
>> 
>> New firmware for rt2800usb was just accepted into the linux-firmware git 
>> tree. Please obtain a copy and try it.
>> 
>> Larry
>>

Hi,

Just an update, this driver has been solid so far:
rt2870sta

With the Media Link 150 USB stick, not a single crash yet--
The rt2800usb driver is laggy and crashes the kernel (as of 2.6.38.x)--
Is there a possiblity to get rtl2870sta into the mainline?
It is the best wireless driver I've used for Linux with various usb wifi
adapters--

# uptime
  19:44:28 up 4 days, 10:16,  2 users,  load average: 1.51, 1.56, 1.25

Justin.


  parent reply	other threads:[~2011-05-02 23:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 15:47 2.6.38: rt2800usb: high latency (1000ms)? Justin Piszcz
2011-04-13 15:59 ` Ivo Van Doorn
2011-04-13 16:01   ` Justin Piszcz
     [not found]     ` <BANLkTinxkXi6WnAyXoZLDR+uyL+TmevuPw@mail.gmail.com>
2011-04-13 16:25       ` Daniel Halperin
2011-04-13 17:57         ` Justin Piszcz
2011-04-13 18:37           ` Daniel Halperin
2011-04-13 20:13             ` Justin Piszcz
2011-04-13 20:31               ` Daniel Halperin
2011-04-13 20:36                 ` Justin Piszcz
2011-04-13 22:26                   ` Joshua Scoggins
2011-04-14  5:38                 ` Igor Plyatov
2011-04-14  5:17               ` Igor Plyatov
2011-04-13 16:11   ` Walter Goldens
2011-04-13 18:44   ` Marc Dietrich
2011-04-25 18:35 ` 2.6.38: rt2800usb: driver is crashing the kernel Justin Piszcz
2011-04-25 20:52   ` Roland Dreier
2011-04-25 20:56     ` Justin Piszcz
2011-04-26 10:22     ` Justin Piszcz
2011-04-26 21:53       ` Justin Piszcz
2011-04-26 22:30         ` Larry Finger
2011-04-26 23:31           ` Justin Piszcz
2011-04-27  0:29             ` Jano
2011-05-02 23:46             ` Justin Piszcz [this message]
2011-05-03  1:15               ` Larry Finger
2011-05-03 12:53                 ` Walter Goldens
2011-05-03 13:08                   ` Jools Wills
2011-05-26 16:24                     ` Justin Piszcz

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=alpine.DEB.2.02.1105021944560.14515@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=roland@kernel.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

all inboxes | Powered by JetHome®