All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: dtc: Automatically pick a sensible boot_cpuid_phys
Date: Fri, 19 Feb 2010 08:37:36 -0600	[thread overview]
Message-ID: <E1NiTz6-0000yv-PW@jdl.com> (raw)
In-Reply-To: <20100219045050.GJ29038@yookeroo>

> Currently, when in -Idts -Odtb or -Ifs -Odtb modes, dtc always
> defaults to using 0 as the value for the boot_cpuid_phys header field.
> That's correct quite often, but there are some systems where there is
> no CPU with hardware ID of 0, or where we don't want to use the CPU
> with hardware ID 0 at all (e.g. for AMP-style partitioning).  The only
> way to override this default currently, is with the -b command line
> option.
> 
> This patch improves dtc to instead base the default boot_cpuid_phys
> value on the reg property of the first listed subnode of /cpus.  This
> means that dtc will get boot_cpuid_phys correct by default in a
> greater proportion of cases (since the boot cpu is usually listed
> first, and this way at least the boot_cpuid_phys default will match
> some existing cpu node).  If the node doesn't exist or has an invalid
> 'reg' property (missing or not 4 bytes in length), then
> boot_cpuid_phys is set to 0.
> 
> Signed-off-by: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>

Applied.

jdl

      reply	other threads:[~2010-02-19 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19  4:50 dtc: Automatically pick a sensible boot_cpuid_phys David Gibson
2010-02-19 14:37 ` Jon Loeliger [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=E1NiTz6-0000yv-PW@jdl.com \
    --to=jdl-cyomk+44s/e@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@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 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.