linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Forest Bond <forest@alittletooquiet.net>
To: drago01 <drago01@gmail.com>
Cc: Ivo van Doorn <ivdoorn@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Are these Ralink chips supported?
Date: Tue, 26 Aug 2008 15:27:31 -0400	[thread overview]
Message-ID: <20080826192731.GC26037@storm.local.network> (raw)
In-Reply-To: <f6ca9fed0808261218w20334033h7eef71dba8400ac8@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

Hi,

On Tue, Aug 26, 2008 at 09:18:59PM +0200, drago01 wrote:
> On Tue, Aug 26, 2008 at 9:16 PM, Forest Bond <forest@alittletooquiet.net> wrote:
> > On Wed, Aug 06, 2008 at 10:14:10AM +0200, Ivo van Doorn wrote:
> >> On Tuesday 05 August 2008, Forest Bond wrote:
> >> > 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
> >
> > Okay, the RT2870 driver from Ralink works with this device, but it seems to be a
> > bit quirky:
> >
> >  * The device has to be brought up and down a few times before NetworkManager
> >   sees it.  I'm not sure what NetworkManager is cueing off of.
> >
> >  * I was unable to get the thing to associate and come up using
> >   iwconfig/ifconfig.  Might have been my range on that AP, though, since I was
> >   shooting for an unencrypted network that is a not the closest network in my
> >   building.
> >
> >  * Usual odd bits with vendor drivers like odd build system subtleties and
> >   seemingly unnecessary configuration files (does anyone really care to fiddle
> >   with those, or doesn't everyone just want things to work with the standard
> >   configuration mechanisms like I do?).
> >
> > Is there an effort to move this driver in-tree?  The license is GPL.
> 
> Thats what Ivo is doing, port the driver to rt2x00 to make it
> acceptable for merging.

Okay, sorry if I misunderstood.  Is this driver usable and, if so, where can the
code be found?

Thanks,
Forest
-- 
Forest Bond
http://www.alittletooquiet.net
http://www.pytagsfs.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-08-26 19:25 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
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 [this message]
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=20080826192731.GC26037@storm.local.network \
    --to=forest@alittletooquiet.net \
    --cc=drago01@gmail.com \
    --cc=ivdoorn@gmail.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).