On Monday, May 21, 2012, Richard Purdie wrote: > On Sun, 2012-05-20 at 20:35 -0700, Khem Raj wrote: > > This patchset adds required bits into metadata for having > > mips64/n64 support. I have tested the core-image-sato and > core-image-minimal > > builds and boots on qemumips64 and runs gcc regression testsuite. > > It needs linux-yocto-dev kernel for now which can be obtained from > > poky-extra repo. Additionally systemd-image on angstrom-next builds and > boots > > fine on qemumips64 as well. > > > > Additionally it also adds bits to have SH4 root file systems to be > > able to built and again core-image-sato builds for sh4 however qemu > > machine support is not yet done but root file sytem boots fine on > > real hardware. > > > > The images are tested on both eglibc and uclibc. > > > > Any help in providing feedback or testing these patches is welcome. > > > > I have tested them enough for over a month now. > > > > The following changes since commit > 326563d5a897ae2dba7cfd8d73579d3d979d72c8: > > > > sstate.bbclass: Make sure we don't have an empty fixmepath file > (2012-05-18 15:24:45 +0100) > > > > are available in the git repository at: > > git://git.openembedded.org/openembedded-core-contrib kraj/mips64 > > > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/mips64 > > > > Khem Raj (14): > > insane.bbclass: Add mips64{el} to known machines > > site: Add mips64 eglibc and uclibc site files > > gcc-4.6, gcc-4.7: Add support for building mips64 cross compiler > > binutils: Default to n64 when configured for mips64 > > kernel-arch.bbclass: Map mips64{el} to mips KARCH > > eglibc-2.15: Support mips64 > > libc-package: Add sh4 and mips64 to arch options > > runqemu: Add qemush4 and qemumips64 knowledge > > netbase: Add interface files for qemumips64 and qemush4 > > site/sh-common: Add missing caches variables to build glib-2.32 > > xserver-xorg: Fix build for mips64 > > tune-mips64.inc: Add new tune file for mips64 big-endian > > qemumips64.conf: Add machine configuration for mips64(eb) > > qemush4.conf: Add machine configuration for qemush4 > > > We need to figure out what it means to add new qemu machines like this > to OE-Core. I'm not against it however I can't offer the Yocto Project's > resources to test them at this point as we're haven't budgeted for it.
Yes absolutely, in another version Actually I have these machines in a separate later Called meta-qemuextra may be such a layer would make sense ? > > The above patches make sense regardless so I've merged them except the > final two machine files. I'd like to hold off adding those until the > system builds and runs with our default kernel and qemu recipes. > Hopefully this lets you develop without having a huge queue of patches. > > In the meantime we need to figure out the resource concern for testing. > Is there a commercial interest in these new machines from anyone who > could perhaps help with the resource issue? > > Cheers, > > Richard > > > > > _______________________________________________ > Openembedded-core mailing list > [email protected] <javascript:;> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
