From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Cc: devicetree-discuss
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Subject: Re: having a keyword to specify the boot cpu like memreserve?
Date: Wed, 12 Nov 2008 09:37:11 +1100 [thread overview]
Message-ID: <20081111223711.GA16405@yookeroo.seuss> (raw)
In-Reply-To: <9103EB04-3F34-4490-856F-B30B307B4B1F-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
On Tue, Nov 11, 2008 at 10:05:13AM -0600, Kumar Gala wrote:
> Does anyone have strong feelings about having something like:
>
> /dts-v1/;
>
> /boot-cpu/ 1;
>
> As a way to specify the boot cpu w/o doing dtc -b. (I would assume -b
> would override the value in the .dts)
I've thought about implementing exactly this before. The other option
is to somehow mark the actual boot CPU node, and have dtc pick that up
and set the boot cpu appropriately.
But there's no reason we can't support both options in the long run
(with an appropriate precedence order / error on conflicts). And this
way is simpler to implement, so lets do it.
--
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
prev parent reply other threads:[~2008-11-11 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 16:05 having a keyword to specify the boot cpu like memreserve? Kumar Gala
[not found] ` <9103EB04-3F34-4490-856F-B30B307B4B1F-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2008-11-11 22:37 ` 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=20081111223711.GA16405@yookeroo.seuss \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.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