lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 9 Jul 2009 05:18:45 +0100
From:	Hin-Tak Leung <hintak.leung@...il.com>
To:	Marcin Slusarz <marcin.slusarz@...il.com>
Cc:	"John W. Linville" <linville@...driver.com>,
	Linux wireless <linux-wireless@...r.kernel.org>,
	Przemyslaw Kulczycki <azrael@...ocom.pl>,
	LKML <linux-kernel@...r.kernel.org>,
	Gábor Stefanik <netrolller.3d@...il.com>
Subject: Re: [PATCH] wireless: fix supported cards for rtl8187

On Wed, Jul 8, 2009 at 11:18 PM, Marcin Slusarz<marcin.slusarz@...il.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@...il.com>:
> On Wed, Jul 8, 2009 at 11:49 PM, Hin-Tak Leung<hintak.leung@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ