public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Zimman, Chris" <czimman@bloomberg.com>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] JFFS2 Access and interrupts
Date: Thu, 07 Sep 2006 11:21:00 -0000	[thread overview]
Message-ID: <4B24CC52E8A6EB4A95B414126492987C01616A5A@lo2525.corp.bloomberg.com> (raw)

Most likely, it's not really a problem with JFFS2 itself, but rather
with the underlying flash driver as they're not interrupt safe.  eCosPro
has newer versions of the flash drivers that are interrupt safe.
 
--Chris

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Gary Thomas
Sent: Wednesday, September 06, 2006 8:32 PM
To: Gernot Zankl
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] JFFS2 Access and interrupts

Gernot Zankl wrote:
> Hi all,
> 
> while writing a file in a jffs2 filesystem (by means of open, write,
> close)
> my application seems to hang in function write(). 
> After guarding the write access with
> HA_DISABLE_INTERRUPTS/HAL_RESTORES_INTERRUPTS 
> the write accesses worked properly.
> 
> After a short inspection of flash.c (in packages/io/flash/current/src)
> it seems that in my port these guards are already present,
> placed around the "__anonymizer"-ed flash access functions.
> 
> Is there a general rule, how to handle mutual IRQs and flash access ?
> Do I miss something ?
> Is there a configuration option, I've forgotten to enable ?

There aren't any configuration options for this - it's assumed to work.

Can you please explain in more detail exactly what you've done to get
things to work?  Given that the generic functions (e.g. flash_program)
already disable interrupts, I'm a bit confused.

> 
> Kind regards,
> Gernot Zankl
> 
> Btw: PowerPC MPC5200B and external flash Spansion S29GL064M

Given that the eCos port for the MPC5200 is not public (you got it
from Analogue & Micro), it makes sense to ask these questions of
A&M, not the general list.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-09-07 11:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-07 11:21 Zimman, Chris [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-06 10:50 [ECOS] Getting segmentation fault while unmounting JFFS2 file system 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
2006-09-14 12:56           ` Gary Thomas
2006-09-14 15:15           ` 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=4B24CC52E8A6EB4A95B414126492987C01616A5A@lo2525.corp.bloomberg.com \
    --to=czimman@bloomberg.com \
    --cc=ecos-discuss@sources.redhat.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).