From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: ben@simtec.co.uk, linuxppc-dev@ozlabs.org,
linux-mtd@lists.infradead.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: OF compatible MTD platform RAM driver ?
Date: Thu, 27 Mar 2008 10:24:45 +0100 [thread overview]
Message-ID: <200803271024.51591.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <47EA6E88.5050109@ru.mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
On Wednesday 26 March 2008 16:40, Sergei Shtylyov wrote:
> Segher Boessenkool wrote:
>
> >> - Using another device node with a compatible value set to
> >> "linear-ram" (or
> >> something similar). This would support both volatile and non-volatile
> >> devices, and a property could be added to specify if the device is
> >> volatile
> >> or not.
>
> > "memory-mapped-memory" perhaps :-)
>
> > Or, just "memory". Although that one might play havoc with some
>
> I'd suggest "ram" and "rom" then. Luckily the device trees don't contain
> binding for the real RAM chips yet. :-)
And when it will we'll be in trouble.
Here are a few names. I like physmap-r[ao]m better. Does anyone have another
suggestion ? I'd like to send a revised patch.
linear-r[ao]m
linear-mapped-r[ao]m
mapped-r[ao]m
memory-mapped-r[ao]m
physmap-r[ao]m
> > not-quite-correct main memory probing code.
>
> You mean the there's parsers that search the "compatible" prop for
> "memory" as well as "device_type" prop?
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-27 9:24 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
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 [this message]
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=200803271024.51591.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 \
--cc=sshtylyov@ru.mvista.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).