Xref: utzoo comp.arch:22824 comp.sys.intel:1713
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker.mit.edu!bloom-beacon!eru!kth.se!sunic!mcsun!hp4nl!charon!dik
From: dik@cwi.nl (Dik T. Winter)
Newsgroups: comp.arch,comp.sys.intel
Subject: Re: Interrupt handler for the i860
Message-ID: <3564@charon.cwi.nl>
Date: 21 May 91 08:17:27 GMT
References: <4690@alliant.Alliant.COM> <1530@fang.dsto.oz>
Sender: news@cwi.nl
Followup-To: comp.arch
Organization: CWI, Amsterdam
Lines: 13

In article <1530@fang.dsto.oz> jdy@itd.dsto.oz writes:
 > There have been quite a few posts on the complexity of the state-saving and
 > restoring code that needs to be put in the interrupt handler. Since this 
 > particular code is just about essential for i860 sysprogs, and is almost
 > hardware independant, is there any reason why it should not be put in the
   ^^^^^^^^^^^^^^^^^^^^ Eh?
 > public domain? Are people so cheesed off after having written such code 
 > that they cannot bear the thought of just giving it away for free? 
 > 
Look in the Programmer's Reference Manual, pages 7-10 to 7-12.
--
dik t. winter, cwi, amsterdam, nederland
dik@cwi.nl