Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu
From: cloos@acsu.buffalo.edu (James H. Cloos)
Newsgroups: comp.sys.handhelds
Subject: Re: M/L Interrupts/Concurrent Routines
Keywords: ml, interrupts, concurrent routines
Message-ID: <72853@eerie.acsu.Buffalo.EDU>
Date: 24 Apr 91 20:28:40 GMT
References: <1991Apr23.115645.9250@corpane.uucp> <72610@eerie.acsu.Buffalo.EDU> <15233@life.ai.mit.edu>
Sender: news@acsu.Buffalo.EDU
Organization: State University of New York @ Buffalo
Lines: 22
Nntp-Posting-Host: lictor.acsu.buffalo.edu

In article <15233@life.ai.mit.edu> bson@rice-chex.ai.mit.edu (Jan Brittenson) writes:
|In a posting of [23 Apr 91 20:03:15 GMT]
|   cloos@acsu.buffalo.edu (James H. Cloos) writes:
| > There must be a ML-level routine that can be used to call an xlib
|
|Calling an XLIB is actually quite simple:
|
|	move	pc, a
|	add.a	xlib_ref-., a
|	jump	@a
|xlib_ref:
|	data.a	#2e92
|	data.3	700, 1
|
|Will transfer control to XLIB 700 1.
|

Duh.	[SIGH]

So, did I epitomise missing the obvious?  

-JimC