From: Christian Lamparter <chunkeey@googlemail.com>
To: Stephen Chen <Stephen.Chen@atheros.com>
Cc: Fabian Lenz <lenz_fabian@yahoo.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>
Subject: Re: [RFC] ar9170usb: add ar9170 usbid
Date: Tue, 15 Sep 2009 10:54:00 +0200 [thread overview]
Message-ID: <200909151054.00872.chunkeey@googlemail.com> (raw)
In-Reply-To: <618D4DE9D5223A45A46C48063FD64045109947ACC0@TAEXMB-01.global.atheros.com>
On Tuesday 15 September 2009 01:39:40 Stephen Chen wrote:
> Hi Christian,
>
> I could not find this VID/PID in INF file in Windows release.
> This ID combination could be obsolete.
you can get their vendor driver from here:
http://www.tp-link.com/support/download.asp?a=1&m=TL-WN821N
-> Driver Files/XP/arusb_xp.inf
--- snip --- Driver Files/${OS}/arusb_${OS}.inf
%ATHR.DeviceDesc.9170% = ATHRXP9170.ndi, USB\VID_0CF3&PID_1002
ATHR.DeviceDesc.9170 = "TP-LINK TL-WN821N 11N Wireless Adapter"
--- snip ---
Looks like they are trying to hijack Atheros' usbid space
by assigning custom product IDs.
This can confuse the unsuspected user and maybe break some stuff.
I'm not joking, this is an accident waiting to happen!
(see "rt2500usb vs. rt73usb" => http://patchwork.kernel.org/patch/45342/
for how this can go wrong.)
For now, you/[Atheros] should add the PID to your win driver as well
(so it's marked as _used_) and get in touch with TP-Link to come up
with a way for vendors - w/o their own VID - to get custom PIDs.
Regards,
Chr
next prev parent reply other threads:[~2009-09-15 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 18:46 missing device id in ar9170 driver Fabian Lenz
2009-09-14 21:08 ` [RFC] ar9170usb: add ar9170 usbid Christian Lamparter
2009-09-14 23:39 ` Stephen Chen
2009-09-15 8:54 ` Christian Lamparter [this message]
[not found] ` <200909150752.19146.lenz_fabian@yahoo.de>
2009-09-15 8:06 ` Christian Lamparter
2009-09-15 11:37 ` Stefan Lippers-Hollmann
2009-09-15 13:16 ` Christian Lamparter
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=200909151054.00872.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=Stephen.Chen@atheros.com \
--cc=lenz_fabian@yahoo.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.