public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: oyvind.harboe@zylin.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Stress testing JFFS2
Date: Tue, 07 Oct 2003 13:43:00 -0000	[thread overview]
Message-ID: <20031007134301.GC15932@lunn.ch> (raw)
In-Reply-To: <1065532608.5999.8.camel@famine>

On Tue, Oct 07, 2003 at 03:16:48PM +0200, ?yvind Harboe wrote:
> > Please could you give us a complete test case. Something we can run
> > ourselves. Create a new bugzilla bug on bugs.ecos.sourceware.org and
> > include the source code and the ecos configuration you are using. 
> > 
> > That will make it much easier for us to see whats happening.
> 
> OK.
> 
> But I need a few pointers. Clearly this standalone test case 
> should not be EB40a specific. 
> 
> Ideally anyone should be able to run the testcase, but setting up a
> JFFS2 mount consists of a fair bit of hardware specific ecos.ecc
> manipulations, etc.

Yep. Ideally would be to write a test case which runs on the synth
target. We can all work with that. This does work, i've run the
standard test case on synth before.

> This might not be eCos specific, but I would expect the eCos community
> having greater interest in this kind of bug being fixed than
> non-embedded applications.

Actually, it could be ecos specific. There is an wrapper round jffs2
which implements the interface between eCos fileio and jffs2. The
problem could be in there. Also, its easier to debug jffs2 in eCos
than inside a linux kernel.

     Andrew

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

  reply	other threads:[~2003-10-07 13:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 10:57 Øyvind Harboe
2003-10-07 12:31 ` David Vrabel
2003-10-07 13:04 ` Andrew Lunn
2003-10-07 13:16   ` Øyvind Harboe
2003-10-07 13:43     ` Andrew Lunn [this message]
2003-10-07 16:42       ` Thomas Koeller
2003-10-07 17:57         ` Andrew Lunn
2003-10-08  8:34           ` Thomas Koeller
2003-10-07 13:36 ` Eric Donnat
2003-10-07 16:43 Øyvind Harboe
2003-10-08  7:37 Øyvind Harboe
2003-10-08  9:07 ` Jani Monoses
2003-10-15 10:07   ` Thomas Koeller
2003-10-15 10:52     ` David Woodhouse
2003-10-15 11:26       ` Thomas Koeller
2003-10-16 10:25         ` David Woodhouse
2003-10-15 11:53 Dinesh Kumar
2003-10-15 12:54 ` Thomas Koeller
2003-10-15 18:33 Doug Fraser
2003-10-16  7:23 Øyvind Harboe
2003-10-16  7:32 ` Andrew Lunn
2003-10-16  7:35   ` Øyvind Harboe

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=20031007134301.GC15932@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=oyvind.harboe@zylin.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).