From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
"IvDoorn@gmail.com" <IvDoorn@gmail.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"helmut.schaa@googlemail.com" <helmut.schaa@googlemail.com>
Subject: Re: [rt2x00-users] [PATCH] wireless: rt2x00: rt2800usb add more devices ids
Date: Sun, 15 Apr 2012 20:09:21 +0200 [thread overview]
Message-ID: <4F8B0ED1.5050302@01019freenet.de> (raw)
In-Reply-To: <201C9B63-C214-4D44-B3D0-44948F9DE260@gmail.com>
Hello Gertjan,
thank you for your response!
Gertjan van Wingerde wrote:
[...]
> It is impossible to test each and every device that uses a Ralink
> chipset. Therefore we run tests on the chipsets only, and simply list
> all devices that contain these chipsets.
>
> Granted, we are having issues with some of the chipsets, but that
> should not prevent adding other devices that use the same chipset to
> the driver.
It would help for making decisions on which brand to buy, if there were
a notice in the source code, e.g.: _device successfully tested
(802.11abgn)_ - other devices don't get any comment.
This way, I would be completely content with the practice to fire in
blindly every ID of each existing device containing a Ralink chipset.
Kind regards,
Andreas
next prev parent reply other threads:[~2012-04-15 18:11 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
2012-04-15 12:03 ` Andreas Hartmann
2012-04-15 13:04 ` Gertjan van Wingerde
2012-04-15 18:09 ` Andreas Hartmann [this message]
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=4F8B0ED1.5050302@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=IvDoorn@gmail.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.com \
--cc=xose.vazquez@gmail.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).