From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Laurie Gellatly <laurie.gellatly@netic.com>
Cc: eCos discuss-list <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] LPC2XXX watchdog feeds and interrupts
Date: Mon, 26 Oct 2009 21:34:00 -0000 [thread overview]
Message-ID: <20091026213429.GA15230@sg-laptop> (raw)
In-Reply-To: <DD73C537-F2E2-42AD-AB45-7C39EAC8B41C@netic.com>
On Tue, Oct 27, 2009 at 08:03:55AM +1100, Laurie Gellatly wrote:
> Hi Sergei,
> Two things. It should not be an option as when the feed sequence is
> eventually interrupted and the processor is reset it can be VERY
> time consuming to track down. I know from bitter experience. The
> other is I was not sure about which interrupt disable/enable
> function pairs to use. Is HAL_DISABLE_INTERRUPTS preferred over
> cyg_disable_interrupts? We need ALL interrupts off during the feed.
Or cyg_scheduler_{,un}lock() then, but, that is kernel depended.
Perhaps, you are right, IMO, eCos kernel hackers can say the last
words :-) I just wanted to have an optional fix via CDL.
Sergei
--
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:[~2009-10-26 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 20:40 Sergei Gavrikov
2009-10-26 21:05 ` Laurie Gellatly
2009-10-26 21:34 ` Sergei Gavrikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-19 9:32 [ECOS] RedBoot image for Olimex LPC-E2294 peter_lanius
2009-10-19 10:42 ` Sergei Gavrikov
2009-10-19 11:42 ` peter_lanius
2009-10-19 13:47 ` Sergei Gavrikov
2009-10-24 9:37 ` [ECOS] RedBoot loading eCOS examples causes PC reboot peter_lanius
2009-10-24 12:38 ` Sergei Gavrikov
[not found] ` <738229.12555.qm@web51906.mail.re2.yahoo.com>
2009-10-25 13:20 ` Sergei Gavrikov
2009-10-26 9:58 ` [ECOS] LPC2XXX watchdog feeds and interrupts Laurie Gellatly
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=20091026213429.GA15230@sg-laptop \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=laurie.gellatly@netic.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).