From: "Garcia Jérémie" <GARCIAJ@3il.fr>
To: <linuxppc-dev@ozlabs.org>
Subject: How to read/write in flash memories (MTD)?
Date: Thu, 31 Mar 2005 11:59:08 +0200 [thread overview]
Message-ID: <D4FDDD1349B5AC46B68FC26AD8AF42D6226B17@exnet.3il.fr> (raw)
L&G,
Although I'm a newbie in linux kernel development, I'm in charge of =
adapting a Montavista LSP to fit our hardware. In our platform, we use 2 =
AMD flash memories (AM29LV) in which one we would like to process =
read/write operations. 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.
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....
NOTE: i'm using a powerPC 405EP
J=E9r=E9mie
next reply other threads:[~2005-03-31 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 9:59 Garcia Jérémie [this message]
2005-03-31 23:34 ` How to read/write in flash memories (MTD)? Josh Boyer
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=D4FDDD1349B5AC46B68FC26AD8AF42D6226B17@exnet.3il.fr \
--to=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