From: Khem Raj <raj.khem@gmail.com>
To: Kang Kai <Kai.Kang@windriver.com>
Cc: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: Question about aarch64 target
Date: Thu, 28 Aug 2014 01:13:51 -0700 [thread overview]
Message-ID: <20140828081351.GJ13139@haswell> (raw)
In-Reply-To: <53FEE267.6010303@windriver.com>
On 14-08-28 16:03:51, Kang Kai wrote:
> On 2014年08月28日 15:33, Khem Raj wrote:
> >On 14-08-27 18:53:41, Kang Kai wrote:
> >>Hi Saul,
> >>
> >>I am working on Bug 6487 - Add Aarch64 qemu target. I take tune and config
> >>files from linaro then succeeds to build core-image-minimal and
> >>core-image-sato.
> >>
> >>And I have 2 question about it now:
> >>1 What should the new qemu aarch64 bsp looks like at the end? Do the files
> >>in the patch attached are enough? And what more test should we do except to
> >>build images such as core-image-sato, core-image-sato even build world?
> >>
> >may be eventually support linux-yocto, and linux-linaro both, it should
> >be tested at same level as other QEMU BSPs
> >
> >>2 There 2 aarch64 configure files from linaro. First one is little endian
> >>and it is as default, and the other one is big endian. I take the little
> >>endian one as qemuarm64.conf as linaro does. Do we need add the other one as
> >>qemuarm64_be.conf or something like that?
> >Name them same as meta-linaro please, so eventually linaro layer can
> >drop it and take up the maintenance of them in OE-Core
>
> Keep same name with linaro is convenient for merge work. But the name
> 'genericarmv8' is not coordinated with existing qemu bsps. I prefer to use
> qemuarmv8 for coordination.
Thats a valid point, I would give in.
prev parent reply other threads:[~2014-08-28 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 10:53 Question about aarch64 target Kang Kai
2014-08-27 12:58 ` Bruce Ashfield
2014-08-28 7:33 ` Khem Raj
2014-08-28 8:03 ` Kang Kai
2014-08-28 8:13 ` Khem Raj [this message]
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=20140828081351.GJ13139@haswell \
--to=raj.khem@gmail.com \
--cc=Kai.Kang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.