Re: [XenPPC] XenPPC IEEE1275 binding?

2006-08-21 Thread Jimi Xenidis


On Aug 21, 2006, at 12:07 AM, Olof Johansson wrote:


On Wed, Aug 09, 2006 at 09:05:24AM -0400, Jimi Xenidis wrote:


We intend to include these in the OpenPAPR :-P


Yet another PAPR!?


hmm..
no the same one power.org blessed, the plan is to have Xen bindings  
and more :)

why is 1100+ pages to much for your disk? :-P
-JX

___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


Re: [XenPPC] XenPPC IEEE1275 binding?

2006-08-20 Thread Olof Johansson
On Wed, Aug 09, 2006 at 09:05:24AM -0400, Jimi Xenidis wrote:

 We intend to include these in the OpenPAPR :-P

Yet another PAPR!?


-Olof

___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


[XenPPC] XenPPC IEEE1275 binding?

2006-08-08 Thread Hollis Blanchard
I remember seeing some mention of it, but I don't think we currently
have an IEEE1275 binding describing the contents of the /xen node. I'm
currently doing the device tree work to fill that in, and we're going to
replace the start_info struct we're currently using, so now would be a
good time.

This is what we've got at the moment (written by Jimi):
xen {
name = xen;
start-info = 0 @START_INFO@ 0 1000;
version = Xen-3.0-unstable;
reg = 0 @DOMAIN_ID@ 0 0;
domain-name = @DOMAIN_NAME@;

console {
name = console;
interrupts = @CONSOLE_EVTCHN@ 0;
};
};

start-info is going away, which means we'll need to add more properties
to replace it... something like this:
xen {
name = xen;
version = Xen-3.0-unstable;
reg = 0 @DOMAIN_ID@ 0 0;
domain-name = @DOMAIN_NAME@;
shared = @SHARED_INFO@;
privileged;
init-domain;
console {
name = console;
interrupts = @CONSOLE_EVTCHN@ 0;
frameno = @CONSOLE_MFN@;
};
store {
name = store;
interrupts = @STORE_EVTCHN@ 0;
frameno = @STORE_MFN@;
};
};

What are all the extra 0s in there? Why do we want a reg property when
we can use separate explicitly-named properties?

If we can flesh this out a little bit in email, we can start a wiki page
with the info.

-- 
Hollis Blanchard
IBM Linux Technology Center


___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel