This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: [PATCH] fix possible jffs2 deadlock (sync with mtd cvs)
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Neundorf, Alexander" <Alexander dot Neundorf at jenoptik dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Mon, 2 Aug 2004 15:03:26 +0200
- Subject: Re: [ECOS] [PATCH] fix possible jffs2 deadlock (sync with mtd cvs)
- References: <5A8A17126B73AC4C83968F6C4505E3C5EA647A@JO-EX01.JENOPTIK.NET>
On Mon, Aug 02, 2004 at 02:55:55PM +0200, Neundorf, Alexander wrote:
>
> ...
> > > Another question:
> > >
> > > The file jffs2/..../fs-ecos.c contains a check for gcc
> > 3.2.x and ARM_ARCH_4 -> #error This compiler is known to be broken
> > >
> > > Does this also apply for ARM_ARCH_5 ?
> > > It compiles here with -mcpu=xscale and gcc 3.2.1 ...
> >
> > I don't know if the strongARM code is also broken. I suggest you take
> > a look at the referenced discussion and look at the assembly language
> > your compiler is generating. If it is also broken let me know and i
> > will extend the #error for ARM_ARCH_5.
> >
>
> Ok, I'll have a look.
> What about the patch ?
It was decided by the jffs2 maintainer to reject the patch. Its the
compiler that is broken, not JFFS2. Fixing the compiler is the proper
solution.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss