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: Thu, 24 May 2007 01:05:25 +0200 [thread overview]
Message-ID: <15e29856db235bcba4228266653c5982@kernel.crashing.org> (raw)
In-Reply-To: <1179937253.11247.44.camel@pterry-fc6.micromemory.com>
>> 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).
> Ooops, I just posted a question to you before I saw this pop up sorry?
No problem.
> But when you say "firmware" do you mean u-boot or your kernel loading
> code or do you mean some aspect of the hardware, eg, its EEPROM program
> which can vary from hardware to hardware instantiation?
Any of those. Anything before the kernel takes control.
> If you mean u-boot I'm confused (so whats new?). AFAIK u-boot can't
> probe and set this up
Maybe it should.
> and even if it did, linux in the arch's I'm
> familiar with sets everything up anew regardless of what the boot
> loader
> did.
...and maybe that needs changing.
If it's a platform thing, it's the platform firmware code
that should configure it (and then it belongs in the device
tree). If reasonably the kernel should configure it later,
_it_ should do it (and then there shouldn't be a device tree
property).
I have no clue which it is.
Segher
next prev parent reply other threads:[~2007-05-23 23: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
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 [this message]
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=15e29856db235bcba4228266653c5982@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 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.