From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jimi Xenidis <jimix@watson.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [patch][rfc]flattened device tree: Passing a dtb (blob) to Linux.
Date: Fri, 14 Apr 2006 09:12:13 +1000 [thread overview]
Message-ID: <1144969933.4935.45.camel@localhost.localdomain> (raw)
In-Reply-To: <5148225C-AE27-4365-A1C2-40C46491AF0D@watson.ibm.com>
On Wed, 2006-04-12 at 22:05 -0400, Jimi Xenidis wrote:
> A devtree compiler (dtc) generated devtree blob is "relocatable" and
> so does not contain a reserved_map entry for the blob itself.
> This means that if passed to Linux, Linux will not get lmb_reserve()
> the blob and it could be over.
> The following patch will explicitly reserve the "blob" as it was
> given to us and stops prom_init.c from creating a reserved mapping
> for the blob.
>
> NOTE: that the dtc must also not generate the blob reservation
> entry. Should we try to detect this redundant entry? Should we bump
> the DT version number?
We should make lmb_reserve() of redudant/overlapping entries become
harmless I think. We need to be backward compatible with earlier blobs
that do contain themselves in the reserve map
Ben.
next prev parent reply other threads:[~2006-04-13 23:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 2:05 [patch][rfc]flattened device tree: Passing a dtb (blob) to Linux Jimi Xenidis
2006-04-13 2:15 ` Jimi Xenidis
2006-04-13 5:36 ` Michael Neuling
2006-04-13 10:37 ` Jimi Xenidis
2006-04-13 11:07 ` Michael Ellerman
2006-04-13 13:19 ` Jimi Xenidis
2006-04-13 14:34 ` Michael Ellerman
2006-04-18 16:48 ` Jon Loeliger
2006-04-18 18:04 ` Michael Ellerman
2006-04-18 18:42 ` Jimi Xenidis
2006-04-20 15:42 ` Jon Loeliger
2006-04-20 20:20 ` Mark A. Greer
2006-04-13 23:12 ` Benjamin Herrenschmidt [this message]
2006-04-14 12:45 ` Jimi Xenidis
2006-04-14 16:19 ` Michael Ellerman
2006-05-18 22:03 ` [PATCH] powerpc: Auto reserve of device tree blob Michael Neuling
2006-05-22 16:25 ` Jon Loeliger
2006-05-23 15:04 ` Jon Loeliger
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=1144969933.4935.45.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jimix@watson.ibm.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 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).