home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.ada
- Path: sparky!uunet!darwin.sura.net!jvnc.net!yale.edu!ira.uka.de!fauern!fauna!mskuhn
- From: mskuhn@immd4.informatik.uni-erlangen.de (Markus Kuhn)
- Subject: Re: Serial interrupt handler in Meridian Ada on PC?
- References: <1992Jul21.110241.15174@verdix.com> <Bruyt1.F0F@immd4.informatik.uni-erlangen.de> <PAT.92Jul27074448@summit.opus>
- Message-ID: <Bs24Is.2Ks@immd4.informatik.uni-erlangen.de>
- Organization: CSD., University of Erlangen, Germany
- Date: Mon, 27 Jul 1992 16:59:16 GMT
- Lines: 30
-
- pat@summit.opus (pat gioannini) writes:
-
- >I am wondering how well these drivers work with Ada tasking.
-
- BTW: You find some FOSSIL drivers (e.g. BNU, X00, ...) in
- portal/pc/modem/fossil/:ftp.uni-erlangen.de.
-
- >If the interrupt handler is written in Ada then receiving a character
- >available interrupt can start rendezvous with higher level task. The
- >higher level task starts immediately if its priority is high enough.
-
- I didn't succed in writing serial line drivers that use an Ada interrupt
- rendevous for each single character for speeds over 1200bits/sec on an
- 12MHz 286 AT. So I prefer a ready to use interrupt driven FIFO device
- driver where I can poll big blocks of characters. A rendevous for each
- single byte is MUCH too much overhead! (Meridian 4.1)
-
- >If the interrupt handler is written in assembly or C or whatever and does
- >not understand Ada tasking you are left with polling the serial driver
- >for a character available.
-
- The perfect solution: The interrupt handler triggers an interrupt after
- e.g. 64 bytes have been received of after a 0.1sec timeout, or ...
-
- Markus
-
- --
- Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
- Internet: mskuhn@immd4.informatik.uni-erlangen.de | X.500 entry available
- ------------------ ISO? Nicht immer. Aber immer ÷fter! -------------------
-