Article View: comp.sys.amiga.tech
Article #7778Re: CIA Timers and Interrupt priority problems
From: Jim Burwell
Date: Thu, 03 Jan 1991 22:01
Date: Thu, 03 Jan 1991 22:01
26 lines
1523 bytes
1523 bytes
forgeas@swinjm.UUCP (Jean-Michel Forgeas) writes: >In article <650@faatcrl.UUCP>, Jim Burwell writes: >> [...]This works fine, except that the CIA B timer hardware Interrupt priorities >> are so high that the music player now interrupts EVERYTHING.[...] >Just a suggestion: since Exec is preemptive, your interrupt routine could >just Signal() a task which has a priority of 1 or 2. Then the task really >becomes active each time it is signaled. Hmm. That MIGHT work. But I know there would be conditions which could easily arise which would delay my program from getting it's time slice, and screw up the music. And music with screwed up timing is not worth listening to. It would probably be so annoying that people would just turn it off :-). I'd rather avoid the entire issue of Exec task schedualling by keeping things one step lower-level than Exec. C'ya, Jim -- UUCP: ...!rutgers!faatcrl!jimb Internet: jimb@faatcrl.UUCP Under brooding skys and watchful eyes On convulsive seas of false urgency We walk empty corridors in vain - "No Exit", Fate's Warning
Technical Details
Message-ID:
<663@faatcrl.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!faatcrl!jimbReferences:
<650@faatcrl.UUCP> <18759fb0.ARN0afd@swinjm.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!faatcrl!jimb From: jimb@faatcrl.UUCP (Jim Burwell) Newsgroups: comp.sys.amiga.tech Subject: Re: CIA Timers and Interrupt priority problems Message-ID: <663@faatcrl.UUCP> Date: 3 Jan 91 22:01:36 GMT References: <650@faatcrl.UUCP> <18759fb0.ARN0afd@swinjm.UUCP> Organization: FAA Technical Center, Atlantic City NJ Lines: 26