From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Ruifeng Wang (Arm Technology China)" <Ruifeng.Wang@arm.com>,
Liron Himi <lironh@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture based on armv8-a
Date: Fri, 24 May 2019 14:06:37 +0100 [thread overview]
Message-ID: <300bdc0f-19d4-0c3d-cc04-0c2b69273a7b@intel.com> (raw)
In-Reply-To: <AM6PR08MB4424AC8810E8B575459245999E020@AM6PR08MB4424.eurprd08.prod.outlook.com>
On 5/24/2019 2:10 AM, Ruifeng Wang (Arm Technology China) wrote:
> Hi,
>
>> -----Original Message-----
>> From: Liron Himi <lironh@marvell.com>
>> Sent: Thursday, May 23, 2019 18:51
>> To: Ruifeng Wang (Arm Technology China) <Ruifeng.Wang@arm.com>;
>> thomas@monjalon.net
>> Cc: dev@dpdk.org; nd <nd@arm.com>; Liron Himi <lironh@marvell.com>
>> Subject: RE: [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture
>> based on armv8-a
>>
>> Hi,
>>
>> This patch can only work with MUSDK newer than 18.09.
>> Do you have access to a newer version?
>
> Will newer MUSDK version available on github?
> I have no access to Marvell Extranet.
+1, in github [1] latest branch I can see is 18.09
[1]: https://github.com/MarvellEmbeddedProcessors/musdk-marvell.git
>
>>
>> Regards,
>> Liron
>>
>> -----Original Message-----
>> From: Ruifeng Wang (Arm Technology China) <Ruifeng.Wang@arm.com>
>> Sent: Thursday, May 23, 2019 13:11
>> To: Liron Himi <lironh@marvell.com>; thomas@monjalon.net
>> Cc: dev@dpdk.org; nd <nd@arm.com>
>> Subject: [EXT] RE: [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA
>> architecture based on armv8-a
>>
>> External Email
>>
>> ----------------------------------------------------------------------
>> Hi Liron,
>>
>>> -----Original Message-----
>>> From: dev <dev-bounces@dpdk.org> On Behalf Of lironh@marvell.com
>>> Sent: Saturday, May 18, 2019 05:27
>>> To: thomas@monjalon.net
>>> Cc: dev@dpdk.org; Liron Himi <lironh@marvell.com>
>>> Subject: [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture
>>> based on armv8-a
>>>
>>> From: Liron Himi <lironh@marvell.com>
>>>
>>> This patch introduces armada target to address difference in number of
>>> cores, no numa support
>>>
>>> Change-Id: Ieaabe77b165000fe1280f98105329a0e63833b92
>>> Signed-off-by: Liron Himi <lironh@marvell.com>
>>> Reviewed-by: Alan Winkowski
>>> Tested-by: Liron Himi
>>> ---
>>
>> My local compilation on MacchiatoBin failed with the target.
>> I have musdk-armada-18.09 checked out from
>> https://github.com/MarvellEmbeddedProcessors/musdk-marvell.git
>> LIBMUSDK_PATH was set before compiling.
>> Hit errors as below:
>> == Build drivers/net/mvneta
>> CC mvneta_ethdev.o
>> In file included from
>> /home/arm/dpdk/drivers/net/mvneta/mvneta_rxtx.h:10:0,
>> from
>> /home/arm/dpdk/drivers/net/mvneta/mvneta_ethdev.c:25:
>> /home/arm/dpdk/drivers/net/mvneta/mvneta_ethdev.h:24:29:
>> fatal error: drivers/mv_neta.h: No such file or directory
>> compilation terminated.
>> /home/arm/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for
>> target 'mvneta_ethdev.o' failed
>>
>> I tried to copy the files from musdk to LIBMUSDK_PATH, but still cannot
>> finish compiling.
>> CC test_ipsec.o
>> LD test
>> /home/arm/dpdk/arm64-armada-linuxapp-
>> gcc/lib/librte_pmd_mvneta.a(mvneta_ethdev.o): In function
>> `mvneta_stats_get':
>> mvneta_ethdev.c:(.text+0x1c4): undefined reference to
>> `neta_ppio_get_statistics'
>> /home/arm/dpdk/arm64-armada-linuxapp-
>> gcc/lib/librte_pmd_mvneta.a(mvneta_ethdev.o): In function
>> `mvneta_mtu_set':
>> mvneta_ethdev.c:(.text+0x368): undefined reference to
>> `neta_ppio_set_mru'
>> mvneta_ethdev.c:(.text+0x37c): undefined reference to
>> `neta_ppio_set_mtu'
>> /home/arm/dpdk/arm64-armada-linuxapp-
>> gcc/lib/librte_pmd_mvneta.a(mvneta_ethdev.o): In function
>> `mvneta_promiscuous_disable':
>> mvneta_ethdev.c:(.text+0x4e4): undefined reference to
>> `neta_ppio_get_promisc'
>> mvneta_ethdev.c:(.text+0x4f8): undefined reference to
>> `neta_ppio_set_promisc'
>> ......
>>
>> My musdk repo is updated. Is anything else needed?
>>
>> Regards,
>> /Ruifeng
next prev parent reply other threads:[~2019-05-24 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 21:27 [dpdk-dev] [PATCH 0/2] Introduces armada target lironh
2019-05-17 21:27 ` [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture based on armv8-a lironh
2019-05-22 9:11 ` Ruifeng Wang (Arm Technology China)
2019-05-22 9:12 ` Liron Himi
2019-05-23 10:11 ` Ruifeng Wang (Arm Technology China)
2019-05-23 10:51 ` Liron Himi
2019-05-24 1:10 ` Ruifeng Wang (Arm Technology China)
2019-05-24 13:06 ` Ferruh Yigit [this message]
2019-05-27 1:42 ` Ruifeng Wang (Arm Technology China)
2019-05-17 21:27 ` [dpdk-dev] [PATCH 2/2] meson: " lironh
2019-05-17 21:34 [dpdk-dev] [PATCH 0/2] Introduces armada target lironh
2019-05-17 21:34 ` [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture based on armv8-a lironh
2019-05-18 10:59 ` Jerin Jacob Kollanukkaran
2019-05-24 7:50 ` Ruifeng Wang (Arm Technology China)
2019-05-26 5:33 ` Liron Himi
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=300bdc0f-19d4-0c3d-cc04-0c2b69273a7b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Gavin.Hu@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=dev@dpdk.org \
--cc=lironh@marvell.com \
--cc=nd@arm.com \
--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).