From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: "eCos Discuss" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] FLASH API v.2 and interrupts
Date: Wed, 07 Oct 2009 17:30:00 -0000 [thread overview]
Message-ID: <PGEAIGBPLOMOJDAPCOJHGEKPNNAB.pderocco@ix.netcom.com> (raw)
In-Reply-To: <pntyybta80.fsf@delenn.bartv.net>
> From: Bart Veer
>
> On other hardware the flash driver has to disable the cache before it
> can talk directly to the flash chip. You do not want interrupts or
> context switches while the cache is disabled, the resulting system
> performance would be terrible. The LEAVE_INTERRUPTS_ENABLED option is
> not available on hardware like this.
That seems an odd assumption to make. In lots of systems, max CPU horsepower
is only needed intermittently, and keeping the system responsive, say, to
slow user input would be preferable to shutting everything down during flash
writes.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
--
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-07 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 10:35 Iris Lindner
2009-10-02 10:50 ` [ECOS] IDE failed to identify unit 0 - wrote: a0, read: 7f Jim Bradleigh
2009-10-02 14:06 ` [ECOS] Debugging Redboot Jim Bradleigh
2009-10-07 16:20 ` Bart Veer
2009-10-02 11:13 ` [ECOS] FLASH API v.2 and interrupts Stanislav Meduna
2009-10-07 16:55 ` Bart Veer
2009-10-07 17:30 ` Paul D. DeRocco [this message]
2009-10-07 18:46 ` Bart Veer
2009-10-08 11:22 ` Iris Lindner
2009-10-08 13:50 ` Bart Veer
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=PGEAIGBPLOMOJDAPCOJHGEKPNNAB.pderocco@ix.netcom.com \
--to=pderocco@ix.netcom.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).