From: "Ruifeng Wang (Arm Technology China)" <Ruifeng.Wang@arm.com>
To: Ferruh Yigit <ferruh.yigit@intel.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>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture based on armv8-a
Date: Mon, 27 May 2019 01:42:15 +0000 [thread overview]
Message-ID: <AM0PR08MB44185A3894C2E5FC1E3D1CE99E1D0@AM0PR08MB4418.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <300bdc0f-19d4-0c3d-cc04-0c2b69273a7b@intel.com>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Friday, May 24, 2019 21:07
> To: Ruifeng Wang (Arm Technology China) <Ruifeng.Wang@arm.com>; Liron
> Himi <lironh@marvell.com>; thomas@monjalon.net
> Cc: 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
>
> 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
>
With guide from Liron, I can build ARMADA target with MUSDK version 18.09 (after properly configured).
Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
next prev parent reply other threads:[~2019-05-27 1:42 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
2019-05-27 1:42 ` Ruifeng Wang (Arm Technology China) [this message]
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=AM0PR08MB44185A3894C2E5FC1E3D1CE99E1D0@AM0PR08MB4418.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Gavin.Hu@arm.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).