Re: PPP object questions
Jesse Marroquin <jesse.marroquin-6tN4nzCoH/[email protected]>
| Newsgroups | gmane.comp.hardware.microcontrollers.tini |
|---|---|
| Message-ID | <[email protected]> |
Shawn, > > Hello. I would like to understand how to more effectively use the PPP > object. I am confused about the points brought up in these emails: > > http://lists.dalsemi.com/maillists/tini/2003-July/028179.html The ACCM is a bit map used to escape the 32 ASCII control characters in the range 0x00 to 0x1f. The ACCM is a 32 bit field where bit 0 represents the character 0x00. A bit value of 1 enables and a value of 0 disables escaping of a character. The default is to escape all 32 characters, an ACCM of 0xffffffff. For a link that can handle arbitrary data a value of 0x00000000 can be used. For a link using XON/XOFF flow control a value of 0x000a0000 will escape characters 0x11(XON) and 0x13(XOFF). If your link is using XON/XOFF flow control use setLocalACCM and setRemoteACCM to set an ACCM of 0x000a0000. The setting of an ACCM value is not dependent on server/client operation. > http://lists.dalsemi.com/maillists/tini/2003-July/028177.html freePort() forces the PPP native library to release the serial port object. This allows the serial port object to be used by the application again. The application should not read or write to the serial port between the up() and and freePort() methods. The next two methods need to be called if you are going to release the handle of the current PPP object and create a new PPP object. This is the case when an application creates a new PPP object for each new connection. If the application reuses a single PPP object for the lifetime of the application these method do not need to be used. These methods release native resources that would normally be released in a finalize method. In the case of reusing the PPP object, the native resources will be released when the application exits or is killed. The use of a single PPP object is recommended. finish() terminates a sleeping read thread within the PPP native object, kills an internal timer thread and kills an internal queue thread. freeNativeInterface() releases native resources used by the PPP object. This should be the last of the methods called. Because of the bank 7 size limit the PPPCommand was removed from the optional Slush commands. > > Thanks, > -Shawn > > _______________________________________________ > TINI mailing list > TINI-6tN4nzCoH/[email protected] > To UNSUBSCRIBE, edit your profile, or see list archives: > http://lists.dalsemi.com/mailman/listinfo/tini Jesse _______________________________________________ TINI mailing list TINI-6tN4nzCoH/[email protected] To UNSUBSCRIBE, edit your profile, or see list archives: http://lists.dalsemi.com/mailman/listinfo/tini