linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>
Subject: [RFC] ath9k: advertise support for p2p
Date: Thu, 16 Sep 2010 15:20:11 +0200	[thread overview]
Message-ID: <1284643211.3731.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100916125821.369545798@sipsolutions.net>

Obvious patch really, but I guess the filtering thing should be figured
out first ... this is just for people who want to keep using ath9k after
updates to the supplicant and already have a patched kernel.

---
 drivers/net/wireless/ath/ath9k/init.c |    2 ++
 1 file changed, 2 insertions(+)

--- wireless-testing.orig/drivers/net/wireless/ath/ath9k/init.c	2010-09-16 14:08:48.000000000 +0200
+++ wireless-testing/drivers/net/wireless/ath/ath9k/init.c	2010-09-16 14:09:03.000000000 +0200
@@ -638,6 +638,8 @@ void ath9k_set_hw_capab(struct ath_softc
 		hw->flags |= IEEE80211_HW_MFP_CAPABLE;
 
 	hw->wiphy->interface_modes =
+		BIT(NL80211_IFTYPE_P2P_GO) |
+		BIT(NL80211_IFTYPE_P2P_CLIENT) |
 		BIT(NL80211_IFTYPE_AP) |
 		BIT(NL80211_IFTYPE_STATION) |
 		BIT(NL80211_IFTYPE_ADHOC) |



      parent reply	other threads:[~2010-09-16 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 12:58 [PATCH 0/2] p2p interface types Johannes Berg
2010-09-16 12:58 ` [PATCH 1/2] cfg80211/nl80211: introduce p2p device types Johannes Berg
2010-09-16 12:58 ` [PATCH 2/2] mac80211: add p2p device type support Johannes Berg
2010-09-16 18:22   ` Luis R. Rodriguez
2010-09-16 18:30     ` Johannes Berg
2010-09-16 18:40       ` Luis R. Rodriguez
2010-09-16 18:42         ` Johannes Berg
2010-09-16 18:56           ` Luis R. Rodriguez
2010-09-16 13:20 ` Johannes Berg [this message]

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=1284643211.3731.3.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).