From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tom Rini <trini@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/5] qemuarm: Swap for an arm7ve (A15) configuration
Date: Mon, 11 Mar 2019 08:13:21 -0700 [thread overview]
Message-ID: <3303e413e766655231584cffd06b018f63bf4e93.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190311150926.GY5026@bill-the-cat>
On Mon, 2019-03-11 at 11:09 -0400, Tom Rini wrote:
> On Mon, Mar 11, 2019 at 03:12:26AM +0000, Richard Purdie wrote:
>
> > From: Jon Mason <jdmason@kudzu.us>
> >
> > Add new QEMU BSP for a Arm Cortex-A15 system and use this as
> > qemuarm,
> > moving the old armv5te Versatile PB based machine to qemuarmv5.
> >
> > The new machine uses the QEMU virt machine type, which should be
> > faster to emulate and updates the qemuarm support to a modern
> > architecture.
> >
> > Signed-off-by: Jon Mason <jdmason@kudzu.us>
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> Should we also not set UBOOT_MACHINE here to qemu_arm_defconfig for
> the new machine? We dropped versatilepb support back in 2015
> however.
> Thanks!
For which machine, the new qemuarm or the qemuarmv5? I'm guessing you
mean the latter?
We perhaps could/should but it isn't set now so I'd suggest it be done
in a separate patch.
I would like to see u-boot being used in more builds but if we don't
actually test/use the binary, its not so useful and that would mean
further changes?
Cheers,
Richard
next prev parent reply other threads:[~2019-03-11 15:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 3:12 [PATCH 1/5] qemuarm: Swap for an arm7ve (A15) configuration Richard Purdie
2019-03-11 3:12 ` [PATCH 2/5] machine: bump preferred version to 5.0 Richard Purdie
2019-03-11 3:12 ` [PATCH 3/5] qemuarm64: Fix graphics hang with 5.0 kernel Richard Purdie
2019-03-11 3:12 ` [PATCH 4/5] linux-yocto: Fix systemtap issue on armv7 Richard Purdie
2019-03-11 3:16 ` Bruce Ashfield
2019-03-11 4:29 ` Victor Kamensky
2019-03-11 4:27 ` Khem Raj
2019-03-11 12:12 ` richard.purdie
2019-03-11 12:40 ` Bruce Ashfield
2019-03-11 3:12 ` [PATCH 5/5] meta-selftest/virgl: Exclude centos7 from the kmscube test Richard Purdie
2019-03-11 15:09 ` [PATCH 1/5] qemuarm: Swap for an arm7ve (A15) configuration Tom Rini
2019-03-11 15:13 ` Richard Purdie [this message]
2019-03-11 15:19 ` Tom Rini
2019-03-20 0:22 ` Denys Dmytriyenko
2019-03-20 0:25 ` richard.purdie
2019-03-21 20:35 ` Denys Dmytriyenko
2019-03-21 23:48 ` richard.purdie
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=3303e413e766655231584cffd06b018f63bf4e93.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=trini@konsulko.com \
/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