MTerm: Difference between revisions

From Bitchin100 DocGarden
Jump to navigationJump to search
Line 7: Line 7:
* 38400bps support
* 38400bps support
* Hardware flow control
* Hardware flow control
* Avoids flowing off the sender as much as possible, filling up free RAM with data up to limit of machine
* The  core should be open, educational, and reusable in other applications
* The  core should be open, educational, and reusable in other applications
* Permit queueing of multiple receive or transmit operations
* "Zero copy" - receive and transmit directly to/from the clients memory.
* Configurable RX level high/low watermarks for disable/re-enable of RTS
* Adjustable number of RX buffers and buffer size
* Priority of operations are:
* Priority of operations are:
** The current RX or TX operation as an atomic unit
** The current RX or TX operation as an atomic unit
Line 15: Line 18:
** No-scroll display updates
** No-scroll display updates
** Scrolling updates
** Scrolling updates
* Permit queueing of multiple receive or transmit operations
* "Zero copy" - receive and transmit directly to/from the clients memory.
* Configurable RX level high/low watermarks for disable/re-enable of RTS

Revision as of 23:36, 10 February 2009

Overview

This is a design document for a Model 100 terminal program.

Features

  • 38400bps support
  • Hardware flow control
  • The core should be open, educational, and reusable in other applications
  • Permit queueing of multiple receive or transmit operations
  • "Zero copy" - receive and transmit directly to/from the clients memory.
  • Configurable RX level high/low watermarks for disable/re-enable of RTS
  • Adjustable number of RX buffers and buffer size
  • Priority of operations are:
    • The current RX or TX operation as an atomic unit
    • Keyboard polling
    • Bottom line display
    • No-scroll display updates
    • Scrolling updates
Retrieved from "https://bitchin100.com/wiki/index.php?title=MTerm&oldid=1006"