diff options
Diffstat (limited to 'Documentation/networking/phonet.txt')
-rw-r--r-- | Documentation/networking/phonet.txt | 32 |
1 files changed, 14 insertions, 18 deletions
diff --git a/Documentation/networking/phonet.txt b/Documentation/networking/phonet.txt index 2d9bc2b711fc..24ad2adba6e5 100644 --- a/Documentation/networking/phonet.txt +++ b/Documentation/networking/phonet.txt | |||
@@ -199,33 +199,29 @@ between itself and a remote pipe-end point (e.g. modem). | |||
199 | 199 | ||
200 | The implementation adds socket options at SOL_PNPIPE level: | 200 | The implementation adds socket options at SOL_PNPIPE level: |
201 | 201 | ||
202 | PNPIPE_CREATE | 202 | PNPIPE_PIPE_HANDLE |
203 | It accepts an integer argument where-in | 203 | It accepts an integer argument for setting value of pipe handle. |
204 | lower order 16 bits: pn_dev and pn_port pair for remote pep. | ||
205 | higher order 16 bits: 8 bit pipe-handle | ||
206 | |||
207 | It sends a PNS_PEP_CONNECT_REQ on sequenced socket itself. On getting | ||
208 | PNS_PEP_CONNECT_RESP, it sends PNS_PEP_CONNECT_REQ to remote pep. On | ||
209 | getting response from remote pep, it selects the best possible Flow | ||
210 | control mechanism supported by remote-pep (modem) and then it sends | ||
211 | PNS_PEP_CREATED_IND to the sequenced socket and to the remote pep. | ||
212 | |||
213 | It then updates the pipe state associated with the sequenced socket to | ||
214 | be PIPE_DISABLED. | ||
215 | 204 | ||
216 | PNPIPE_ENABLE accepts one integer value (int). If set to zero, the pipe | 205 | PNPIPE_ENABLE accepts one integer value (int). If set to zero, the pipe |
217 | is disabled. If the value is non-zero, the pipe is enabled. If the pipe | 206 | is disabled. If the value is non-zero, the pipe is enabled. If the pipe |
218 | is not (yet) connected, ENOTCONN is error is returned. | 207 | is not (yet) connected, ENOTCONN is error is returned. |
219 | 208 | ||
220 | PNPIPE_DESTROY | 209 | The implementation also adds socket 'connect'. On calling the 'connect', pipe |
221 | This will send out PNS_PEP_DISCONNECT_REQ on the sequenced socket and | 210 | will be created between the source socket and the destination, and the pipe |
222 | the remote pep. | 211 | state will be set to PIPE_DISABLED. |
223 | It will also update the pipe state associated with the sequenced socket | ||
224 | to PIPE_IDLE | ||
225 | 212 | ||
226 | After a pipe has been created and enabled successfully, the Pipe data can be | 213 | After a pipe has been created and enabled successfully, the Pipe data can be |
227 | exchanged between the host-pep and remote-pep (modem). | 214 | exchanged between the host-pep and remote-pep (modem). |
228 | 215 | ||
216 | User-space would typically follow below sequence with Pipe controller:- | ||
217 | -socket | ||
218 | -bind | ||
219 | -setsockopt for PNPIPE_PIPE_HANDLE | ||
220 | -connect | ||
221 | -setsockopt for PNPIPE_ENCAP_IP | ||
222 | -setsockopt for PNPIPE_ENABLE | ||
223 | |||
224 | |||
229 | Authors | 225 | Authors |
230 | ------- | 226 | ------- |
231 | 227 | ||