From: Jan Viktorin <viktorin@rehivetech.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jimmy Carter <jimmycarter256@gmail.com>,
users@dpdk.org, dev@dpdk.org, jianbo.liu@linaro.org,
kosar@rehivetech.com
Subject: Re: [dpdk-users] [dpdk-maintainers] Issue->Dpdk for arm cortex-a15 compilation
Date: Tue, 16 May 2017 13:38:52 +0200 [thread overview]
Message-ID: <20170516133852.75a21642.viktorin@rehivetech.com> (raw)
In-Reply-To: <11688640.S3aN4PYXg2@xps>
On Tue, 16 May 2017 13:22:19 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 16/05/2017 12:51, Jan Viktorin:
> > DPDK does not support OpenWRT because (as far as I know) nobody from
> > the DPDK community is using it in this way. I build DPDK via Buildroot
> > but this is unsupported by the DPDK upstream.
>
> Why means "unsupported upstream"? Are we missing some patches?
I mean that DPDK does not contain anything related to Buildroot in its
repositories and it is not related to it in any way... It does not mean
whether it does or does not work.
And also, I've never finished my Builroot integration into the Buildroot
upstream.
> Should we integrate Buildroot compilation in our CI?
Well, I do it. If the support is upstreamed into the Buildroot master,
I'd say yes, It would be a good idea to include it in the DPDK CI. This
is about having somebody to do it...
Regards
Jan
--
Jan Viktorin E-mail: Viktorin@RehiveTech.com
System Architect Web: www.RehiveTech.com
RehiveTech
Brno, Czech Republic
next prev parent reply other threads:[~2017-05-16 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 10:08 [dpdk-users] " Jimmy Carter
2017-05-16 10:51 ` Jan Viktorin
2017-05-16 11:22 ` [dpdk-users] [dpdk-maintainers] " Thomas Monjalon
2017-05-16 11:38 ` Jan Viktorin [this message]
2017-05-16 11:44 ` [dpdk-users] [dpdk-dev] " Neil Horman
2017-05-16 11:51 ` Jan Viktorin
2017-05-16 19:22 ` Neil Horman
2017-05-16 11:55 ` Jimmy Carter
2017-05-16 12:28 ` Jan Viktorin
2017-05-16 13:27 ` Jimmy Carter
2017-05-16 14:00 ` Jan Viktorin
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=20170516133852.75a21642.viktorin@rehivetech.com \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=jianbo.liu@linaro.org \
--cc=jimmycarter256@gmail.com \
--cc=kosar@rehivetech.com \
--cc=thomas@monjalon.net \
--cc=users@dpdk.org \
/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).