This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: interrupt handling
- To: ecos-discuss at sourceware dot cygnus dot com
- Subject: Re: [ECOS] interrupt handling
- From: Nick Garnett <nickg at cygnus dot co dot uk>
- Date: 29 Aug 2000 14:46:59 +0100
- Newsgroups: cygnus.sourceware.ecos.d
- Organization: Cygnus Solutions, a Red Hat company (Cambridge, UK)
- References: <21DDE8E5343ED411840A00A0CC33402010484D@exchange.sdesigns.com>
Fabrice Gautier <Fabrice_Gautier@sdesigns.com> writes:
> Hi,
>
> Is it possible to attach more than one cyg_interrupt object to the same
> vector?
Only if you enable the chaining option. However this usually also
reduces the number of real vectors in use, often down to one on
targets that need software decoding of interrupts.
>
> If not, what is the behaviour of a cyg_interrupt_attach when the vector is
> already attached?
It should give an error code. It may not on all platforms however.
>
> Is it possible to know the cyg_interrupt object(s) attached to a vector?
>
There is currently no way of enumerating the objects. eCos is meant to
be small enough, and applications sufficiently in control, that this
was considered unnecessary.
--
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK