From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: "'Gary Kenaley'" <gkenaley@echelon.com>,
"'Bill Gatliff'" <bgat@billgatliff.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux 2.6.x, MTD drivers and NAND flashes
Date: Tue, 12 Jun 2007 12:06:29 +0200 [thread overview]
Message-ID: <000f01c7acd9$633bc290$5201a8c0@GEG2400> (raw)
In-Reply-To: <DDBD7B17DB2ECE48BCD94C593F7255B4046EA149@monk.echelon.echcorp.com>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
Gary and Bill,
My need is to load a basic Linux kernel on boards to program multiple
NOR and NAND flashes with CRAMFS and JFFS2 (perhaps YAFFS) images.
I usually used mtd character accesses to do the job on NOR flashes.
But flash_eraseall and flashcp seem to be excellent tools.
I'll try them quickly.
Many thanks for your help
Bye
Laurent
> -----Message d'origine-----
> De : Gary Kenaley [mailto:gkenaley@echelon.com]
> Envoyé : lun. 11 juin 2007 21:00
> À : Bill Gatliff; Laurent Lagrange
> Cc : linuxppc-embedded@ozlabs.org
> Objet : RE: Linux 2.6.x, MTD drivers and NAND flashes
>
>
> Laurent,
>
> Can't you just use the flashcp copy command from the
> mtd-utils package?
> --------------------------------------------------------------
> ---------
> flash_eraseall -j /dev/mtd0
>
> mkfs.jffs2 -b -n --eraseblock=131072 --pagesize=2048 -p -r
> /test_root -v -o test_root.img
>
> flashcp test_root.img /dev/mtd0
>
>
> The other way is what Bill mentions:
> ------------------------------------
> flash_eraseall -j /dev/mtd0
> mount -t jffs2 /dev/mtdblock0 /tmp/mnt
> tar -xzf test_root.tgz -C /tmp/mnt
> umount /tmp/mnt
>
> Gary
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2264 bytes --]
next prev parent reply other threads:[~2007-06-12 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 15:20 Linux 2.6.x, MTD drivers and NAND flashes Laurent Lagrange
2007-06-11 15:59 ` Bill Gatliff
2007-06-11 19:59 ` Gary Kenaley
2007-06-12 10:06 ` Laurent Lagrange [this message]
2007-06-12 13:37 ` Detlev Zundel
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='000f01c7acd9$633bc290$5201a8c0@GEG2400' \
--to=lagrange@fr.oleane.com \
--cc=bgat@billgatliff.com \
--cc=gkenaley@echelon.com \
--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