Path: utzoo!attcan!uunet!mcsun!unido!mpirbn!p554mve
From: p554mve@mpirbn.mpifr-bonn.mpg.de (Michael van Elst)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Micro Timing Critical sections HELP!
Message-ID: <1244@mpirbn.mpifr-bonn.mpg.de>
Date: 23 Sep 90 23:24:26 GMT
References: <4934@uqcspe.cs.uq.oz.au> <1687@shodha.enet.dec.com> <4969@uqcspe.cs.uq.oz.au>
Reply-To: p554mve@mpirbn.UUCP (Michael van Elst)
Organization: Max-Planck-Institut fuer Radioastronomie, Bonn
Lines: 22

In article <4969@uqcspe.cs.uq.oz.au> thyssen@batserver.cs.uq.oz.au writes:
>void
>Open_Timer()
>{  /* save info on current timer setup */
>  ciab_resource = OpenResource(CIABNAME);
>  CIACRAsave = ciab.ciacra;
>  CIACRBsave = ciab.ciacrb;
>  ciab.ciaicr = 0xff &~CIAICRF_TA &~CIAICRF_TB; /* disable timer interupts */
>}

As far as I know you have to allocate the interrupt associated with the
timer to use the timer registers. Since opening the cia resource will
not grant exclusive access to the cia your code might run into problems
when more than one application tries to use the timer.
The interrupt can be allocated with a call to AddICRVector() (sp ?)..

Regards,
-- 
Michael van Elst
UUCP:     universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
                                "A potential Snark may lurk in every tree."