Thread (4 messages) 4 messages, 3 authors, 2011-01-06

Re: [RFC] MPIC Bindings and Bindings for AMP Systems

flat view

From: Blanchard, Hollis <hidden>
Date: 2011-01-05 22:49:40
Also in: linuxppc-dev

On 01/05/2011 02:09 PM, Scott Wood wrote:
On Wed, 5 Jan 2011 15:58:55 -0600
Meador Inge[off-list ref]  wrote:
quoted
We need some sort of mapping between a message register and a message
register number so that the message registers can be referenced through
some sort of API (e.g. 'mpic_msgr_read(0)').  One way to do that would
be by putting an order on the registers.  Maybe there is a better way,
though ...
A message register is uniquely identified by a reference to the device
tree node, plus a 0-3 index into that node's message registers.
Really what we're talking about is software configuration, not hardware 
description. We've gone back and forth on representing this information 
in the device tree, and most recently decided against it. Outside the 
kernel, a device node reference isn't really practical.

Hollis Blanchard
Mentor Graphics, Embedded Systems Division
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help