From: Wolfgang Denk <wd@denx.de>
To: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: /dev/flash and MTD
Date: Fri, 09 Aug 2002 21:33:08 +0200 [thread overview]
Message-ID: <20020809193313.21BAA10DE1@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 09 Aug 2002 11:34:58 PDT." <3D540B52.8080709@redswitch.com>
In message <3D540B52.8080709@redswitch.com> you wrote:
> To enable MTD on a board, do we still need /dev/flash? In other words,
No, this is not needed for MTD. It's an alternative interface to
access flash memory; we mostly keep it for compatibility with older
projects, and because it provides some nice features like allowing to
mmap() the flash (RO).
> is there any relationship between /dev/flash and MTD? I found that only
> on Denx distribution of 2.4.4 there is such a device '/dev/flash'. Thanks.
These are two independend solutions to the task of providing access
to flash memory; MTD is superior when you also need a block device
interface.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
When you say "I wrote a program that crashed Windows", people just
stare at you blankly and say "Hey, I got those with the system, *for
free*". - Linus Torvalds in <3itc77$9lj@ninurta.fer.uni-lj.si>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-09 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D540B52.8080709@redswitch.com>
2002-08-09 18:38 ` /dev/flash and MTD diekema_jon
2002-08-09 19:33 ` Wolfgang Denk [this message]
[not found] <3D54526C.80703@redswitch.com>
2002-08-10 8:37 ` Wolfgang Denk
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=20020809193313.21BAA10DE1@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=xjin@redswitch.com \
/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).