From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: *** X-Spam-Status: No, score=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID, RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3cfb384718eb4f7a X-Google-Attributes: gid103376,public From: "Jerry van Dijk" Subject: Re: question re Ada equivalent of C function Date: 1998/02/22 Message-ID: <01bd3f7d$43882660$4a2c5c8b@aptiva>#1/1 X-Deja-AN: 327481249 References: <34EEFF9C.1D01FA5D@stellar1.com> <01bd3f1d$44728800$582c5c8b@aptiva> <34EF6CC6.28EF2D4A@stellar1.com> Organization: Ordina Finance Newsgroups: comp.lang.ada Date: 1998-02-22T00:00:00+00:00 List-Id: Talking about accessing I/O addresses, David Fisher schreef in artikel <34EF6CC6.28EF2D4A@stellar1.com>... > The hardware will be a Pentium; the OS will be Linux, the compiler > (presumably) GNAT. Thing is, development is being done with Aonix 7.1 on NT4. As both Linux and NT are real operating systems, neither will allow you to directly access an IO port from a user program. By messing around with rights and such you might be able to pull it off using inline-assembly tricks, but at this low level both Linux vs NT and GNAT vs OA are incompatible. The best solution would be if you would have a device driver for the I/O you are trying to access, one for NT and one for Linux. Unless, of course, you are not trying to access any particular device connected to these I/O ports, but need to access I/O ports related to the machine's operation itself. Then there might be OS facilities to do this. As usual when you work so close to the machine, it all depends... -- -- Jerry van Dijk | Leiden, Holland -- Team Ada | email: jdijk@acm.org