From: "Aaron Case" <aaron.case@dynazign.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "Ecos-Discuss" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] context for creating interrupts on edb7312
Date: Wed, 19 Nov 2003 20:22:00 -0000 [thread overview]
Message-ID: <GBEOKKOEOGFDMKDFCHIMOENLCAAA.aaron.case@dynazign.com> (raw)
In-Reply-To: <1069270590.1961.618.camel@hermes>
>
> ------Is creating interrupts within the init context possible?-------
>
What do you mean "creating" interrupts? Do you mean actually fielding
them (when they occur)? In that case, no, since interrupts are not
turned on (enabled) until you call the scheduler.
a call(s) to cyg_interrupt_create()
> I am using the EDB7312 processor with the arm720t core.
>
> I would prefer to locate all interrupt creation and configuration in
> cyg_user_start, the init context, but have had little success in doing so.
>
Can you explain what you mean by this?
Calls to cyg_interrupt_create(), cyg_intterrupt_attach(), and
cyg_interrupt_unmask() that create and configure the interrupt structure of
the system.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-11-19 20:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:34 Aaron Case
2003-11-19 19:36 ` Gary Thomas
2003-11-19 20:22 ` Aaron Case [this message]
2003-11-19 22:18 ` Gary Thomas
2003-11-20 14:25 ` Aaron Case
2003-11-20 14:35 ` Gary Thomas
2003-11-20 15:01 ` Aaron Case
2003-11-20 15:21 ` Gary Thomas
2003-11-21 15:06 ` Aaron Case
2003-11-21 15:55 ` Gary Thomas
2003-11-21 16:32 ` Aaron Case
2003-11-21 17:22 ` Gary Thomas
2003-11-21 17:28 ` Gary Thomas
2003-11-21 18:28 ` Aaron Case
2003-11-19 16:50 amassa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=GBEOKKOEOGFDMKDFCHIMOENLCAAA.aaron.case@dynazign.com \
--to=aaron.case@dynazign.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@mlbassoc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).