From: Andrey Volkov <avolkov@varma-el•com>
To: Andrea Galbusera <andrea.galbusera@teamware•it>
Cc: dedekind@yandex•ru, linux-mtd@lists•infradead.org,
linuxppc-embedded@ozlabs•org
Subject: Re: JFFS2 on Lite5200
Date: Tue, 17 Oct 2006 17:20:37 +0400 [thread overview]
Message-ID: <4534D8A5.7060206@varma-el.com> (raw)
In-Reply-To: <1161081183.22948.58.camel@localhost.localdomain>
Hello Andrea,
Andrea Galbusera wrote:
> Hello.
>
> I'm currently using linux-2.6.16 from denx on a Lite5200 V2.0. I need to
> access a JFFS2 filesystem on the onboard flash ( 16MB Am29L652D ).
>
> I see the flash using physmap driver and cmdline partitions.
> I experience a problem when creating files on JFFS2 with filename longer
> than a few characters. They appear to be created correctly with the
> content I want, but, after unmounting and remounting the filesystem they
> result unreadable and ls complains with "no such file or
> directory" (short-named files are ok).
--snip--
OMG, again same question,
Andrea, check ml archive, I already sent patch half-year ago
(http://ozlabs.org/pipermail/linuxppc-embedded/2006-April/022566.html)
Problem is in alignment/memcpy: JFFS2 code assumed that memory at
unaligned addresses could be touched, but access to an external MMIO
on MPC5200 _must_ be aligned (i.e. you could not read u32 from odd address).
P.S. Artem, I repeat, I sent this patch _HALF_YEAR_AGO_
how about to fix scan.c?
--
Regards
Andrey
next prev parent reply other threads:[~2006-10-17 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 10:33 JFFS2 on Lite5200 Andrea Galbusera
2006-10-17 13:20 ` Andrey Volkov [this message]
2006-10-17 13:36 ` Artem Bityutskiy
2006-10-17 13:54 ` Andrey Volkov
2006-10-17 17:37 ` David Woodhouse
2006-10-17 20:16 ` Andrey Volkov
2006-10-17 14:18 ` Artem Bityutskiy
2006-10-17 20:37 ` Wolfgang Denk
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=4534D8A5.7060206@varma-el.com \
--to=avolkov@varma-el$(echo .)com \
--cc=andrea.galbusera@teamware$(echo .)it \
--cc=dedekind@yandex$(echo .)ru \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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