Timur Tabi wrote:
David Gibson wrote:
Indeed, indexing or writing into shared registers is exactly what
cell-index is for.
I don't care whether it's cell-index or device-id, but I need to know
which DMA controller is #0 and which one is #1, and I need to know which
channel is #0, which
On Wed, Nov 21, 2007 at 09:33:05AM -0600, Kumar Gala wrote:
On Nov 21, 2007, at 8:59 AM, Timur Tabi wrote:
+ Example:
+ [EMAIL PROTECTED] {
Shouldn't this be [EMAIL PROTECTED]
its an example that has not basis is reality :)
But it should at least be internally consistent with this:
On Nov 21, 2007, at 11:35 AM, Scott Wood wrote:
On Wed, Nov 21, 2007 at 09:33:05AM -0600, Kumar Gala wrote:
On Nov 21, 2007, at 8:59 AM, Timur Tabi wrote:
+ Example:
+ [EMAIL PROTECTED] {
Shouldn't this be [EMAIL PROTECTED]
its an example that has not basis is reality :)
But it
Kumar Gala wrote:
On Nov 21, 2007, at 11:35 AM, Scott Wood wrote:
A cell-index property would be useful here for indexing into the summary
status register.
Divide by 0x80.
:-P
Using cell-index for things like this is reasonably common, and endorsed
by current ePAPR drafts.
Scott Wood wrote:
I don't see any justification for having such a property in the parent node,
though.
The SSI needs to know which DMA controller is #0 and which one is #1.
I literally program the SSI and the GUTS registers with the DMA controller and
channels numbers. I need to know which
Kumar Gala wrote:
Shouldn't we put some text somewhere that we're calling it the Elo
controller even though that word isn't used in the reference manual?
we don't really have a place to put that. its effectively documented
right here.
I still think we need something. Otherwise, people
---
Documentation/powerpc/booting-without-of.txt | 113 ++
1 files changed, 113 insertions(+), 0 deletions(-)
diff --git a/Documentation/powerpc/booting-without-of.txt
b/Documentation/powerpc/booting-without-of.txt
index 3d959d6..161fb0d 100644
---
