* [ECOS] EB40a flash programming, interrupts and multithreading
@ 2003-09-10 13:48 Øyvind Harboe
0 siblings, 0 replies; only message in thread
From: Øyvind Harboe @ 2003-09-10 13:48 UTC (permalink / raw)
To: 'ecos-discuss (E-Mail)'
Does the scheme below put this issue to bed once and
for all?
1. move all interrupt code and data to ram
2. During flash programming, lock the scheduler
(disable other threads), leave interrupts running.
3. the above should be written such that the user can overide
the default implementation of the flash programming
pre-post sequence, e.g. to only disable certain threads, or
to do nothing(since the app is known to be entirely in ram).
Earlier discussions on this didn't end up with
a conclusion:
http://sources.redhat.com/ml/ecos-patches/2003-08/msg00041.html
Øyvind
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-09-10 13:48 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-10 13:48 [ECOS] EB40a flash programming, interrupts and multithreading Øyvind Harboe
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).