From: Thomas Monjalon <thomas@monjalon.net>
To: oulijun <oulijun@huawei.com>
Cc: ferruh.yigit@intel.com, dev@dpdk.org, linuxarm@openeuler.org,
juraj.linkes@pantheon.tech, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] config/arm: fix Hisilicon kunpeng920 SoC build
Date: Wed, 24 Feb 2021 11:24:27 +0100 [thread overview]
Message-ID: <5309744.5Ik2CEZAj8@thomas> (raw)
In-Reply-To: <df76989d-5659-f152-58e1-3588e347b6d5@huawei.com>
24/02/2021 10:17, oulijun:
>
> 在 2021/2/24 15:41, Thomas Monjalon 写道:
> > 24/02/2021 02:34, oulijun:
> >>
> >> 在 2021/2/10 17:41, Thomas Monjalon 写道:
> >>> 03/02/2021 13:46, Lijun Ou:
> >>>> From: Chengchang Tang <tangchengchang@huawei.com>
> >>>>
> >>>> Because of the '9ca2f16' have merged, the current hns3
> >>>> pmd driver can not be directly complied on the kunpeng920
> >>>> server board. Therefore, we need to fix the meson build.
> >>>> Besides, add kunpeng 920 SoC meson cross compile target.
> >>>>
> >>>> Fixes: 9ca2f16faa7f ("config/arm: isolate generic build")
> >>>
> >>> Why do you think this patch is fixing the one above?
> >>> It looks just a new config, not a fix. Am I missing something?
> >>>
> >> I'm sorry to see you so late. In the meantime, we are celebrating the
> >> Spring Festival. This patch fixes the problem. If the patch is not
> >> added, the latest version cannot be directly compiled on the Kunpeng 930
> >> server board.In addition, the cross compilation configuration file is added.
> >
> > Please can you explain what was removed which breaks your compilation?
> >
> I understand that implementation_id is identified in 9ca2f16. If the
> configuration file does not contain implementation_id, it will be
> displayed as unsupported.
>
> The error as follows:
> config/arm/meson.build:227:2: ERROR: Problem encountered: Unsupported
> Arm implementer: 0x48. Please add support for it or use the generic
> (-Dmachine=generic) build.
>
> Besides, we use the -Dmachine=generic, the bug is not resolved.
> the cmd as:
> meson build or meson -Dmachine=generic build
What is the result of a generic build?
next prev parent reply other threads:[~2021-02-24 10:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 12:46 [dpdk-dev] [PATCH 0/2] meson build fixes for hns3 Lijun Ou
2021-02-03 12:46 ` [dpdk-dev] [PATCH 1/2] config/arm: fix Hisilicon kunpeng920 SoC build Lijun Ou
2021-02-10 9:41 ` Thomas Monjalon
2021-02-24 1:34 ` oulijun
2021-02-24 7:41 ` Thomas Monjalon
2021-02-24 9:17 ` oulijun
2021-02-24 10:24 ` Thomas Monjalon [this message]
2021-02-24 11:55 ` Juraj Linkeš
2021-02-24 12:09 ` Thomas Monjalon
2021-03-01 10:46 ` Juraj Linkeš
2021-03-05 1:36 ` oulijun
2021-03-22 1:01 ` Min Hu (Connor)
2021-02-03 12:46 ` [dpdk-dev] [PATCH 2/2] config/arm: fix Hisilicon kunpeng930 Soc build Lijun Ou
2021-03-05 1:38 ` [dpdk-dev] [PATCH 0/2] meson build fixes for hns3 oulijun
2021-03-10 1:35 ` [dpdk-dev] [PATCH V2 0/4] add Hisilicon kunpeng CPU support Lijun Ou
2021-03-10 1:35 ` [dpdk-dev] [PATCH V2 1/4] config/arm: add Hisilicon kunpeng920 implementer Lijun Ou
2021-03-20 2:27 ` Min Hu (Connor)
2021-03-23 8:07 ` Ruifeng Wang
2021-03-23 13:51 ` oulijun
2021-03-23 15:40 ` Ruifeng Wang
2021-03-25 7:21 ` oulijun
2021-03-25 7:45 ` Ruifeng Wang
2021-03-25 7:56 ` oulijun
2021-03-25 8:10 ` Ruifeng Wang
2021-03-26 12:40 ` Jerin Jacob
2021-03-10 1:35 ` [dpdk-dev] [PATCH V2 2/4] config/arm: add Hisilicon kunpeng930 implementer Lijun Ou
2021-03-26 12:42 ` Jerin Jacob
2021-03-10 1:35 ` [dpdk-dev] [PATCH V2 3/4] config/arm: add kunpeng920 meson cross compile target Lijun Ou
2021-03-25 7:48 ` Ruifeng Wang
2021-03-26 12:45 ` Jerin Jacob
2021-03-10 1:35 ` [dpdk-dev] [PATCH V2 4/4] config/arm: add kunpeng930 " Lijun Ou
2021-03-25 7:49 ` Ruifeng Wang
2021-03-26 12:46 ` Jerin Jacob
2021-03-27 1:27 ` [dpdk-dev] [PATCH V3 0/3] add Hisilicon kunpeng CPU support Lijun Ou
2021-03-27 1:27 ` [dpdk-dev] [PATCH V3 1/3] config/arm: add Hisilicon kunpeng implementer Lijun Ou
2021-03-27 1:27 ` [dpdk-dev] [PATCH V3 2/3] config/arm: add kunpeng920 cross target Lijun Ou
2021-03-27 1:27 ` [dpdk-dev] [PATCH V3 3/3] config/arm: add kunpeng930 " Lijun Ou
2021-04-16 9:57 ` [dpdk-dev] [PATCH V4 0/3] add Hisilicon kunpeng CPU support Lijun Ou
2021-04-16 9:57 ` [dpdk-dev] [PATCH V4 1/3] config/arm: add Hisilicon kunpeng implementer Lijun Ou
2021-04-16 9:57 ` [dpdk-dev] [PATCH V4 2/3] config/arm: add kunpeng920 cross target Lijun Ou
2021-04-16 9:57 ` [dpdk-dev] [PATCH V4 3/3] config/arm: add kunpeng930 " Lijun Ou
2021-04-19 8:10 ` [dpdk-dev] [PATCH V4 0/3] add Hisilicon kunpeng CPU support Thomas Monjalon
[not found] ` <6032863.io6GlxzLMq@thomas>
[not found] ` <f0e55cbc-3b61-8858-a5e7-aeee9dc613c2@huawei.com>
[not found] ` <6796692.TXxtQ3U2Ta@thomas>
2021-03-25 13:26 ` [dpdk-dev] [Linuxarm] [PATCH V2 0/4] " oulijun
2021-03-25 14:40 ` Thomas Monjalon
2021-03-26 0:41 ` oulijun
2021-04-05 19:50 ` Honnappa Nagarahalli
2021-04-06 1:00 ` oulijun
2021-04-07 2:19 ` Honnappa Nagarahalli
2021-04-08 3:30 ` oulijun
2021-04-08 8:01 ` Thomas Monjalon
[not found] <mailman.4282.1614163031.25471.dev@dpdk.org>
2021-02-24 11:02 ` [dpdk-dev] [PATCH 1/2] config/arm: fix Hisilicon kunpeng920 SoC build Thierry Herbelot
2021-02-24 11:44 ` Juraj Linkeš
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=5309744.5Ik2CEZAj8@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=juraj.linkes@pantheon.tech \
--cc=linuxarm@openeuler.org \
--cc=oulijun@huawei.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;
as well as URLs for NNTP newsgroup(s).