From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 00/14] mips64 support and sh4 support
Date: Mon, 21 May 2012 10:51:21 -0500 [thread overview]
Message-ID: <4FBA6479.1040105@windriver.com> (raw)
In-Reply-To: <1337588501.11345.605.camel@ted>
On 5/21/12 3:21 AM, 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.
> 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?
From a commercial interest standpoint, I don't know if there is any with SH4.
For the company I work for, SH has been so minor that we likely wouldn't
consider it significant enough to spend effort on.
However, MIPS64 is completely different. There are numerous MIPS64 processors
and such, and I strongly advocate OE (and Yocto Project) support for MIPS64.
One thing to note, it should be possible to use the MIPS64 QEMU to replace the
"qemumips" configuration already in OE-core. Then the qemumips64 can be used to
validation, mips (o32), mips64 (n64) and eventually mips64 (n32) binaries once
they are available. This would also be a good target to validation complex
multilib sets on.
--Mark
> Cheers,
>
> Richard
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-05-21 16:01 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 ` [RFC][PATCH 00/14] mips64 support and sh4 support Richard Purdie
2012-05-21 14:36 ` Khem Raj
2012-05-21 15:51 ` Mark Hatle [this message]
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=4FBA6479.1040105@windriver.com \
--to=mark.hatle@windriver.com \
--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