On Thu, 2014-01-30 at 18:28 +0100, Arnd Bergmann wrote: > On Thursday 30 January 2014, Ian Campbell wrote: > > mach-virt has existed for a while but it is not written down what it actually > > consists of. Although it seems a bit unusual to document a binding for an > > entire platform since mach-virt is entirely virtual it is helpful to have > > something to refer to in the absence of a single concrete implementation. > > > > I've done my best to capture the requirements based on the git log and my > > memory/understanding. > > > > While here remove the xenvm dts example, the Xen tools will now build a > > suitable mach-virt compatible dts when launching the guest. > > It might be worth noting in the changeset comment that the 'compatible' > string is actually no longer needed on newer kernels: All the members > of the machine descriptor are now the defaults (we should remove the > virt_init() function as well), and the fallback machine descriptor should > work just fine if any other string gets passed. So Marc's plan has actually happened. Neat. In that case is there even any point in listing explicit compatiblity strings (except perhaps as a historical note) -- I can just say that this is the fallback/default machine? I'll leave the virt_init change to a separate patch if that's ok. Ian. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
