From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: PATCH: Add memreserve to DTC
Date: Mon, 11 Jul 2005 16:30:25 +1000 [thread overview]
Message-ID: <20050711063025.GA11752@localhost.localdomain> (raw)
In-Reply-To: <1120859097.8609.15.camel@cashmere.sps.mot.com>
On Fri, Jul 08, 2005 at 04:44:58PM -0500, Jon Loeliger wrote:
> David and Ben,
>
> This patch adds support for memreserve to the DTC's notion
> of the "source file". That is, you can now say this:
>
>
> memreserve = <
> 0000 0001 0000 0002
> 0000 0003 0000 0004
> >
>
> / {
> model = "MPC8555CDS";
> compatible = "MPC85xxCDS";
> #address-cells = <2>;
> #size-cells = <2>;
> linux,phandle = <100>;
>
> There is minor fiddling with the -R flag that needs to be
> resolved at this point.
>
> I've included read and writing for the source and blob formats,
> but don't have a clue what to do with the /proc/devices format.
>
> I've also tinkered the Makefile to do automatic dependency
> file generation and inclusion. Yep, I got bit by out of
> date dependencies during my development here. :-)
I applied the dependency portions of the patch to the git tree, with
some tweaks to fix some corner cases.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/people/dgibson
prev parent reply other threads:[~2005-07-11 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 21:44 PATCH: Add memreserve to DTC Jon Loeliger
2005-07-11 4:55 ` David Gibson
2005-07-11 21:22 ` Jon Loeliger
2005-07-12 2:01 ` David Gibson
2005-07-12 8:02 ` Segher Boessenkool
2005-07-14 1:02 ` David Gibson
2005-07-14 13:29 ` Segher Boessenkool
2005-07-12 4:06 ` David Gibson
2005-07-14 20:03 ` Jon Loeliger
2005-07-15 7:19 ` David Gibson
2005-07-15 14:30 ` Jon Loeliger
2005-07-19 1:17 ` David Gibson
2005-07-11 6:30 ` David Gibson [this message]
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=20050711063025.GA11752@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=jdl@freescale.com \
--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 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.