TIP: Click on subject to list as thread! ANSI
echo: cis.os9.6809.coco
to: PaulSeniura 76476,464 (X)
from: PaulSeniura 76476,464
date: 1991-07-31 23:59:39
subject: #11566-#Timer Thoughts

#: 11567 S10/OS9/6809 (CoCo)
    31-Jul-91  23:59:39
Sb: #11566-#Timer Thoughts
Fm: PaulSeniura 76476,464
To: PaulSeniura 76476,464 (X)

..

Well let's say once the timer interrupts, we "know" it's "us" who needs to
respond.  What to do?  Remember we're in system mode at this point, and the
user pgm probably is nowhere mapped-in right now.  In order to call the user
pgm's F$SSWI vector, we must "become" that task by saving then poking D.Proc
with the id of that task.  Then we can issue a matching SWIn 6809 instruction
right then & there.  Right?  OS9's software interrupt routine will cause the
user pgm to get mapped in and *bingo* we're running the code for that task.
Right?  We don't need to mess with map-in calls and DAT-image calls etc. Right?

And the second Timer article update still has further questions which should be
consulted at this time.  And I hope these replies have made it clearer in order
to understand that second update?

-- Thx, Paul Seniura.



There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.