public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: "Carlos, John J USAATC" <john.carlos@atc.army.mil>,
	linux-mtd@lists.infradead.org
Subject: Re: Another mkfs.jffs2 question pagesize verse size of image?
Date: Thu, 3 Jun 2004 22:04:36 +0200	[thread overview]
Message-ID: <200406032204.36458.tglx@linutronix.de> (raw)
In-Reply-To: <EFF9A3506F74924AB5CC77BDC66E79351812AE@atcml01.atc.army.mil>

On Thursday 03 June 2004 22:01, Carlos, John J USAATC wrote:
> Hi,
>
>   I run mkfs.jffs2 on my host.  When I use defaults to create image and the
> try to write to the DOC using nandwrite I get input file is not page
> aligned.  When I try to create the jffs2 image using the -s 512 and -e
> 32768 my image grows to large.  Should the values of page size be 512 bytes
> " from documentation pdf file" and 32768 erase size as reported by
> mtd_debug???????

nandwrite does not work on DOC if you use the DOC driver in mtd/devices. JFFS2 
does neither.

Dan Brown is working on the DOC code which uses the generic nand driver code 
and can be used with JFFS2 and the nand tools.

Read the maillist archive and contact Dan.

-- 
Thomas
________________________________________________________________________
Steve Ballmer quotes the statistic that IT pros spend 70 percent of their 
time managing existing systems. That couldn’t have anything to do with 
the fact that 99 percent of these systems run Windows, could it?
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

      reply	other threads:[~2004-06-03 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 20:01 Another mkfs.jffs2 question pagesize verse size of image? Carlos, John J USAATC
2004-06-03 20:04 ` Thomas Gleixner [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=200406032204.36458.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=john.carlos@atc.army.mil \
    --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