From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Linux wireless" <linux-wireless@vger.kernel.org>,
"Przemyslaw Kulczycki" <azrael@autocom.pl>,
LKML <linux-kernel@vger.kernel.org>,
"Gábor Stefanik" <netrolller.3d@gmail.com>
Subject: Re: [PATCH] wireless: fix supported cards for rtl8187
Date: Thu, 9 Jul 2009 05:18:45 +0100 [thread overview]
Message-ID: <3ace41890907082118h52764c98i7ebd9365bcd69b2c@mail.gmail.com> (raw)
In-Reply-To: <4A551B43.3020104@gmail.com>
On Wed, Jul 8, 2009 at 11:18 PM, Marcin Slusarz<marcin.slusarz@gmail.com> wrote:
> Hin-Tak Leung wrote:
>> Is there a v1, and what does it use?
>
> I don't know.
2009/7/8 Gábor Stefanik <netrolller.3d@gmail.com>:
> On Wed, Jul 8, 2009 at 11:49 PM, Hin-Tak Leung<hintak.leung@gmail.com> wrote:
>> Is there a v1, and what does it use?
>
> I have the v1, it is rt73-based. (v3 is rt2070, not rt3070, though.)
I guess I have two questions: (1) are the 3 variants labelled in that
way as such v1/v2/v3 (on the box,
or one of the USB device identity queries)? (2) are they distinguished
by different product IDs?
The point is that the commit (which only changes the help message) is
only appropriate if they are labelled as v1/v2/v3 and not
distinguished by different product IDs. If they are distinguished by
different product IDs and the current codes for the three drivers bind
correctly to each, then the change is only relevant to people who
manually build their kernel and want to build one driver but not the
others. (i.e. instead of distros which ship the full set of driver
modules). Which goes to my first question...
if they are not labelled v1/v2/v3 as such, it may be more
useful/informative to change to
[some variant of ] ... [(other variants are supported by the
rt2070/rt3070 modules)]
instead of just adding [v2] to the end.
next prev parent reply other threads:[~2009-07-09 4:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 20:03 Marcin Slusarz
2009-07-08 21:49 ` Hin-Tak Leung
2009-07-08 22:18 ` Marcin Slusarz
2009-07-09 4:18 ` Hin-Tak Leung [this message]
2009-07-09 4:44 ` Larry Finger
2009-07-09 10:47 ` Hin-Tak Leung
2009-07-09 11:14 ` Marcin Slusarz
2009-07-09 12:40 ` Hin-Tak Leung
2009-07-09 12:49 ` Gábor Stefanik
2009-07-09 13:11 ` Marcin Slusarz
2009-07-11 4:33 ` Hin-Tak Leung
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=3ace41890907082118h52764c98i7ebd9365bcd69b2c@mail.gmail.com \
--to=hintak.leung@gmail.com \
--cc=azrael@autocom.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcin.slusarz@gmail.com \
--cc=netrolller.3d@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
all inboxes | Powered by JetHome®