This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Ecos interrupt handling
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: "A.K.V.SAI JAYRAM" <sai at cdotb dot ernet dot in>
- Cc: ecos-discuss at sources dot redhat dot com, Tim Hölters <Hoeltetm at iis dot fhg dot de>
- Date: 26 Nov 2002 18:37:19 +0000
- Subject: Re: [ECOS] Ecos interrupt handling
- References: <Pine.OSF.4.21.0211261403090.23363-100000@ws9.cdotb.ernet.in>
"A.K.V.SAI JAYRAM" <sai@cdotb.ernet.in> writes:
> Hi Tim...
> Thanx for the info.
> I have checked the documents for interrupts. But nothing is given in
> detail.
I'm not sure how much detail you want, but there is some in the
documentation in at least these places:
http://www.vsr.si/ecos/ecos/cvsdoc/kernel-interrupts.html
http://www.vsr.si/ecos/ecos/cvsdoc/hal-interrupt-handling.html
http://www.vsr.si/ecos/ecos/cvsdoc/hal-exception-handling.html
http://www.vsr.si/ecos/ecos/cvsdoc/devapi-device-driver-interface-to-the-kernel.html
>
> Is there any document which explains the implementation methodology...? or
> source code document..?
If you need more detail, read the code. I would recommend starting
with the MIPS or PowerPC HALs, since these architectures are cleaner
in this area that things like the ARM or 386.
--
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss