Re: [MiNT] FreeMiNT 1.15.10b

[Martin-Éric Racine <q-funk@pp.fishpool.fi>]

Hello Frank!

I am having problems with these drivers, on kernel 1.15.10b:

On any port, 'stty < /dev/ttyS[0-4]' manages to read the current
baudrates to plausible values, but 'stty 9600 > /dev/ttyS[0-4]'
produces the error "stty: standard input: unable to perform all
requested operations" (9600 is just an example; any valid speed
produces the same error).

MFP 0.12

Using Minicom set for the portname (/dev/modem1), I can receive
characters, but outgoing characters don't ever reach the other
side. If Minicom is set to use the TTY name (/dev/ttyS0) instead,
MiNT freezes as soon as I try to send anything. Using Connect,
outgoing characters reach the other side, and there is a delay of
about 10 seconds before the response (in this case, a login
prompt) is received; it works, but it is sluggish.

SCC 0.25

Using Minicom, the same results happen as with MFP.  Using
Connect, the baudrate for both SCC ports is 499999 and cannot be
changed. In any case, characters can neither be sent or received
using Connect on the SCC ports.


On another aspect, when the MFP driver is installed, Serial1
disappears from the /dev folder; isn't that driver supposed to
support TT-MFP already?  Also, unless the SCC driver is loaded,
/dev/lan never appears at all; shouldn't the kernel itself find
both serial2 and lan?


MiNT-Net

The sockets are now rather unstable, using the drivers found in
the current beta. Previously, pinging the TT from my Linux box
returned a rock-solid 2.4ms but using current binaries, response
is anywhere between 2.5ms and 8.3ms, over a connection on the
Riebl. Connection over PLIP is even less stable, with most
replies varying wildly between 8.4ms and 12.4ms, even though PLIP
previously proved faster and more stable than the Riebl.


Obviously, the above are only symptoms. Besides, since Connect
only knows how to use RSVF devices, it was not possible to test
using TTY devices.

Hopefully, the above can at least help you pinpoint what might be
the source of the bugs.  If you need any additional tests or log
files, tell me which ones.

-- 
Martin-Éric Racine, IT Consultant * http://funkyware.atari.org/  
* May the Funk be with Q! * Author of the Atari TT030 Homepage.