From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jett Chen <jett_chen@ralinktech.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Questions about rt2800usb
Date: Fri, 8 Apr 2011 08:50:10 +0200 [thread overview]
Message-ID: <201104080850.11086.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <4D9E316E.4000908@lwfinger.net>
Hi Larry,
Am Donnerstag, 7. April 2011 schrieb Larry Finger:
> 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.
rt2800pci is quite stable already (at least for me). So removing rt2860sta
would be ok I think.
> 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?
I'm not quite sure about rt2800usb. It's still a bit immature in my opinion.
On the other hand, as long as people just use the staging driver instead of
reporting bugs for rt2800usb that situation won't change that fast.
Helmut
next prev parent reply other threads:[~2011-04-08 6:52 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
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 [this message]
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=201104080850.11086.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=Larry.Finger@lwfinger.net \
--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 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.