public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Aaron Case" <aaron.case@dynazign.com>
To: "Ecos-Discuss" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] context for creating interrupts on edb7312
Date: Wed, 19 Nov 2003 16:34:00 -0000	[thread overview]
Message-ID: <GBEOKKOEOGFDMKDFCHIMAENKCAAA.aaron.case@dynazign.com> (raw)

Hello,

My question pertains to the context for which an interrupt would be created
and attached.

The Massa text shows an example where an interrupt is created, attached, and
unmasked in cyg_user_start(), see code listing 3.2. Yet 3 pages later, see
Item list 3.7, it gives thread(and not init as in the code listing) as the
only viable context for creating a interrupt(via cyg_interrupt_create).
This seems to be in conflict.

Intuitively, creation of interrupts would be in cyg_user_start, init
context, like the code listing example BUT, I was never able to get this to
work. I have however been able to get work in the thread context, which
agrees with the item list but seems counter intuitive.

The eCos reference manual confirms my intuition by stating the following in
the valid context section of the ref manual...

"In a typical configuration interrupt handlers are created and attached
during system initialization, and never detached or deleted. However it is
possible to perform these operations at thread level, if desired..."

I, however, have not be able to get interrupts to work in the init context,
only in the thread context.

------Is creating interrupts within the init context possible?-------

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.

I would also like to add, Im not criticizing the online docs, they appear
correct, just a bit generic(so as to apply to all platforms, I assume).

Aaron Case
Firmware Engineer
Dynazign, Inc.
Charlotte, NC


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2003-11-19 16:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 16:34 Aaron Case [this message]
2003-11-19 19:36 ` Gary Thomas
2003-11-19 20:22   ` Aaron Case
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=GBEOKKOEOGFDMKDFCHIMAENKCAAA.aaron.case@dynazign.com \
    --to=aaron.case@dynazign.com \
    --cc=ecos-discuss@sources.redhat.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).