Remove documentation for label option in p2p_connect
P2P use cases do not allow use of Label config method and the earlier code for this has already been removed, but this documentation was not updated at the same time. Signed-hostap: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
481234cf1a
commit
61ff2c8080
1 changed files with 4 additions and 5 deletions
|
@ -110,7 +110,7 @@ the desired configuration method. For example, "p2p_prov_disc
|
|||
us and "p2p_prov_disc 02:01:02:03:04:05 keypad" would request the peer
|
||||
to enter a PIN that we display.
|
||||
|
||||
p2p_connect <peer device address> <pbc|pin|PIN#> [label|display|keypad]
|
||||
p2p_connect <peer device address> <pbc|pin|PIN#> [display|keypad]
|
||||
[persistent] [join|auth] [go_intent=<0..15>] [freq=<in MHz>]
|
||||
|
||||
Start P2P group formation with a discovered P2P peer. This includes
|
||||
|
@ -121,10 +121,9 @@ The <pbc|pin|PIN#> parameter specifies the WPS provisioning
|
|||
method. "pbc" string starts pushbutton method, "pin" string start PIN
|
||||
method using an automatically generated PIN (which will be returned as
|
||||
the command return code), PIN# means that a pre-selected PIN can be
|
||||
used (e.g., 12345670). [label|display|keypad] is used with PIN method
|
||||
to specify which PIN is used (label=PIN from local label,
|
||||
display=dynamically generated random PIN from local display,
|
||||
keypad=PIN entered from peer device label or display). "persistent"
|
||||
used (e.g., 12345670). [display|keypad] is used with PIN method
|
||||
to specify which PIN is used (display=dynamically generated random PIN
|
||||
from local display, keypad=PIN entered from peer display). "persistent"
|
||||
parameter can be used to request a persistent group to be formed.
|
||||
|
||||
"join" indicates that this is a command to join an existing group as a
|
||||
|
|
Loading…
Reference in a new issue