linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com,
	IvDoorn@gmail.com, linville@tuxdriver.com, gwingerde@gmail.com,
	helmut.schaa@googlemail.com
Subject: Re: [rt2x00-users] [PATCH] wireless: rt2x00: rt2800usb add more devices ids
Date: Sun, 15 Apr 2012 11:19:33 +0200	[thread overview]
Message-ID: <4F8A92A5.8090707@gmail.com> (raw)
In-Reply-To: <4F8A6CB6.4080006@01019freenet.de>

On 04/15/2012 08:37 AM, Andreas Hartmann wrote:

> Did you test them? What did you test exactly? What exactly works, what
> does not?

NO. NOTHING . I DON'T KNOW. But...

> It doesn't mean anything, if they work with the legacy driver.

..., the chips in these devices are *identified* . They perform so well
or so badly like those that are already in the driver(rt2800usb).

> Linksys WUSB600Nv2 e.g. works fine with the legacy driver, but only
> limited (if at all) with rt2800usb yet.

<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/wireless/rt2x00/Kconfig;h=299c3879582da14e12ca00d7f11184da8c61bed7;hb=HEAD#l83>

config RT2800USB_RT35XX
	bool "rt2800usb - Include support for rt35xx devices ( *EXPERIMENTAL* )"
	depends on *EXPERIMENTAL*

  reply	other threads:[~2012-04-15  9:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15  0:09 [PATCH] wireless: rt2x00: rt2800usb add more devices ids Xose Vazquez Perez
2012-04-15  6:37 ` [rt2x00-users] " Andreas Hartmann
2012-04-15  9:19   ` Xose Vazquez Perez [this message]
2012-04-15 12:03     ` Andreas Hartmann
2012-04-15 13:04       ` Gertjan van Wingerde
2012-04-15 18:09         ` Andreas Hartmann
2012-04-15 12:25 ` Gertjan van Wingerde

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=4F8A92A5.8090707@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=IvDoorn@gmail.com \
    --cc=andihartmann@01019freenet.de \
    --cc=gwingerde@gmail.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=users@rt2x00.serialmonkey.com \
    /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).