Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history
yaml
---
r: 215258
b: refs/heads/master
c: 1a63c35
h: refs/heads/master
v: v3
  • Loading branch information
John W. Linville committed Oct 15, 2010
1 parent a6a8aff commit 585ff87
Show file tree
Hide file tree
Showing 35 changed files with 707 additions and 1,375 deletions.
2 changes: 1 addition & 1 deletion [refs]
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: b3c0598952e02f1f1f6d003574549d940ecbf31a
refs/heads/master: 1a63c353c856c9f6d44a533afb6ad6dbbcdea683
32 changes: 14 additions & 18 deletions trunk/Documentation/networking/phonet.txt
Original file line number Diff line number Diff line change
Expand Up @@ -199,33 +199,29 @@ between itself and a remote pipe-end point (e.g. modem).

The implementation adds socket options at SOL_PNPIPE level:

PNPIPE_CREATE
It accepts an integer argument where-in
lower order 16 bits: pn_dev and pn_port pair for remote pep.
higher order 16 bits: 8 bit pipe-handle

It sends a PNS_PEP_CONNECT_REQ on sequenced socket itself. On getting
PNS_PEP_CONNECT_RESP, it sends PNS_PEP_CONNECT_REQ to remote pep. On
getting response from remote pep, it selects the best possible Flow
control mechanism supported by remote-pep (modem) and then it sends
PNS_PEP_CREATED_IND to the sequenced socket and to the remote pep.

It then updates the pipe state associated with the sequenced socket to
be PIPE_DISABLED.
PNPIPE_PIPE_HANDLE
It accepts an integer argument for setting value of pipe handle.

PNPIPE_ENABLE accepts one integer value (int). If set to zero, the pipe
is disabled. If the value is non-zero, the pipe is enabled. If the pipe
is not (yet) connected, ENOTCONN is error is returned.

PNPIPE_DESTROY
This will send out PNS_PEP_DISCONNECT_REQ on the sequenced socket and
the remote pep.
It will also update the pipe state associated with the sequenced socket
to PIPE_IDLE
The implementation also adds socket 'connect'. On calling the 'connect', pipe
will be created between the source socket and the destination, and the pipe
state will be set to PIPE_DISABLED.

After a pipe has been created and enabled successfully, the Pipe data can be
exchanged between the host-pep and remote-pep (modem).

User-space would typically follow below sequence with Pipe controller:-
-socket
-bind
-setsockopt for PNPIPE_PIPE_HANDLE
-connect
-setsockopt for PNPIPE_ENCAP_IP
-setsockopt for PNPIPE_ENABLE


Authors
-------

Expand Down
Loading

0 comments on commit 585ff87

Please sign in to comment.