From: Phil Yang <Phil.Yang@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Gavin Hu <Gavin.Hu@arm.com>, Joyce Kong <Joyce.Kong@arm.com>,
nd <nd@arm.com>, "stable@dpdk.org" <stable@dpdk.org>,
Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 2/2] doc: add aarch32 build guidance
Date: Mon, 25 May 2020 03:20:28 +0000 [thread overview]
Message-ID: <VE1PR08MB4640F2D40A1F60A009BFEBC4E9B30@VE1PR08MB4640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <4358338.8uJDUzQGum@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday, May 25, 2020 5:21 AM
> To: Phil Yang <Phil.Yang@arm.com>
> Cc: dev@dpdk.org; david.marchand@redhat.com; jerinj@marvell.com;
> Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; Gavin Hu
> <Gavin.Hu@arm.com>; Joyce Kong <Joyce.Kong@arm.com>; nd
> <nd@arm.com>; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 2/2] doc: add aarch32 build guidance
>
> 11/11/2019 11:34, Phil Yang:
> > Add a guidance for aarch64 natively build 32-bit aarch32 DPDK.
> >
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Phil Yang <phil.yang@arm.com>
> > Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> > Tested-by: Joyce Kong <joyce.kong@arm.com>
> >
> > ---
> > .../linux_gsg/cross_build_dpdk_for_arm64.rst | 36
> ++++++++++++++++++----
> > 1 file changed, 30 insertions(+), 6 deletions(-)
>
> What is the status of this patch?
> The patch 1/2 was rejected.
> There are new works around aarch32.
> Is it still relevant?
Thank you for your kindly reminder.
Yes. It is relevant.
This document is intended to guide the user to cross-compile aarch32 DPDK.
Usually the cross-compile host is x86, but cross-compiling on aarch64 is convenient as well, but not everyone knows how to do it.
So it is helpful to provide relevant reference documents.
Thanks,
Phil
next prev parent reply other threads:[~2020-05-25 3:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 10:34 [dpdk-stable] [PATCH 1/2] mk: fix unsupported flag error on armhf architercture Phil Yang
2019-11-11 10:34 ` [dpdk-stable] [PATCH 2/2] doc: add aarch32 build guidance Phil Yang
2020-05-24 21:21 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2020-05-25 3:20 ` Phil Yang [this message]
2020-05-27 8:28 ` Ruifeng Wang
2020-07-02 5:37 ` Phil Yang
2020-07-02 8:01 ` Jerin Jacob
2019-11-11 10:47 ` [dpdk-stable] [dpdk-dev] [PATCH 1/2] mk: fix unsupported flag error on armhf architercture Bruce Richardson
2019-11-12 5:25 ` Phil Yang (Arm Technology China)
2019-11-12 6:03 ` Thomas Monjalon
2019-11-12 6:40 ` Phil Yang (Arm Technology China)
2019-11-26 17:01 ` Thomas Monjalon
2019-11-27 8:09 ` Phil Yang (Arm Technology China)
2019-11-27 9:29 ` Bruce Richardson
2019-11-27 10:00 ` Phil Yang (Arm Technology China)
2019-11-27 10:32 ` Thomas Monjalon
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=VE1PR08MB4640F2D40A1F60A009BFEBC4E9B30@VE1PR08MB4640.eurprd08.prod.outlook.com \
--to=phil.yang@arm.com \
--cc=Gavin.Hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Joyce.Kong@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).