Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!mips!troi!peter
From: peter@dbaccess.com (Peter A. Castro)
Newsgroups: comp.sys.amiga.tech
Subject: Re: 020 & 030 CACR
Message-ID: <721@troi.dbaccess.com>
Date: 4 Oct 90 18:20:36 GMT
References: <4788@crash.cts.com>
Organization: DB/Access Inc., Santa Clara, CA
Lines: 31

in article <4788@crash.cts.com>, lkoop@pnet01.cts.com (Lamonte Koop) says:
+ 
+ Now that I finally have some working code for reading/setting the
+ 68020..030...???  CACR, I have ONE question.  I realize it would be a good
+ idea to disable task switching and such when SETTING the CACR, but how 'bout
+ reading it?  I know you CAN do either one with task switching uninhibited (or
+ interrupts for that matter), but just how necessary is it?  (I don't like to
+ inhibit the system unneccessarily).  Any thoughts?

   Um, how often are you planning on reading it?  Really, you should treat it
   as if it were an EXEC system list.  This means Disabling and Enabling.
   After all, if you are traversing this list and it should be changed while
   you were swapped out, well... you'll get to visit the Guru almost certainly.
+  
+ --LaMonte
+ 
+ "The MOST original .sig yet: A non-existant one!"
+ 
+ UUCP: {hplabs!hp-sdd ucsd nosc}!crash!pnet01!lkoop
+ ARPA: crash!pnet01!lkoop@nosc.mil
+ INET: lkoop@pnet01.cts.com

Peter A. Castro                   INTERNET: peter@dbaccess.com        // //|
c/o DB/Access Inc.                UUCP: {uunet,mips}!troi!peter      // //||
2900 Gordon Avenue, Suite 101     FAX: (408) 735-0328            \\ // //-||-
Santa Clara, CA 95051-0718        TEL: (408) 735-7545             \// //  ||
-- 
Peter A. Castro                   INTERNET: peter@dbaccess.com        // //|
c/o DB/Access Inc.                UUCP: {uunet,mips}!troi!peter      // //||
2900 Gordon Avenue, Suite 101     FAX: (408) 735-0328            \\ // //-||-
Santa Clara, CA 95051-0718        TEL: (408) 735-7545             \// //  ||