Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8106] New: mkfs.jffs2 uses the --pagesize parameter incorrectly
Date: Fri, 15 May 2015 06:24:50 +0000 (UTC)	[thread overview]
Message-ID: <bug-8106-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=8106

           Summary: mkfs.jffs2 uses the --pagesize parameter incorrectly
           Product: buildroot
           Version: 2015.02
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: mlesniew at gmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Buildbot is able to generate the output image in different formats, one of them
is JFFS2.  The image is created as usual using the mkfs.jffs2 tool.  As the
JFFS2 system is intended for use with mtd devices, the tool allows specifying
the parameters of the flash memory, to which the image will be written.

Now in buildroot's config one can choose the type of flash, for which the JFFS2
image will be generated.  This are the BR2_TARGET_ROOTFS_JFFS2_NANDFLASH_*
configuration variables.  Selecting one of them sets
BR2_TARGET_ROOTFS_JFFS2_EBSIZE and BR2_TARGET_ROOTFS_JFFS2_PAGESIZE values.

BR2_TARGET_ROOTFS_JFFS2_EBSIZE is the erase block size.  It should match the
erase block size of the flash memory that will store the image.  This value is
later used as a parameter to mkfs.jffs2 (the --eraseblock option).  This one is
used correctly. 

The BR2_TARGET_ROOTFS_JFFS2_PAGESIZE variable is set to the flash memory page
size.  During the build it is used as the value of the --pagesize parameter for
mkfs.jffs2.

It turns out, that the --pagesize parameter of mkfs.jffs2 has nothing to do
with the NAND page size.  It should be set to the virtual memory management
page size of the target system.  In most cases this should be set to 4K, which
is the default value used if --pagesize is not supplied. 

Please consult the mkfs.jffs2 manual page (and the --help output) for details.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2015-05-15  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  6:24 bugzilla at busybox.net [this message]
2015-05-15 13:41 ` [Buildroot] [Bug 8106] mkfs.jffs2 uses the --pagesize parameter incorrectly bugzilla at busybox.net
2015-05-22  7:45 ` bugzilla at busybox.net
2015-05-22  9:37 ` bugzilla at busybox.net

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=bug-8106-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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