It is not necessarily the processors PIR register value, nor does
it have any other meaning.
You can set the PIR to whatever you want, it's R/W.
It doesn't have to be. Book3 2.02 says:
"Read access to the PIR is privileged; write access, if provided, is
described in the Book IV, PowerPC Imple
On Sat, Aug 12, 2006 at 08:29:49PM +0200, Segher Boessenkool wrote:
> >It is not necessarily the processors PIR register value, nor does
> >it have any other meaning.
>
> You can set the PIR to whatever you want, it's R/W.
It doesn't have to be. Book3 2.02 says:
"Read access to the PIR is pri
Question to all:
The "cpuid" from firmware (OF "reg" property) is significant only
to uniquely identify the interrupt line that FW assigned to it
(usually for IPIs).
Not firmware in most cases; it's "hardcoded" in the hardware.
It is not necessarily the processors PIR register value, nor do
On Aug 11, 2006, at 10:26 PM, Amos Waterland wrote:
This patch gets things to the point that each secondary processor can
call the same C routine that the primary processor did
I would like the initial CPU enumeration to be simpler, like it was
in the last patch:
- one int to communicate
