This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

forwarded message from Sandeep Rikhi




Respected Sir
Thanks for your kind help. Could you please guide me for the source code.
 Also, ecos is already supporting 
MPC850 which is being used in the project,
It would be a matter of great help if you could put some light on the
names of the files to be studied for interrupt handling.
Thanks & regards !

*********************************************************
        Sandeep Rikhi
        GET-GCPE Group.
        Switching Division B1,
        Centre for Development of Telematics,
        Millers Road, Bangalore.
        India.
        Ph: (080) 2263399 ext:205/217,2250009,2282119   
*********************************************************

On 7 Sep 2000, Jesper Skov wrote:

> >>>>> "Sandeep" == Sandeep Rikhi <sr@cdotb.ernet.in> writes:
> 
> Sandeep> Suppose we configure eCos to allow DSRs and handle
> Sandeep> them in a list. Also, Suppose some thread is executing and
> Sandeep> there is an interrupt occurance.
> 
> [snip]
> 
> This is all handled by the "standard" eCos interrupt code. You must
> write your HAL to match the interrupt handling semantics of one of the
> existing HALs.
> 
> Here's a little detail about the interrupt processing:
> 
> http://sources.redhat.com/ecos/docs-latest/porting/hal-interrupts.html
> 
> To get all the details you'd have to read the code.
> 
> Suffice to say that your concerns are all addressed by the "standard"
> eCos interrupt handling semantics.
> 
> Jesper
> 





Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]