From: Steev Klimaszewski <steev@genesi-usa.com>
To: Walter Goldens <goldenstranger@yahoo.com>
Cc: Jett Chen <jett_chen@ralinktech.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Questions about rt2800usb
Date: Thu, 7 Apr 2011 18:03:27 -0500 [thread overview]
Message-ID: <BANLkTikRMATHAUmsQa8T4LD4_C9T76asAQ@mail.gmail.com> (raw)
In-Reply-To: <73768.20361.qm@web161614.mail.bf1.yahoo.com>
On Thu, Apr 7, 2011 at 5:19 PM, Walter Goldens <goldenstranger@yahoo.com> wrote:
>
>> I know from experience that the
>> staging driver rt82860sta has been replaced by rt2800pci and
>> I plan to push a patch deleting the driver from staging.
>>
>> It appears that rt2870sta has been replaced by rt2800usb.
>> Is that correct? If so, I will also include the deletion of
>> that driver from staging in the patch.
>>
>> I noticed that rt2870sta includes a few USB IDs not found
>> in rt2800usb, namely:
>>
>> 0x2001:0x3c09, 0x2001:0x3c0a, and 0x2019:0xed14.
>>
>> Any reasons why these should not be included in rt2800usb?
>>
>> Please let me know of any objections to removing those two
>> staging drivers.
>
> Here's my vote against removing the rt2870sta from staging. Some longstanding issues with latency and duplicate packets (rt307x) are persistent with rt2800usb, whereas rt2870sta works fine.
>
> my two cents
>
> Walter
Personally, I've had the opposite (since the patch to disable power
management on rt2800usb.) rt2870sta hasn't been noticeably more
stable, and in fact, I tend to see div0 bugs quite often when using
it. That said, I'm using Azurewave rt3070s.
--
Steev Klimaszewski <steev@genesi-usa.com>
Senior Software Engineer, Genesi USA, Inc.
next prev parent reply other threads:[~2011-04-07 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 21:49 Questions about rt2800usb Larry Finger
2011-04-07 22:19 ` Walter Goldens
2011-04-07 23:03 ` Steev Klimaszewski [this message]
2011-04-08 9:32 ` Walter Goldens
2011-04-08 9:42 ` Ivo Van Doorn
2011-04-08 9:54 ` Walter Goldens
2011-04-08 12:21 ` Walter Goldens
2011-04-08 12:41 ` Helmut Schaa
2011-04-08 16:31 ` Walter Goldens
2011-04-08 6:50 ` Helmut Schaa
2011-04-08 7:42 ` Ivo Van Doorn
-- strict thread matches above, loose matches on Subject: below --
2011-04-10 16:55 Xose Vazquez Perez
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=BANLkTikRMATHAUmsQa8T4LD4_C9T76asAQ@mail.gmail.com \
--to=steev@genesi-usa.com \
--cc=Larry.Finger@lwfinger.net \
--cc=goldenstranger@yahoo.com \
--cc=jett_chen@ralinktech.com \
--cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).