linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: pterry@micromemory.com
Cc: linuxppc-dev@ozlabs.org, Zhang Wei-r63237 <Wei.Zhang@freescale.com>
Subject: Re: Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D
Date: Wed, 23 May 2007 18:05:43 +0200	[thread overview]
Message-ID: <836bca7802dca173490f4d38e0c48b7a@kernel.crashing.org> (raw)
In-Reply-To: <1179934657.11247.14.camel@pterry-fc6.micromemory.com>

>> The law should really be removed.
> In my application I'm may be using a huge part of the 36-bit address
> space to address multiple remote RIO boards in a peer DMA multicomputer
> application. The default law just for maintenance messages isn't going
> to cut it.

If the firmware sets up the "law", it should put a property
in the node describing the setting.  If Linux sets up the
laws, there shouldn't be a property (since it is a policy
decision).

>>> The dbells and mboxs can be removed. The default setting in rio is 
>>> okay.
>>
>> this could possibly be useful.

Same issue.  Even if the firmware uses a default setting,
it should still put it in the device tree _iff_ it is the
firmware's decision (and not the kernel's).


Segher

  reply	other threads:[~2007-05-23 16:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 19:38 Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Phil Terry
2007-05-22 20:08 ` Segher Boessenkool
2007-05-22 20:09 ` Timur Tabi
2007-05-22 23:05 ` Arnd Bergmann
2007-05-24  6:48   ` Porting RapidIO from ppc arch to powerpc arch in support ofMPC8641D Zhang Wei-r63237
2007-05-24  9:19     ` Arnd Bergmann
2007-05-24  9:44       ` Zhang Wei-r63237
2007-05-24 11:27         ` Arnd Bergmann
2007-05-23 13:26 ` Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Zhang Wei-r63237
2007-05-23 13:32   ` Mark A. Greer
2007-05-23 14:03     ` Zhang Wei-r63237
2007-05-23 15:42       ` Phil Terry
2007-05-23 15:53       ` Mark A. Greer
2007-05-23 15:54       ` Phil Terry
2007-05-23 14:21   ` Kumar Gala
2007-05-23 15:37     ` Phil Terry
2007-05-23 16:05       ` Segher Boessenkool [this message]
2007-05-23 16:20         ` Phil Terry
2007-05-23 16:20           ` Kumar Gala
2007-05-23 16:43             ` Phil Terry
2007-05-23 23:17               ` Segher Boessenkool
2007-05-23 23:05           ` Segher Boessenkool
2007-05-24  7:31       ` Porting RapidIO from ppc arch to powerpc arch in support ofMPC8641D Zhang Wei-r63237
2007-05-23 16:00     ` Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Segher Boessenkool
2007-05-23 16:13       ` Phil Terry
2007-05-24  0:52     ` David Gibson

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=836bca7802dca173490f4d38e0c48b7a@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Wei.Zhang@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=pterry@micromemory.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).