[Coco] serial terminal?
Kevin Diggs
kevdig at hypersurf.com
Mon Sep 6 18:30:40 EDT 2004
Hi,
A while back there was someone who sounded like they knew their stuff,
serially speaking. I don't. I am trying to get linux to work as a
terminal on my tre.
The setup is as follows. Linux 2.4.26 on a 486dx2-40. Terminal program
is minicom. Serial parameters are 19200 8N1, hardware handshake. Serial
chip is 16550A.
On the tre the setup is FHL eliminator (2 serial ports using 65c52
serial chip). Driver is DACIA. Using their modded xmode:
OS9:xmode_elim /t3
nam=T3 mgr=SCF ddr=DACIA hpn=07 hpa=FF60 upc=00 bso=01
dlo=00 eko=01 alf=01 nul=00 pau=00 pag=18 bsp=08 del=18
eor=0D eof=1B rpr=09 dup=19 psc=17 int=03 qut=05 bse=08
ovf=07 par=0E bau=07 xon=00 xof=00 col=50 row=18 xtp=41
wnd=41 val= sty= cpx= cpy= fgc= bgc= bdc=
The par byte (offset $26 in descriptor (same as type?) is:
%0xxxxxxx 1 stop bit
%1xxxxxxx 2 stop bits
%x00xxxxx 8 bits
%x01xxxxx 7 bits
%x10xxxxx 6 bits
%x11xxxxx 5 bits
%xxxyxxxx y sets modem kill (0->no action, 1 returns
e$hangup)
%xxxxyxxx receive software flow control (1 -> enabled)
%xxxxxyxx transmit software flow control (1 -> enabled)
%xxxxxxyx CTS/RTS hardware flow control (1->enabled)
%xxxxxxxy DSR/DTR hardware flow control (1->enabled)
The xtyp byte (offset $2e) is:
%xyxxxxxx 0 sets DTR when opened and disables when closed
1 enables DTR on device (/t3) initialization
%xxxxyyyy controls receive buffer size in pages (0 use
default)
The problem is flow control. It is not particularly easy to get a sub 2
MHz 8-bit machine to overrun a 40 MHz 32 machine with a buffered serial
chip. But I am seeing occasional listing glitches. I also tried a par of
2 and it is much worse.
Also, noone responded to my basic09 on a terminal question. I fixed the
problem by switching the terminal emulation to ANSI.
kevin
More information about the Coco
mailing list