Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!elroy!brad From: brad@gobi.jpl.nasa.gov (Brad Pickering) Newsgroups: comp.os.minix Subject: Re: MacMINIX, interrupts, and ACK register saving conventions Message-ID: Date: 29 May 91 14:37:56 GMT References: <54891@nigel.ee.udel.edu> Sender: news@elroy.jpl.nasa.gov (Usenet) Organization: Jet Propulsion Laboratory, Pasadena, CA Lines: 28 In-Reply-To: KENC@vaxb.acs.unt.edu's message of 29 May 91 04:39:02 GMT Nntp-Posting-Host: ais-gw.jpl.nasa.gov > something about how certain interrupts don't cause a context switch might > be related to the uucp problems I don't know but I really doubt it. The context switch to finish handling the interrupt should happen fairly quickly anyways. > questions about MacMINIX running on bare hardware. Actually, what I had in mind is having MINIX take control a system startup time before the system file and inits have been loaded (Sorry). I think this may only work on systems with the 256k roms because of the resources available in these roms. The only parts of the MacOS that I really want to get away from are the file system and the window manager. I would like to see X Windows running on MacMINIX also but I think it would be too slow. > suggestions about handling time critical interrupts in MINIX but letting > apple handle the rest. sounds ok to me. I think I'd be happy with apple handling all interrupts but eventually I'd like to replace these with handlers written specifically for MacMINIX. These routines would be pretty machine specific though so I doubt any such modification would ever but put in the mainline MINIX. -- -- Brad Pickering brad@gobi.jpl.nasa.gov --