DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Ruoshan Shi <ruoshan.shi@nxp.com>
Cc: "X.f. Ren" <xiaofeng.ren@nxp.com>,
	ci@dpdk.org,  Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: [dpdk-ci] Upgraded DTS Version for NXP
Date: Thu, 17 Sep 2020 17:00:06 -0400	[thread overview]
Message-ID: <CAOeXdvYfAzdgK=Gi-vqAoa+7Bu8-4FSv7AgLLKG2DY=sMuA7XQ@mail.gmail.com> (raw)

Hi Ruoshan,

Since DPDK has discontinued make support for compiling, a DTS upgrade
is needed for performance testing to continue on all systems.

I am attempting to upgrade DTS on the NXP machine, but it seems that
it is a fork of DTS that is from NXP's bitbucket server.
Is it possible to pull from the upstream DPDK DTS repository and use
that instead?

I also installed meson and ninja on the machine which is needed for
the new version, but I am having trouble building.
It uses these commands to build (172.18.0.202 in /root/dpdk):
1. CC=gcc meson --werror -Denable_kmods=True -Dlibdir=lib
--default-library=static arm64-dpaa-linuxapp-gcc
2. ninja -C arm64-dpaa-linuxapp-gcc -j 8

Could you help me look into this?

Thanks,
Brandon

-- 
Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

             reply	other threads:[~2020-09-17 21:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 21:00 Brandon Lo [this message]
2020-09-18 11:52 ` Hemant Agrawal
2020-09-18 16:55   ` Brandon Lo
2020-09-22  5:56     ` Juraj Linkeš
2020-09-22 14:06       ` Brandon Lo
2020-10-22 17:26         ` Brandon Lo
2020-12-03 16:53           ` Brandon Lo
2021-01-19 21:02             ` Brandon Lo

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='CAOeXdvYfAzdgK=Gi-vqAoa+7Bu8-4FSv7AgLLKG2DY=sMuA7XQ@mail.gmail.com' \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=ruoshan.shi@nxp.com \
    --cc=xiaofeng.ren@nxp.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).