public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrea Galbusera <andrea.galbusera@teamware.it>,
	linux-mtd@lists.infradead.org, linuxppc-embedded@ozlabs.org
Subject: Re: JFFS2 on Lite5200
Date: Wed, 18 Oct 2006 00:16:58 +0400	[thread overview]
Message-ID: <45353A3A.9060609@varma-el.com> (raw)
In-Reply-To: <1161106630.23666.109.camel@hades.cambridge.redhat.com>

David Woodhouse wrote:
> On Tue, 2006-10-17 at 17:54 +0400, Andrey Volkov wrote:
>> No, MPC5200 could write any size chunks, but it must be aligned (same
>> restrictions as in SH4), and this restriction applied only to LPB, but
>> not SDRAM.
>>
>> Also, I've in view that jffs2(jffs3 ?) read/write stuff already used
>> functions which MTD drivers exported, but jffs2_scan_dirent_node and
>> friends - doesn't.
> 
> There are two modes of operation for JFFS2 scan. Either it can use the
> MTD device's read() function to read from the flash into memory and scan
> from there, or -- IF the flash can be accessed as if it were normal
> memory -- it can use the point() method and skip the read() call by
> using a pointer directly into the flash.
> 
> In your case, the flash cannot be accessed directly as if it were normal
> memory. So your map driver probably shouldn't be allowing point() to
> succeed.
> 
> Having said that, I'm not entirely sure we have the code set up so that
> 'simple' map drivers _can_ prevent point(). We may need to fix that.
David, thanks for an explanations (Artem already pointed me to this
jffs2 behavior).

--
Regards
Andrey

  reply	other threads:[~2006-10-17 20:17 UTC|newest]

Thread overview: 7+ 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
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 [this message]
2006-10-17 14:18   ` Artem Bityutskiy

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=45353A3A.9060609@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=andrea.galbusera@teamware.it \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /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