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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,641105de50ec2788
X-Google-Attributes: gid103376,public
From: Geert Bosch <geert@gonzo.sun3.iaf.nl>
Subject: Re: 2nd help about handling HW interrupt and apologizes.
Date: 1998/04/10
Message-ID: <6glg1a$8og$1@gonzo.sun3.iaf.nl>#1/1
X-Deja-AN: 342857420
Distribution: world
References: <6gft3m$rib$1@nnrp1.dejanews.com> <352BB2AE.1DC7325E@cl.cam.ac.uk>
 <m37m4y6iy2.fsf@fred.muc.de>
Organization: La Calandre Infortunee
Newsgroups: comp.lang.ada
Date: 1998-04-10T00:00:00+00:00
List-Id: <comp.lang.ada>


Andi Kleen <ak@muc.de> wrote:
   To just get the job done it is probably easier to just write a small
   stub kernel driver in C that communicates with the Ada program running
   in userspace over a device or a netlink socket.

Of course you'll have exactly the same problems when you write these
drivers in C as when you write them in Ada! As you mentioned it is
not safe to use the C run-time library as well. So, yes, you should
write your code using a very limited subset of the language and you'll
have to know what kind of code your compiler generates.

For example when using GNAT it is possible to get almost identical
code as when using the GNU C compiler if you just limit yourself to
what would be possible in C. It is easy to do this experiment yourself
and look at the generated code; this is something you should do in
any case when writing code like system kernel modules. 

Regards,
   Geert