From: michael@walle.cc (Michael Walle)
To: linux-arm-kernel@lists.infradead.org
Subject: orion/kirkwood and device tree
Date: Sun, 6 Nov 2011 23:40:58 +0100 [thread overview]
Message-ID: <201111062340.59042.michael@walle.cc> (raw)
In-Reply-To: <20111106160538.GD19491@lunn.ch>
Hi Andrew,
thanks for the patch,
Am Sonntag 06 November 2011, 17:05:38 schrieb Andrew Lunn:
> Soon to follow is my patch to cleanup the address mapping of orion
> based platforms. I think this is one step towards solving your
> kirkwood_mbus_dram_info problem. I think the next steps are:
>
> Rename all the {kirkwood|dove|orion5x|mv78xx0}_mbus_dram_info to
> orion_mbus_dram_info and move this variable into
> arch/arm/plat-orion/addr-map.c.
>
> Move all the address setup code which is currently in various drives
> into arch/arm/plat-orion/addr-map.c. Remove orion_mbus_dram_info from
> all the platform_data structures.
mh and then use orion_mbus_dram_info directly within the device drivers?
--
Michael
next prev parent reply other threads:[~2011-11-06 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111031105740.GC29402@lunn.ch>
[not found] ` <20111031152100.GR32165@titan.lakedaemon.net>
[not found] ` <20111031164042.GD29402@lunn.ch>
2011-10-31 22:50 ` orion/kirkwood and device tree Michael Walle
2011-10-31 22:54 ` Russell King - ARM Linux
2011-11-01 6:25 ` Andrew Lunn
2011-11-02 16:50 ` Jason
2011-11-02 22:03 ` Michael Walle
2011-11-03 18:15 ` memory map in fdt was: " Jason
2011-11-03 18:15 ` Jason
2011-11-03 18:47 ` Jason
2011-11-03 21:50 ` Michael Walle
2011-11-04 9:21 ` Simon Guinot
2011-11-16 23:34 ` Michael Walle
2011-11-04 14:01 ` Nicolas Pitre
2011-11-06 23:12 ` Michael Walle
2011-11-06 16:05 ` Andrew Lunn
2011-11-06 22:40 ` Michael Walle [this message]
2011-11-07 6:27 ` Andrew Lunn
2011-11-07 2:35 ` Nicolas Pitre
2011-11-07 6:28 ` Andrew Lunn
2011-11-06 16:07 ` [PATCH 1/1] [orion] Consolidate the address map setup on Orion based platforms Andrew Lunn
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=201111062340.59042.michael@walle.cc \
--to=michael@walle.cc \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.