public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Different erase block sizes in a JFFS2 partion.
Date: Fri, 29 Sep 2006 08:43:36 +0200	[thread overview]
Message-ID: <451CC098.7050805@transmode.se> (raw)
In-Reply-To: <625fc13d0609281607l5d2ad581k9615afa8d4f3caa@mail.gmail.com>

Josh Boyer wrote:
> On 9/28/06, Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:
>> Got multiple NOR chips with top and bottom boot blocks with diffrent EB size
>> then the rest of the blocks.
> 
> Intel P30?  IIRC, the MTD driver maps those into a set of larger
> virtual eraseblocks.  You might not be able to even distinguish that
> they exist.

yes, Intel P30.
The cfi_cmdset_0001 driver maps them like this:
0: offset=0x0,size=0x8000,blocks=4
1: offset=0x20000,size=0x20000,blocks=255
2: offset=0x2000000,size=0x8000,blocks=4
3: offset=0x2020000,size=0x20000,blocks=255

First, this map is wrong. 2: and 3: should be swapped, that is,
the small blocks should be at the end of the device.

the small blocks fits into a larger one so I should have no problem reading/writing
to such virtual block, but I don't think erase will work as JFFS2 will
only erase one of the small blocks instead of all 4. Maybe I am missing something?

      reply	other threads:[~2006-09-29  6:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 21:55 Different erase block sizes in a JFFS2 partion Joakim Tjernlund
2006-09-28 23:07 ` Josh Boyer
2006-09-29  6:43   ` Joakim Tjernlund [this message]

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=451CC098.7050805@transmode.se \
    --to=joakim.tjernlund@transmode.se \
    --cc=jwboyer@gmail.com \
    --cc=linux-mtd@lists.infradead.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