From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: Chris Zimman <czimman@bloomberg.com>
Cc: ecos <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] jffs2_1 test case error
Date: Fri, 28 Mar 2008 15:24:00 -0000 [thread overview]
Message-ID: <47ED0BCD.9030205@televic.com> (raw)
In-Reply-To: <F31C1582037F5041B0CD525FD870AE6A77424D@ny2545.corp.bloomberg.com>
Chris Zimman wrote:
>>The manual states it is only necessary to disable interrupts during
>>flash accesses if your code also resides in flash (ROM image)
>>(http://ecos.sourceware.org/docs-latest/ref/ecos-flash-library.html).
>>
>>
>
>Regardless of what the manual says, I'm telling you from experience, the V1
>flash drivers are not interrupt safe. If you don't disable interrupts while
>flash access is going on, you are going to have problems.
>
>
I have to admit that we *have* problems...
OK, you mean not interrupt safe, so this means the flash drivers need
exact timing...
I'll try the flash_v2 drivers, and I'll keep you informed.
Thanks,
Jürgen
>--Chris
>
>
>
--
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:[~2008-03-28 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 12:56 Chris Zimman
2008-03-26 15:38 ` Jürgen Lambrecht
2008-03-26 15:51 ` Chris Zimman
2008-03-27 9:04 ` Jürgen Lambrecht
2008-03-27 9:58 ` Chris Zimman
2008-03-28 15:24 ` Jürgen Lambrecht [this message]
2008-03-29 8:35 ` Chris Zimman
-- strict thread matches above, loose matches on Subject: below --
2006-10-26 10:33 Srinivas rao
2006-10-26 11:34 ` Andrew Lunn
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=47ED0BCD.9030205@televic.com \
--to=j.lambrecht@televic.com \
--cc=czimman@bloomberg.com \
--cc=ecos-discuss@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).