From: "Gernot Zankl" <zankl@decomsys.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] JFFS2 Access and interrupts
Date: Thu, 14 Sep 2006 12:42:00 -0000 [thread overview]
Message-ID: <0F0005CE495E094A96B04D78F24E5A7F3858B5@mana.decomsys.com> (raw)
In-Reply-To: <45094B9D.7020208@mlbassoc.com>
Gary Thomas wrote:
> Gernot Zankl wrote:
> > Hi all !
> >
> > Thanks for your answers.
> > FYI I finally found the/our bug, causing the application to
> > corrupt the jffs2. We just used the wrong block size in
> > the configuration of the underlying flash driver, causing to
> > erase too much flash memory (and destroying still active inodes).
>
> FAOD - it had *nothing* to do with interrupts during FLASH operations?
At least not in "our" version of the flash driver (v1) which has been
provided and modified by Analogue&Micro, where all calls to the
critical functions are guarded by the HAL_DISABLE_INTERRUPTS and
HAL_RESTORES_INTERRUPTS macros.
Regards,
Gernot Zankl
Btw. what does "FAOD" mean, "Fatty acid oxidation disorder" ?
--
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:[~2006-09-14 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 10:36 [ECOS] Getting segmentation fault while unmounting JFFS2 file system Amitesh Singh
2006-09-06 10:50 ` Gary Thomas
2006-09-06 16:43 ` [ECOS] JFFS2 Access and interrupts Gernot Zankl
2006-09-06 19:32 ` Gary Thomas
2006-09-07 14:50 ` Bart Veer
2006-09-08 8:43 ` Andrew Lunn
2006-09-08 10:00 ` Gernot Zankl
2006-09-08 16:58 ` Andrew Lunn
2006-09-14 12:27 ` Gernot Zankl
2006-09-14 12:31 ` Gary Thomas
2006-09-14 12:42 ` Gernot Zankl [this message]
2006-09-14 12:56 ` Gary Thomas
2006-09-14 15:15 ` Bart Veer
2006-09-07 11:21 Zimman, Chris
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=0F0005CE495E094A96B04D78F24E5A7F3858B5@mana.decomsys.com \
--to=zankl@decomsys.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@mlbassoc.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).