In article <BsGqDo.58s@ux1.cso.uiuc.edu> Upholder@uiuc.edu (THE Upholder of Truth) writes:
quoted text
>However, netiher getty or kermit (or xcomm or minicom as far as I can tell)
>support rates over 38400.  My modem will do 57.6K (with compression) and
>I hope to connect at full speed once I get back to campus (the local dialup
>is only 38400 anyway so it doesn't matter yet).
>
>Is this a kernel limitation?  or is it getty/kermit/etc?

  If you take a look at /usr/include/termios.h, you can see where the
problem is. You can find the Holy Bit Rates listed there. Sometimes
that kind of standards just make me puke.

  I'm currently using a hack in the bit clock division table in serial.c
to make 200 bps actually be 57600 bps, and it's working well on my
486/33 with 16550A. Even stressing the system with cpu load and some heavy
disk reading (atid) seem not to drop characters. Scsi i/o (ST-01) still
makes it loose data, but I recall scsi didn't yet use the new irq code,
and it'll be fixed in the future. (Is this correct?)

  But the main question: Is there a good, clean way of getting 57600
bps? I would like to hear your comments on how one should do it.
-- 
Jaakko Hyv{tti                  Jaakko.Hyvatti@Helsinki.FI
Karstulantie 8 B 30             hyvatti@plootu.Helsinki.FI
00550  Helsinki, Finland        +358-0-701 7810, -692 7466 (work)