linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Re: /dev/flash and MTD
       [not found] <3D540B52.8080709@redswitch.com>
@ 2002-08-09 18:38 ` diekema_jon
  2002-08-09 19:33 ` Wolfgang Denk
  1 sibling, 0 replies; 3+ messages in thread
From: diekema_jon @ 2002-08-09 18:38 UTC (permalink / raw)
  To: "Xiaogeng (Shawn) Jin"; +Cc: linuxppc-embedded


> To enable MTD on a board, do we still need /dev/flash?

No.

> In other words, 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.

The /dev/flash device entries use a stand alone flash driver that
isn't part of MTD.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: /dev/flash and MTD
       [not found] <3D540B52.8080709@redswitch.com>
  2002-08-09 18:38 ` /dev/flash and MTD diekema_jon
@ 2002-08-09 19:33 ` Wolfgang Denk
  1 sibling, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2002-08-09 19:33 UTC (permalink / raw)
  To: Xiaogeng (Shawn) Jin; +Cc: linuxppc-embedded


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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: /dev/flash and MTD
       [not found] <3D54526C.80703@redswitch.com>
@ 2002-08-10  8:37 ` Wolfgang Denk
  0 siblings, 0 replies; 3+ messages in thread
From: Wolfgang Denk @ 2002-08-10  8:37 UTC (permalink / raw)
  To: Xiaogeng (Shawn) Jin; +Cc: linuxppc-embedded


Dear Shawn,

in message <3D54526C.80703@redswitch.com> you wrote:
>
> WINDOW_SIZE. What does this difference mean? If I know the physical
> start address of flash memory and the size, is there a generic map
> driver available to do the probing? My general question is "do we need a
> MTD map driver for each board, especially for those custom boards?".

Actually we don't. Set  the  config  option  CONFIG_MTD_CMDLINE_PARTS
which  allows  the  use  of  a generic mapping driver and passing the
partitioning info from the command line.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Do not follow where the path may lead....go instead where there is no
path and leave a trail.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-08-10  8:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <3D540B52.8080709@redswitch.com>
2002-08-09 18:38 ` /dev/flash and MTD diekema_jon
2002-08-09 19:33 ` Wolfgang Denk
     [not found] <3D54526C.80703@redswitch.com>
2002-08-10  8:37 ` Wolfgang Denk

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).