Lines Matching full:you

171    * Try to reconnect in 30 seconds, if you need a modem chatscript you have
248  * netif, optional already existing and setup output netif, necessary if you
356  * You can call this function at anytime.
361  * Then you must wait your status_cb() to be called, it may takes from a few
372  * dead state (i.e. disconnected). You need to call ppp_close() before.
394 using the TCPIP API. This is thread safe in all cases but you should avoid
398 if NO_SYS is 0 and if PPP_INPROC_IRQ_SAFE is 1, you may also use pppos_input()
399 from an RX thread, however pppos_input() is not thread safe by itself. You can
400 do that *BUT* you should NEVER call pppos_connect(), pppos_listen() and
402 at all. Using PPP_INPROC_IRQ_SAFE from an RX thread is discouraged unless you
403 really know what you are doing, your move ;-)
424 There is a thread safe API for all corresponding ppp_* functions, you have to
434 you configure a callback that is called on each PPP internal state change.
435 This is different from the status callback which only warns you about
483 * struct netif was moved outside the PPP structure, you have to provide a netif
486 * PPP session are not started automatically after you created them anymore,
487   you have to call ppp_connect(), this way you can configure the session before
496 * New PPPERR_ error codes added, check you have all of them in your status
505   Functions from ppp.h can be used, but you don't need to include this header
508 * PPP_INPROC_OWNTHREAD was broken by design and was removed, you have to create
513   because you might have been fooled by that
515 * If you used tcpip_callback_with_block() on ppp_ functions you may wish to use
523   using the dns_setserver() function so you don't need to do that in the PPP