From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Cc: "Nick Kossifidis" <mickflemm@gmail.com>, "Majo" <virec@inmail.sk>,
linux-wireless@vger.kernel.org,
"Michael Renzmann" <mrenzmann@madwifi.org>
Subject: Re: AR5006X on Fijitsu-Siemens Lifebook E8410 - not work
Date: Fri, 23 Nov 2007 12:39:25 +0100 [thread overview]
Message-ID: <200711231239.25603.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <200711231154.56712.hs4233@mail.mn-solutions.de>
On Friday 23 November 2007 11:54:56 Holger Schurig wrote:
> > Don't be fooled by the PCI ID - we already know that these
> > are not reliable to identify the chipset used on a
> > Atheros-based card. See also http://madwifi.org/ticket/1192.
Hmm, I also notices that in ticket 1192, neither the output
of "lspci" nor "lshw" doesn't even output the subsystem ID. The
MODULE_ALIAS() syntax doesn't seem to have a way to specify
subsystem IDs.
I have two Atheros based cards here, one is a D-Link DWL-G650,
one a Proxim 8470-WD. Both have the PCI ID 168C:0013. The
D-Link has the subsystem ID 1186:3a12, the Proxim has 14b7:0a40.
The driver for the Proxim card contains an INF file, which has
this section:
[Vendor]
; DisplayName Section DeviceID
; ----------- ------- --------
%LEX.DeviceDesc.CB22ag_G% = LEX_CB22ag_01, PCI\VEN_168C&DEV_0013&SUBSYS_0A1014B7
%LEX.DeviceDesc.CB22ag_S% = LEX_CB22ag_02, PCI\VEN_168C&DEV_0013&SUBSYS_AA1014B7
%LEX.DeviceDesc.CB22ab_G% = LEX_CB22ab_01, PCI\VEN_168C&DEV_0012&SUBSYS_0A001B47
%LEX.DeviceDesc.CB22ab_S% = LEX_CB22ab_02, PCI\VEN_168C&DEV_0012&SUBSYS_AA001B47
%LEX.DeviceDesc.CB22ab_A% = LEX_CB22ab_03, PCI\VEN_168C&DEV_0012&SUBSYS_1A001B47
%LEX.DeviceDesc.CB22g_G% = LEX_CB22g_01, PCI\VEN_168C&DEV_0013&SUBSYS_0A4014B7
%LEX.DeviceDesc.CB22g_S% = LEX_CB22g_02, PCI\VEN_168C&DEV_0013&SUBSYS_AA4014B7
%LEX.DeviceDesc.MB22ag% = LEX_MB22ag_01, PCI\VEN_168C&DEV_0013&SUBSYS_0A6014B7
%LEX.DeviceDesc.ORiNOCO% = LEX_ORiNOCO, PCI\VEN_168C&DEV_0013&SUBSYS_04101467
And, as it turns out, the driver for the Proxim card doesn't
recognize the D-Link card, because it looks not only at the
PCI-ID, but also at the subsystem ID.
It would be interesting to get a list of the subsystem IDs of
misdetected atheros-based WLAN cards.
next prev parent reply other threads:[~2007-11-23 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 22:10 AR5006X on Fijitsu-Siemens Lifebook E8410 - not work Majo
2007-11-22 23:38 ` Nick Kossifidis
2007-11-23 5:03 ` Michael Renzmann
2007-11-23 10:24 ` Nick Kossifidis
2007-11-23 10:54 ` Holger Schurig
2007-11-23 11:39 ` Holger Schurig [this message]
2007-11-25 10:07 ` Majo
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=200711231239.25603.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mickflemm@gmail.com \
--cc=mrenzmann@madwifi.org \
--cc=virec@inmail.sk \
/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