On Sat, Dec 07, 2013 at 03:52:12PM +0000, Peter Robinson wrote: > On Sat, Dec 7, 2013 at 3:30 PM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote: > > On Sun, Oct 06, 2013 at 10:06:59AM +0100, Peter Robinson wrote: > >> I would like to support the various ODROID (and I think there's over a > >> dozen of them) but at the moment we don't support any of the Exynos > >> platforms well at the moment and upstream they still haven't managed > >> to land even the basic Multi Platforms support for that kernel which > >> pretty much kills us dead to support it well. I believe Linaro have > >> the action item to land to MP support and I've been told since around > >> 3.7 that it'll be "next cycle" but it never seems to make it. Once MP > >> support lands we'll start to look at it closer. > > > > Sorry to ask what may be obvious, but "Multi Platforms support" > > means device tree support? > > No, it means booting a single kernel on multiple SoCs. Basically going > back to prior to 3.7 we had to have a different kernel for each SoC > (tegra/imx/highbank/omap/versatile) and now we have a single kernel > for pretty much everything. DT tends to be one of the things that come > with that but it's not necessary or dependent. OK, device tree describes the layout of the hardware. What other sorts of differences between SoCs need to be considered? (I thought that ARM instruction sets were compatible within ARM versions?) The reason for asking all this is I'm trying to understand what's going on with the hardkernel ODROID-XU Linux tree. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
