From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id EDE7DA034F; Wed, 24 Feb 2021 11:24:35 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 82CBF406B4; Wed, 24 Feb 2021 11:24:35 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 6F9874069B for ; Wed, 24 Feb 2021 11:24:34 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EE87A5C009D; Wed, 24 Feb 2021 05:24:31 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 24 Feb 2021 05:24:31 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm3; bh= DAyrHFXvhPYIuBYcZWZCnxE4GHZ7T9Zz882yeYi64AU=; b=QxjCFliGk70OXIvE pa0TMYVyt1hT4hXvbRdUsy1ch8Q+FPrEtpCS6yC/guDUWvvRA61ppCMWM7UrcEL/ y06KiO6kymZaqHG88LhUz5EMXM2zN70XU5hpIZgxmUGK6nAjXsdxV6UNagRG9ftW nv/Qr2PEKsYI1FFPp0A22XiNdcWcWokL5+p/pJfvJnotyPwSCpDiCEODpOtq2iLi ph00/gCEuCSwumPa2H4TPiPzI34OBhu8j994gbj8qTdfp8lcLd2Wokk6LAuHEHJM 44iVFck5jzJWl8IisYBlCbKr1HMY4bws1i8rlUMXZLLDrRc3YuxfbzrgXV3NLKaA x7l18w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=DAyrHFXvhPYIuBYcZWZCnxE4GHZ7T9Zz882yeYi64 AU=; b=GXRGNd23ykgws4iLnxqsao28OlvpsTKjw3TdHV6mHgumbYgIKasUOTUfd +eSOX9yP5EFWhhem8W7vHldzUcxqOi8CvsboX6XWPkv5pcC+e/bgQ4qY6XiivjtT reoxk1XmNfRmicEDOhtg1ALHFZIumMy6xatNSKnHipZ1jl7zDwgdDA+IkugBNWY3 ViAn9EjmAN82gtSzdO52RSH1wcWq1zP9Dwa9sHcjzX8TuRL9NtUSFnIP0wILCV5c ujQfMzreM+RLVyfAPgyLD+wgF5oE0TF47DI+CXMOBxinuz9NyUfe+pK0fal6rY8d l/iw5mKQswV4NjLJrIlfAAG1CkdKw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeejgddugecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtqhertd dttdejnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepkeethedtieevhfeigeejle egudefjeehkeekteeuveeiuedvveeutdejveehveetnecukfhppeejjedrudefgedrvddt fedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 35866240065; Wed, 24 Feb 2021 05:24:30 -0500 (EST) From: Thomas Monjalon To: oulijun Cc: ferruh.yigit@intel.com, dev@dpdk.org, linuxarm@openeuler.org, juraj.linkes@pantheon.tech, bruce.richardson@intel.com Date: Wed, 24 Feb 2021 11:24:27 +0100 Message-ID: <5309744.5Ik2CEZAj8@thomas> In-Reply-To: References: <1612356396-21309-1-git-send-email-oulijun@huawei.com> <5435054.rFV2aVPxyo@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH 1/2] config/arm: fix Hisilicon kunpeng920 SoC build X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 24/02/2021 10:17, oulijun: >=20 > =E5=9C=A8 2021/2/24 15:41, Thomas Monjalon =E5=86=99=E9=81=93: > > 24/02/2021 02:34, oulijun: > >> > >> =E5=9C=A8 2021/2/10 17:41, Thomas Monjalon =E5=86=99=E9=81=93: > >>> 03/02/2021 13:46, Lijun Ou: > >>>> From: Chengchang Tang > >>>> > >>>> 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 9= 30 > >> server board.In addition, the cross compilation configuration file is = added. > >=20 > > Please can you explain what was removed which breaks your compilation? > >=20 > I understand that implementation_id is identified in 9ca2f16. If the=20 > configuration file does not contain implementation_id, it will be=20 > displayed as unsupported. >=20 > The error as follows: > config/arm/meson.build:227:2: ERROR: Problem encountered: Unsupported=20 > Arm implementer: 0x48. Please add support for it or use the generic=20 > (-Dmachine=3Dgeneric) build. >=20 > Besides, we use the -Dmachine=3Dgeneric, the bug is not resolved. > the cmd as: > meson build or meson -Dmachine=3Dgeneric build What is the result of a generic build?