Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 00/14] mips64 support and sh4 support
Date: Mon, 21 May 2012 09:21:41 +0100	[thread overview]
Message-ID: <1337588501.11345.605.camel@ted> (raw)
In-Reply-To: <cover.1337570904.git.raj.khem@gmail.com>

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.

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






  parent reply	other threads:[~2012-05-21  8:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21  3:35 [RFC][PATCH 00/14] mips64 support and sh4 support Khem Raj
2012-05-21  3:35 ` [PATCH 01/14] insane.bbclass: Add mips64{el} to known machines Khem Raj
2012-05-21  3:35 ` [PATCH 02/14] site: Add mips64 eglibc and uclibc site files Khem Raj
2012-05-21  3:35 ` [PATCH 03/14] gcc-4.6, gcc-4.7: Add support for building mips64 cross compiler Khem Raj
2012-05-21  3:35 ` [PATCH 04/14] binutils: Default to n64 when configured for mips64 Khem Raj
2012-05-21  3:35 ` [PATCH 05/14] kernel-arch.bbclass: Map mips64{el} to mips KARCH Khem Raj
2012-05-21  3:35 ` [PATCH 06/14] eglibc-2.15: Support mips64 Khem Raj
2012-05-21  3:35 ` [PATCH 07/14] libc-package: Add sh4 and mips64 to arch options Khem Raj
2012-05-21  3:35 ` [PATCH 08/14] runqemu: Add qemush4 and qemumips64 knowledge Khem Raj
2012-05-21  3:35 ` [PATCH 09/14] netbase: Add interface files for qemumips64 and qemush4 Khem Raj
2012-05-21  3:35 ` [PATCH 10/14] site/sh-common: Add missing caches variables to build glib-2.32 Khem Raj
2012-05-21  3:35 ` [PATCH 11/14] xserver-xorg: Fix build for mips64 Khem Raj
2012-05-21  3:35 ` [PATCH 12/14] tune-mips64.inc: Add new tune file for mips64 big-endian Khem Raj
2012-05-21  3:35 ` [PATCH 13/14] qemumips64.conf: Add machine configuration for mips64(eb) Khem Raj
2012-05-21  3:35 ` [PATCH 14/14] qemush4.conf: Add machine configuration for qemush4 Khem Raj
2012-05-21  8:21 ` Richard Purdie [this message]
2012-05-21 14:36   ` [RFC][PATCH 00/14] mips64 support and sh4 support Khem Raj
2012-05-21 15:51   ` Mark Hatle
2012-05-21 12:43 ` Bruce Ashfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1337588501.11345.605.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox