linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	Jon Loeliger <jdl@jdl.com>
Subject: Re: [PATCH] Add StorCenter DTS first draft.
Date: Thu, 19 Jul 2007 11:05:29 -0500	[thread overview]
Message-ID: <1184861129.16820.2.camel@ld0161-tx32> (raw)
In-Reply-To: <1184795678.25235.269.camel@localhost.localdomain>

On Wed, 2007-07-18 at 16:54, Benjamin Herrenschmidt wrote:

> Cache line size is used by the kernel on ppc64 for things like clearing
> memory (to get the stride between subsequent dcbz) or flushing the
> cache :-) It's also passed on to userland.
> 
> If it's absent from the device-tree, we default to the values in the
> cputable, but if you're going to put the properties in the tree, don't
> put a 0 in there. As it is, the day I make the 64 bits code common, your
> DT will break unless I special case "0".
> 
> Ben.

So, just to put this issue to rest some, I have
modified my DTS to have correct values here.
It was _easy_. ;-)

But, a followup patch should clean up _other_, existing
DTS files that have 0 there still.

jdl

  reply	other threads:[~2007-07-19 16:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 14:22 [PATCH] Add StorCenter DTS first draft Jon Loeliger
2007-07-17 14:57 ` Segher Boessenkool
2007-07-17 16:26   ` Josh Boyer
2007-07-17 16:38     ` Segher Boessenkool
2007-07-17 22:27   ` Jon Loeliger
2007-07-17 22:34     ` Scott Wood
2007-07-17 22:56       ` Jon Loeliger
2007-07-18 16:19     ` Segher Boessenkool
2007-07-18 18:27       ` Kumar Gala
2007-07-19 17:03         ` Segher Boessenkool
2007-07-18  1:39 ` Benjamin Herrenschmidt
2007-07-18 16:13   ` Segher Boessenkool
2007-07-18 21:54     ` Benjamin Herrenschmidt
2007-07-19 16:05       ` Jon Loeliger [this message]
2007-07-19 17:07       ` Segher Boessenkool
2007-07-19 21:39         ` Benjamin Herrenschmidt
2007-07-20  7:14           ` Segher Boessenkool

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=1184861129.16820.2.camel@ld0161-tx32 \
    --to=jdl@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=jdl@jdl.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).