v2: fixed an issue around wps pin handling

This patch-set add the Peer's Agent API documentation and implementation.
However, this only works in the context when ConnMan initiates the connection
and not the other way round (which requires quite a bit of work to get it)

Tomasz Bursztyka (16):
  doc: Add RequestPeerInput method to agent API
  agent: Refactor the error reporting method to be more generic
  agent: Add a specific function to call ReportPeerError agent method
  peer: Provide a utility function to get peer's path in the core
  agent: Provide a function for the Peer RequestPeerAuthorization call
  peer: Modify connect driver's signature to handle WPS properly
  peer: Manage peer connection properly through an Agent report
  peer: Call Agent RequestPeerAuthorization on WPS needs
  gsupplicant: WPS PIN and Peer's path parameters are copied value
  gsupplicant: Add an helper to find a peer via its identifier
  gsupplicant: Add an helper to get the supplicant peer's object path
  wifi: Handle properly WPS parameters while connecting a peer
  wifi: Find and use peer's path do disconnect
  gsupplicant: Do not use and remove identifier parameter for peer
  client: Add Agent ReportPeerError method support
  client: Add support for RequestPeerAuthorization on WPS

 client/agent.c            | 144 +++++++++++++++++++++++++++++--------
 doc/agent-api.txt         |  49 +++++++++++++
 gsupplicant/gsupplicant.h |   8 ++-
 gsupplicant/supplicant.c  |  61 +++++++++-------
 include/agent.h           |   4 ++
 include/peer.h            |  10 ++-
 plugins/wifi.c            |  48 +++++++++++--
 src/agent-connman.c       | 177 +++++++++++++++++++++++++++++++++++++++++-----
 src/agent.c               |  17 +++--
 src/connman.h             |  17 +++++
 src/peer.c                | 141 ++++++++++++++++++++++++++++++++----
 11 files changed, 578 insertions(+), 98 deletions(-)

-- 
1.8.5.5

_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman

Reply via email to