linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Damien Thébault" <damien@dtbo.net>
To: linux-wireless@vger.kernel.org
Cc: Kalle Valo <kvalo@codeaurora.org>,
	QCA ath9k Development <ath9k-devel@qca.qualcomm.com>
Subject: Re: [PATCH] ath9k: Add Dell Wireless 1601 with wowlan capability
Date: Fri, 14 Apr 2017 11:53:42 +0200	[thread overview]
Message-ID: <20170414115333.64abcba2@anakin> (raw)
In-Reply-To: <20170406135110.3f4d1f92@anakin>

Hello,

Sorry about this, but when I first sent this patch it didn't reach the
maintainers in Cc because of spam filters. My MX IP is now in spamhaus
PBL whitelist so this should work this time.


Add the Dell Wireless 1601 card as an AR9462 in the ath9k pci list.
Note that the wowlan feature is supported and has been tested
successfully.

Signed-off-by: Damien Th=C3=A9bault <damien@dtbo.net>
---
 drivers/net/wireless/ath/ath9k/pci.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/drivers/net/wireless/ath/ath9k/pci.c b/drivers/net/wireless/at=
h/ath9k/pci.c
index aff473dfa10d..7b7627f85d3a 100644
--- a/drivers/net/wireless/ath/ath9k/pci.c
+++ b/drivers/net/wireless/ath/ath9k/pci.c
@@ -383,6 +383,11 @@ static const struct pci_device_id ath_pci_id_table[] =
=3D {
 			 0x10CF, /* Fujitsu */
 			 0x1783),
 	  .driver_data =3D ATH9K_PCI_WOW },
+	{ PCI_DEVICE_SUB(PCI_VENDOR_ID_ATHEROS,
+			 0x0034,
+			 PCI_VENDOR_ID_DELL,
+			 0x020B),
+	  .driver_data =3D ATH9K_PCI_WOW },
=20
 	/* Killer Wireless (2x2) */
 	{ PCI_DEVICE_SUB(PCI_VENDOR_ID_ATHEROS,
--=20
2.12.2

  reply	other threads:[~2017-04-14  9:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 11:51 [PATCH] ath9k: Add Dell Wireless 1601 with wowlan capability Damien Thébault
2017-04-14  9:53 ` Damien Thébault [this message]
2017-04-20  6:59   ` Kalle Valo
2017-04-19 13:59 ` Kalle Valo

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=20170414115333.64abcba2@anakin \
    --to=damien@dtbo.net \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=kvalo@codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).