linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Add MPC8641 HPCN Device Tree Source file.
Date: Wed, 02 Aug 2006 14:50:17 -0500	[thread overview]
Message-ID: <1154548217.32357.27.camel@basalt.austin.ibm.com> (raw)
In-Reply-To: <1154544503.19994.42.camel@cashmere.sps.mot.com>

On Wed, 2006-08-02 at 13:48 -0500, Jon Loeliger wrote:
> 
> +               PowerPC,8641@0 {
> +                       device_type = "cpu";
> +                       reg = <0>;
> +                       d-cache-line-size = <20>;       // 32 bytes
> +                       i-cache-line-size = <20>;       // 32 bytes
> +                       d-cache-size = <8000>;          // L1, 32K
> +                       i-cache-size = <8000>;          // L1, 32K
> +                       timebase-frequency = <0>;       // 33 MHz,
> from uboot
> +                       bus-frequency = <0>;            // From uboot
> +                       clock-frequency = <0>;          // From uboot
> +                       32-bit;
> +                       linux,boot-cpu;
> +               }; 

I need to do something similar for Xen, so I was curious: I guess the
preferred way for runtime software to fill in values is by *overwriting*
bogus values inserted at compile time?

The other alternative would be for the runtime code to insert new
properties (presumably via memmove()), but overwriting definitely seems
simpler.

-Hollis

  parent reply	other threads:[~2006-08-02 20:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 18:48 [PATCH] Add MPC8641 HPCN Device Tree Source file Jon Loeliger
2006-08-02 19:24 ` Kumar Gala
2006-08-02 19:33   ` Sergei Shtylyov
2006-08-02 20:07     ` Kumar Gala
2006-08-02 19:47   ` Hollis Blanchard
2006-08-02 20:11   ` Jon Loeliger
2006-08-02 20:30     ` Kumar Gala
2006-08-02 20:36       ` Jon Loeliger
2006-08-02 20:53         ` Kumar Gala
2006-08-03 15:49           ` Sergei Shtylyov
2006-08-03 16:46             ` Kumar Gala
2006-08-02 19:50 ` Hollis Blanchard [this message]
2006-08-02 20:49   ` Mark A. Greer

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=1154548217.32357.27.camel@basalt.austin.ibm.com \
    --to=hollis@penguinppc.org \
    --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 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).