From: Josh Boyer <jwboyer@jdub.homelinux.org>
To: "Garcia Jérémie" <GARCIAJ@3il.fr>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: How to read/write in flash memories (MTD)?
Date: Thu, 31 Mar 2005 17:34:21 -0600 [thread overview]
Message-ID: <1112312061.12105.32.camel@jdub.homelinux.org> (raw)
In-Reply-To: <D4FDDD1349B5AC46B68FC26AD8AF42D6226B17@exnet.3il.fr>
On Thu, 2005-03-31 at 11:59 +0200, Garcia J=C3=A9r=C3=A9mie wrote:
> L&G,
> Although I'm a newbie in linux kernel development, I'm in charge of adapt=
ing a Montavista LSP to fit our hardware. In our platform, we use 2 AMD fla=
sh memories (AM29LV) in which one we would like to process read/write opera=
tions. So I'm looking for a way to do that. I saw that at compilation time,=
there is MTD item which seems to be created for that. But I guess activate=
that will not be enough to reach my objective.
You need to enable MTD with the appropriate chip drivers and either the
MTD character device or the MTD block device (or both). These will
create /dev/mtdX and /dev/mtdblockX respectively. If you are using
devfs or sysfs + udev, they should show up in /dev. Otherwise, you'll
need to use mknod to create them.
> Indeed, we are developping an application (in the user-space) which will =
initiate operation on the 2 flash memories. So, how can I access them from =
my application?
> Please help me cause I'm getting lost in the linux sources....
I'm not sure what kind of operations you mean, but the block and char
devices allow read/write operation. If you are looking for a filesystem
to run on these devices, take a look at JFFS2. Cramfs or squashfs can
also be used, but they are read-only.
josh
prev parent reply other threads:[~2005-04-01 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 9:59 How to read/write in flash memories (MTD)? Garcia Jérémie
2005-03-31 23:34 ` Josh Boyer [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=1112312061.12105.32.camel@jdub.homelinux.org \
--to=jwboyer@jdub.homelinux.org \
--cc=GARCIAJ@3il.fr \
--cc=linuxppc-dev@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