From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: "Nick Garnett" <nickg@ecoscentric.com>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Problems with ISR/DSR stacks
Date: Wed, 06 Jun 2007 10:26:00 -0000 [thread overview]
Message-ID: <c09652430706060236m5f93caa1oa2422068121bbd99@mail.gmail.com> (raw)
In-Reply-To: <m3bqfth1ja.fsf@xl5.calivar.com>
On 06 Jun 2007 10:31:37 +0100, Nick Garnett <nickg@ecoscentric.com> wrote:
> "Øyvind Harboe" <oyvind.harboe@zylin.com> writes:
>
> > Enabling INFRA_DEBUG crashes my "rocket"...
> >
> > As far as I can tell the DSR runs run on the thread stack and not the
> > interrupt stack(from inside interrupt_end).
>
> No. DSRs run on the interrupt stack. This is what
> hal_interrupt_stack_call_pending_DSRs() does.
Ah. OK. I'll have to dig into that, but that does give interrupt
stacks a lot more oomph.
> If you disable the interrupt stack then you have to deal with the
> consequences. It is not recommended unless you know what you are
> doing.
I haven't added interrupt stacks to my HAL yet, but is sure is on my
list now(together with GDB support and a number of other things). :-)
Thanks for the clarification!
--
Øyvind Harboe
http://www.zylin.com - eCos ARM & FPGA developer kit
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-06-06 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 9:36 Øyvind Harboe
2007-06-06 9:51 ` Nick Garnett
2007-06-06 10:26 ` Øyvind Harboe [this message]
2007-06-06 14:41 ` Nick Garnett
2007-06-06 15:26 ` Øyvind Harboe
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=c09652430706060236m5f93caa1oa2422068121bbd99@mail.gmail.com \
--to=oyvind.harboe@zylin.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=nickg@ecoscentric.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).