From: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
To: "Jürgen Lambrecht" <J.Lambrecht@televic.com>
Cc: Chris Zimman <czimman@bloomberg.com>,
Andrew Lunn <andrew@lunn.ch>,
Srinivas rao <ch_srinivas321@yahoo.co.in>,
ecos <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] jffs2_1 test case error
Date: Thu, 27 Mar 2008 09:04:00 -0000 [thread overview]
Message-ID: <47EB6291.6040202@televic.com> (raw)
In-Reply-To: <47EA6B35.2050902@televic.com>
Jürgen Lambrecht wrote:
> Chris Zimman wrote:
>
>> Just for what it's worth -- unless you are using the new eCosCentric V2
>> flash drivers, make sure you have interrupts disabled during JFFS2
>
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).
Jürgen
>>
> JFFS2 accesses take so long that I cannot allow to disable interrupts
>
>> access. eCosCentric did a lot of work on JFFS2 to make it stable under
>> eCos. I have no idea how well the stock JFFS2 code works.
>>
>>
> Would it be a good idea to use the flash_v2 branch?
> I don't know if all eCosCentric code is already commited there?
> Kind regards,
> 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-27 9:02 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 [this message]
2008-03-27 9:58 ` Chris Zimman
2008-03-28 15:24 ` Jürgen Lambrecht
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=47EB6291.6040202@televic.com \
--to=j.lambrecht@televic.com \
--cc=andrew@lunn.ch \
--cc=ch_srinivas321@yahoo.co.in \
--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).