linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: ben@simtec.co.uk, linux-mtd@lists.infradead.org, linuxppc-dev@ozlabs.org
Subject: Re: OF compatible MTD platform RAM driver ?
Date: Thu, 27 Mar 2008 15:31:34 +0100	[thread overview]
Message-ID: <200803271531.35401.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <20080327100304.GC10397@localhost.localdomain>

On Thursday 27 March 2008 11:03, David Gibson wrote:
> On Thu, Mar 27, 2008 at 10:13:32AM +0100, Laurent Pinchart wrote:
> > On Wednesday 26 March 2008 13:53, Sergei Shtylyov wrote:
> > > Laurent Pinchart wrote:
> [snip]
> > >     Heh, we've gone thru "physmap" before -- it was labelled
> > >     Linux-specific name (well, I'd agree with that).
> >=20
> > physmap stands for physically mapped. That doesn't sound
> > Linux-specific to me, the fact that the MTD driver has the same name
> > is a pure coincidence.  linmap-rom and linmap-rom sound even more
> > Linux-specific :-)
>=20
> It may not be Linux specific per se, but it's a bad name, because the
> fact that the device is physically direct mapped isn't a useful
> distinguishing feature of the device.  Main memory is also direct
> physically mapped, after all, but that's not what you want to cover
> with this description.  In general how a device is wired is described
> by where it sits in the tree, not by its properties.
>=20
> It only seems like a usefully distinguishing name because it's the
> Linux "physmap_of" driver that uses it.  So in this sense it is a
> Linux specific name after all.  In fact, physmap_of is itself very
> badly named - right now it only handles direct mapped mtds, but that's
> not inherent; it could be trivially extended to also instantiate a
> non-direct-mapped device (as long as the underlying mtd layer
> supported it, of course).  It bears no relation at all to the
> "physmap" driver, except historical accident.
>=20
> > Could we agree on a name ? I'd like to submit a new patch.
>=20
> For ROMs I think just plain "rom" should be sufficient.  For RAMs we
> need something to indicate that it's memory but intended for secondary
> storage, not as main memory.  Unfortunately, I'm finding myself unable
> to think of something.

What about "storage-ram", "auxiliary-ram", "secondary-ram", "application-ra=
m",
"user-ram" or "ramdisk" ?

=2D-=20
Laurent Pinchart
CSE Semaphore Belgium

Chauss=E9e de Bruxelles, 732A
B-1410 Waterloo
Belgium

T +32 (2) 387 42 59
=46 +32 (2) 387 42 75

  parent reply	other threads:[~2008-03-27 14:31 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 15:06 OF compatible MTD platform RAM driver ? Laurent Pinchart
2008-03-10 17:00 ` Rune Torgersen
2008-03-11  0:45   ` David Gibson
2008-03-11 10:39     ` Laurent Pinchart
2008-03-11 22:40       ` David Gibson
2008-03-25 14:36         ` Laurent Pinchart
2008-03-25 15:29           ` Sergei Shtylyov
2008-03-25 15:51             ` Laurent Pinchart
2008-03-25 16:23               ` Sergei Shtylyov
2008-03-25 16:44                 ` Laurent Pinchart
2008-03-25 17:02                   ` Sergei Shtylyov
2008-03-25 17:23                     ` Laurent Pinchart
2008-03-25 17:37                       ` Sergei Shtylyov
2008-03-25 17:56                       ` Rune Torgersen
2008-03-25 18:14                         ` Laurent Pinchart
2008-03-26 12:53                           ` Sergei Shtylyov
2008-03-27  9:13                             ` Laurent Pinchart
2008-03-27 10:03                               ` David Gibson
2008-03-27 12:23                                 ` Sergei Shtylyov
2008-03-28  0:07                                   ` David Gibson
2008-03-28 12:31                                     ` Sergei Shtylyov
2008-03-27 14:31                                 ` Laurent Pinchart [this message]
2008-03-28  0:09                                   ` David Gibson
2008-03-30 18:15                                 ` Segher Boessenkool
2008-03-30 21:16                                   ` Paul Mackerras
2008-03-30 22:39                                     ` Segher Boessenkool
2008-03-31  0:42                                       ` Paul Mackerras
2008-03-31  0:59                                         ` Segher Boessenkool
2008-03-31  1:24                                           ` Segher Boessenkool
2008-03-31  8:21                                       ` Laurent Pinchart
2008-03-31 12:21                                         ` Segher Boessenkool
2008-03-26 15:06                           ` Segher Boessenkool
2008-03-26 15:40                             ` Sergei Shtylyov
2008-03-27  9:24                               ` Laurent Pinchart
2008-03-30 18:12                               ` Segher Boessenkool
2008-03-26 15:09                   ` Segher Boessenkool
2008-03-11 15:00     ` Rune Torgersen
2008-03-11 22:41       ` David Gibson

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=200803271531.35401.laurentp@cse-semaphore.com \
    --to=laurentp@cse-semaphore.com \
    --cc=ben@simtec.co.uk \
    --cc=david@gibson.dropbear.id.au \
    --cc=linux-mtd@lists.infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).