From: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
To: linux-wireless@vger.kernel.org
Subject: Re: Are these Ralink chips supported?
Date: Wed, 6 Aug 2008 16:15:53 +0000 (UTC) [thread overview]
Message-ID: <g7cinp$g4u$1@ger.gmane.org> (raw)
In-Reply-To: 200808061014.10483.IvDoorn@gmail.com
On Wed, 06 Aug 2008 10:14:10 +0200, Ivo van Doorn wrote:
> On Tuesday 05 August 2008, Forest Bond wrote:
>> Hi,
>>
>> I'm having a hard time figuring out if the following wireless chips are
>> supported:
>>
>> * RT2770 + RT2720
>
> I *think* this is the rt2870 driver. The in-kernel driver is under
> development
That is indeed rt2800usb. I don't have any rt2800usb hardware myself yet,
but I would like to test rt2800pci when testable code is available. Any
ETA?
next prev parent reply other threads:[~2008-08-06 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 16:32 Are these Ralink chips supported? Forest Bond
2008-08-06 3:47 ` Iwo Mergler
2008-08-06 8:14 ` Ivo van Doorn
2008-08-06 16:15 ` Daniel Gimpelevich [this message]
2008-08-06 16:47 ` Ivo van Doorn
2008-08-26 19:16 ` Forest Bond
2008-08-26 19:18 ` drago01
2008-08-26 19:27 ` Forest Bond
2008-08-26 19:54 ` Ivo van Doorn
2008-08-27 1:21 ` 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='g7cinp$g4u$1@ger.gmane.org' \
--to=daniel@gimpelevich.san-francisco.ca.us \
--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).