From: David Gibson <david@gibson.dropbear.id.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: scottwood@freescale.com, linuxppc-dev@ozlabs.org
Subject: Re: [RFC][POWERPC] bootwrapper: Add a firmware-independent simpleboot target.
Date: Fri, 8 Feb 2008 22:02:19 +1100 [thread overview]
Message-ID: <20080208110219.GC27955@localhost.localdomain> (raw)
In-Reply-To: <20080202065517.12920.20235.stgit@trillian.secretlab.ca>
On Fri, Feb 01, 2008 at 11:55:42PM -0700, Grant Likely wrote:
> From: Grant Likely <grant.likely@secretlab.ca>
[snip]
> +void platform_init(unsigned long r3, unsigned long r4, unsigned long r5,
> + unsigned long r6, unsigned long r7)
> +{
> + const u32 *na, *ns, *reg, *timebase;
> + u64 memsize64;
> + int node, size, i;
> +
> + /* Allocate initial heap for probing the tree */
> + simple_alloc_init(initial_heap, sizeof(initial_heap), 32, 64);
> +
> + /* Make sure FDT blob is sane */
> + if (fdt_check_header(_dtb_start) != 0)
> + fatal("Invalid device tree blob\n");
I think most of these fatal()s are pretty pointless. This is
platform_init(), so the console won't even have been initialized to
actually print any of the messages. Precisely because this is
simpleboot, in which every bit of information the wrapper has comes
from teh device tree, if the provided blob is so bad as to fail these
basic tests, we're totally stuffed anyway. It'll take a hardware
debugger to track down, and I don't think the fatal()s will actually
help much at that point.
--
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/~dgibson
next prev parent reply other threads:[~2008-02-08 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 6:55 [RFC][POWERPC] bootwrapper: Add a firmware-independent simpleboot target Grant Likely
2008-02-02 6:59 ` Grant Likely
2008-02-08 11:02 ` David Gibson [this message]
2008-02-08 14:07 ` Grant Likely
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=20080208110219.GC27955@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).