From: "Ned W. Rhodes" <ned@softwaresystemsgroup.com>
To: "'David H. Lynch Jr.'" <dhlii@dlasys.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: MTD Flash Howto ?
Date: Fri, 4 Aug 2006 10:20:09 -0400 [thread overview]
Message-ID: <001a01c6b7d1$17dd6130$6201eed0@ssgpoweredge> (raw)
In-Reply-To: <mailman.2056.1154699657.11183.linuxppc-embedded@ozlabs.org>
The book Building Embedded Linux Systems has a good section on the use of
flash file systems.
When you boot, you will see something like this, depending on the type of
flash driver you have. Make sure you have defined your mtd map in
kernel/drivers/mtd/map.
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
JFS: nTxBlock = 965, nTxLock = 7720
Then if you have the MTD partitions correctly identified, the kernel will
show you something like:
CBG flash bank 0: Found 1 x16 devices at 0x0 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Creating 2 MTD partitions on "CBG flash bank 0":
0x00000000-0x01800000 : "ffw1"
0x01800000-0x02000000 : "filesystem1"
Once booted you can look at /proc/mtd and you should see the partitions
something like:
[root@lbg ]# cat /proc/mtd
dev: size erasesize name
mtd0: 01800000 00020000 "ffw1"
mtd1: 00800000 00020000 "filesystem1"
Your mileage may vary depending on the type of flash you have and all the
configuration options, but that is basically how to tell that things are
mapped and ready for use.
Ned W. Rhodes
Software System Group
703.812.5072 x100
next parent reply other threads:[~2006-08-04 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2056.1154699657.11183.linuxppc-embedded@ozlabs.org>
2006-08-04 14:20 ` Ned W. Rhodes [this message]
2006-08-04 15:52 ` MTD Flash Howto ? David H. Lynch Jr.
2006-08-11 21:26 ` Lee Revell
2006-08-04 7:10 Josu Onandia
-- strict thread matches above, loose matches on Subject: below --
2006-08-04 4:04 David H. Lynch Jr.
2006-08-04 16:41 ` T Ziomek
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='001a01c6b7d1$17dd6130$6201eed0@ssgpoweredge' \
--to=ned@softwaresystemsgroup.com \
--cc=dhlii@dlasys.net \
--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;
as well as URLs for NNTP newsgroup(s).