This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: Interrupt arbitration on MPC555
- To: <bob dot koninckx at mech dot kuleuven dot ac dot be>
- Subject: Re: [ECOS] Interrupt arbitration on MPC555
- From: Jesper Skov <jskov at redhat dot com>
- Date: 25 Feb 2000 10:31:23 +0100
- Cc: "ecos discussion forum" <ecos-discuss at sourceware dot cygnus dot com>
- References: <000001bf7f6a$afb1f6c0$56183a86@pc086-2.mech.kuleuven.ac.be>
>>>>> "Bob" == Bob Koninckx <bob.koninckx@mech.kuleuven.ac.be> writes:
Bob> I suppose not every application is interested in using the same
Bob> priorities, some might like to assign a high priority to
Bob> CAN-interruipts and do not even use the TPU, for another
Bob> application it might be necessary to assign a higher priority
Bob> (and hence different arbitration) to the TPU than the
Bob> CAN-controller. These are strong arguments to assign these
Bob> priorities and setup the arbitration somewhere during startup of
Bob> the APPLICATION.
Bob> On the other hand, it also makes sense to use device drivers for
Bob> can, serial ports etc,... These device drivers have to create
Bob> interrupts and hence have to know the priority of these
Bob> interrupts. So it seems you have to set-up priorities and
Bob> arbitration somewhere within ECOS. And then you lose all
Bob> flexibility ....
I think this belongs in the eCos configuration. I don't see how that
loses you any flexibility: normally you would configure eCos for your
application needs anyway.
Jesper