All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Jouni Malinen" <j@w1.fi>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"Jithu Jance" <jithu@broadcom.com>
Subject: P2P Device support: how to deal with p2p_no_group_iface option
Date: Sat, 25 May 2013 13:23:47 +0200	[thread overview]
Message-ID: <51A09F43.5030004@broadcom.com> (raw)

Hi Jouni,

I looked into issues around hwsim p2p tests and got all but one p2p test 
passing now (test_autogo_tdls). I had to remove the p2p_no_group_iface 
option from the p2px.conf files, because otherwise it tries to change 
the P2P management interface into a P2P group interface. When using 
P2P_DEVICE and P2P management interface this is not allowed by 
mac80211_hwsim. Also for brcmfmac the P2P_DEVICE interface is dedicated 
and can only be added/deleted, but not changed. Not sure if that is true 
for iwlmvm as well.

So I would like to discuss how to deal with the p2p_no_group_iface 
option. As P2P_DEVICE is a new concept the name of the option may no 
longer match what it intends. Is the option to force all P2P operations 
to be done on a single interface, ie. wlan0 (or whatever is specified on 
the command line) and no P2P_DEVICE is to be created. Or should it 
change the interface from the command line as P2P group interface.

If we can make a decision here I can finalize the P2P_DEVICE support 
changes.

Regards,
Arend


             reply	other threads:[~2013-05-25 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 11:23 Arend van Spriel [this message]
2013-05-27  9:03 ` P2P Device support: how to deal with p2p_no_group_iface option Johannes Berg
2013-05-27 13:56   ` Arend van Spriel
2013-05-27 13:59     ` Johannes Berg
2013-05-27 14:03       ` Arend van Spriel
2013-05-27 15:53         ` Johannes Berg
2013-05-27 17:40           ` Arend van Spriel
2013-05-27 18:11     ` Jouni Malinen
2013-05-27 19:15       ` Johannes Berg
2013-05-27 19:20         ` Arend van Spriel
2013-05-27 19:27           ` Johannes Berg
2013-05-27 18:51     ` Marcel Holtmann

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=51A09F43.5030004@broadcom.com \
    --to=arend@broadcom.com \
    --cc=hostap@lists.shmoo.com \
    --cc=j@w1.fi \
    --cc=jithu@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --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.