home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!Germany.EU.net!uniol!olis!oytix.north.de!jelal!nox
- From: nox@jelal.north.de (Juergen Lock)
- Newsgroups: comp.sys.atari.st.tech
- Subject: Re: Interrupt interference
- Message-ID: <2286.08.92@jelal.north.de>
- Date: 19 Aug 92 13:36:16 GMT
- Article-I.D.: jelal.2286.08.92
- References: <sourada.714027685@vincent1.iastate.edu>
- Organization: home
- Lines: 33
-
- In <sourada.714027685@vincent1.iastate.edu> sourada@iastate.edu (Steven D Ourada) writes:
-
- >I'm writing a routine to hang off the 50Hz interrupt. This routine often
- >takes as much as 2 ms (long, yes, but unavoidable). The problem is, this
- >seems to interfere pretty badly with timing-intensive things like serial
- >and disk access. ...
-
- yes no wonder, the 50 Hz interrupt is level 6 (MFP)... if you run
- there for too long you sooner or later get receiver overruns on serial
- ports and other nasty things. (even atari themselves didn't get that
- right: try reading a midi dump whild moving the mouse... :-( :-( btw,
- does anyone know if `multitos' has that fixed?)
-
- >Finally, the obvious question: What can I do to ensure that my routine
- >gets the time it needs without bringing down the whole system? Is there
- >a uniform way to see if some time-critical operations are going on? Is
- >there a way to allow these to go on without my routine interfering too
- >badly?
-
- well do you really _need_ the high priority? i mean would something
- seriously break if the routine wouldn't be executed exactly every 20ms?
- if not the solution is simple: use MiNT and make the thing a daemon...
- (timing with usleep()/select() and maybe clock().)
-
- otherwise you probably need a real-time OS... :-(
-
- > Later,
- > Steven Ourada
- anyway, have fun
- Juergen
- --
- J"urgen Lock / nox@jelal.north.de / UUCP: ..!uunet!unido!uniol!jelal!nox
- ...ohne Gewehr
-