Model T TCP Architecture: Difference between revisions

From Bitchin100 DocGarden
Jump to navigationJump to search
(New page: == Overview == Presumably, a TCP stack on the Model 100 cannot be done. All the more reason to do it, right? This article is a place to hash out goals, anti-goals, and a design == Goals...)
 
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Overview ==
== Overview ==


Presumably, a TCP stack on the Model 100 cannot be done. All the more reason to do it, right?
Presumably, a TCP stack on the Model 100 cannot be done. The 8085 is just too underpowered. All the more reason to do it, right?


This article is a place to hash out goals, anti-goals, and a design
This article is a place to hash out goals, anti-goals, and a design


== Goals ==
== Goals ==
* Code runs from Option ROM
* Implements IP, TCP, UDP, PPP
* Header compression
* 100% 8085 assembly language
* May provide option to assemble for Z80/8080 as well
* Implements hardware flow control signals
* 19200bps


== Anti-Goals ==
== Anti-Goals ==


== Design ==
== Design ==
=== TCP ===
=== UDP ===
== References ==
http://www.sics.se/~adam/uip/index.php/Main_Page

Latest revision as of 20:43, 11 August 2009

Overview

Presumably, a TCP stack on the Model 100 cannot be done. The 8085 is just too underpowered. All the more reason to do it, right?

This article is a place to hash out goals, anti-goals, and a design

Goals

  • Code runs from Option ROM
  • Implements IP, TCP, UDP, PPP
  • Header compression
  • 100% 8085 assembly language
  • May provide option to assemble for Z80/8080 as well
  • Implements hardware flow control signals
  • 19200bps

Anti-Goals

Design

TCP

UDP

References

http://www.sics.se/~adam/uip/index.php/Main_Page