From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: devicetree-discuss@ozlabs.org, Vitaly Wool <vwool@ru.mvista.com>,
Artem Bityutskiy <dedekind@infradead.org>,
linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org,
Ken MacLeod <ken@bitsko.slc.ut.us>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd/maps: add mtd-ram support to physmap_of
Date: Fri, 31 Jul 2009 21:47:10 +0200 [thread overview]
Message-ID: <1249069643.3687.0@antares> (raw)
In-Reply-To: <1247834363-28198-1-git-send-email-w.sang@pengutronix.de> (from w.sang@pengutronix.de on Fri Jul 17 14:39:23 2009)
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
Am 17.07.09 14:39 schrieb(en) Wolfram Sang:
> Use physmap_of to access RAMs as mtd and add documenation for it.
> This approach is a lot less intrusive as adding an of-wrapper around
> plat-ram.c. As most extensions of plat-ram.c (e.g. custom
> map-functions) can't be mapped to the device tree anyhow, extending
> physmap_of seems to be the cleanest approach.
The patch works nicely on a custom (roughly Icecube) based 5200B board,
with a Renesas static ram, no partitions and a jffs2 file system on
it. I had to add some more tweaks to physmap_of.c as to work around
the 5200's limitations accessing chips in 16-bit mode through the local
bus, which is a lot easier and cleaner with this patch than with the
old one (of 05 June 09).
Acked-by: Albrecht Dreß <albrecht.dress@arcor.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-07-31 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 12:39 [PATCH] mtd/maps: add mtd-ram support to physmap_of Wolfram Sang
2009-07-31 19:47 ` Albrecht Dreß [this message]
2009-08-08 5:43 ` Grant Likely
2009-08-09 5:17 ` Artem Bityutskiy
2009-08-10 16:19 ` Wolfram Sang
2009-08-10 16:25 ` Artem Bityutskiy
2009-08-11 5:55 ` Artem Bityutskiy
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=1249069643.3687.0@antares \
--to=albrecht.dress@arcor.de \
--cc=dedekind@infradead.org \
--cc=devicetree-discuss@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=ken@bitsko.slc.ut.us \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=vwool@ru.mvista.com \
--cc=w.sang@pengutronix.de \
/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).