Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org
Cc: wilson.tsao@atheros.com, mian.tuo@atheros.com,
	akira.iida@atheros.com, jinyong.ren@atheros.com,
	david.quan@atheros.com,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: [RFT] ath5k: add new PCI devices
Date: Fri, 11 Jun 2010 14:39:23 -0400	[thread overview]
Message-ID: <1276281563-18429-1-git-send-email-lrodriguez@atheros.com> (raw)

Found our PCI device list not up to date with respect
to the PCI device ID db for 0x168c for legacy (non-802.11)
devices:

https://pci-ids.ucw.cz/read/PC/168c/

There a few bogus ones there but I believe these are also
listed on our NDIS driver.

Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
---

[RFT] request to test, if any ath5k users have these devices.

Note: this e-mail is sent on a public mailing list. It is
      appreciated if you do reply to all and keep the
      public mailing list CC'd.

I just saw a patch to add 0xff19 internally but also spotted
the other ones on the PCI device ID db. Folks CC'd do you know if
these other are indeed ath5k device? Can you also confirm if
indeed 0xff19 is an AR5424 device?

  Luis

 drivers/net/wireless/ath/ath5k/base.c |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/drivers/net/wireless/ath/ath5k/base.c b/drivers/net/wireless/ath/ath5k/base.c
index 9d37c1a..cd44e02 100644
--- a/drivers/net/wireless/ath/ath5k/base.c
+++ b/drivers/net/wireless/ath/ath5k/base.c
@@ -103,6 +103,9 @@ static DEFINE_PCI_DEVICE_TABLE(ath5k_pci_id_table) = {
 	{ PCI_VDEVICE(ATHEROS, 0x001b) }, /* 5413 Eagle */
 	{ PCI_VDEVICE(ATHEROS, 0x001c) }, /* PCI-E cards */
 	{ PCI_VDEVICE(ATHEROS, 0x001d) }, /* 2417 Nala */
+	{ PCI_VDEVICE(ATHEROS, 0xff19) }, /* 5424 */
+	{ PCI_VDEVICE(ATHEROS, 0xff1c) },
+	{ PCI_VDEVICE(ATHEROS, 0xff1d) },
 	{ 0 }
 };
 MODULE_DEVICE_TABLE(pci, ath5k_pci_id_table);
-- 
1.6.3.3


                 reply	other threads:[~2010-06-11 18:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1276281563-18429-1-git-send-email-lrodriguez@atheros.com \
    --to=lrodriguez@atheros.com \
    --cc=akira.iida@atheros.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=david.quan@atheros.com \
    --cc=jinyong.ren@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mian.tuo@atheros.com \
    --cc=wilson.tsao@atheros.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