> While this is true, a truly event based processor would have 2 cores: 1
> event core and one processing core.  The processing core would remain idle
> until the event core called it, and this is where it differs from polling,
> the event core would be able to interrupt with an event of higher priority
> if neccessary.  (And I think processors should have built in context
saving
> too....) Real-time processing... Yay... interrupting interrupts.  A of
> course that's only practical in an app where the processor has a stack
> that's a bit deeper than 8 levels.

What you are describing sounds more like a multi-priority interrupt system
than an event polling system.  Note that the 18 family PICs do have two
interrupt priority levels, so a high priority interrupt can be serviced in
the middle of servicing a low priority interrupt.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body