From: "Wiles, Keith" <keith.wiles@intel.com>
To: Oscar Pap <oscarpap94@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Create new driver error
Date: Thu, 31 Jan 2019 17:00:30 +0000 [thread overview]
Message-ID: <B7B6CDB5-8B08-4D71-AC7E-E4FAD79956BA@intel.com> (raw)
In-Reply-To: <CAPwfg=aGdy9WpzuwFg4ghRZ7DvCc-yTn20A+uu6jJPXN3GRtmA@mail.gmail.com>
Sent from my iPhone
> On Jan 31, 2019, at 2:44 AM, Oscar Pap <oscarpap94@gmail.com> wrote:
>
> Hello!
>
> I´m trying to create a new driver called "baseband_ldpc" for baseband but I
> get this error:
>
> EAL: failed to parse device "baseband_ldpc"
> EAL: Unable to parse device 'baseband_ldpc'
>
>
> I created the driver in the /dpdk/drivers/baseband/ldpc folder.
> The file is called ldpc.c
> I created a copy of the Makefile from the other drivers but changed these
> lines:
>
> LIB =librte_pmd_bbdev_ldpc.a
> ...
> EXPORT_MAP :=rte_pmd_bbdev_ldpc_version.map
> ...
> SRCS-$(CONFIG_RTELIBRTE_PMD_BBDEV_LDPC) += ldpc.c
>
>
> I added this line in the Makefile in the folder /dpdk/drivers/baseband
> DIRS-$(CONFIG_RTE_LIBRTE_PMD_BBDEV_LDPC) += ldpc
> DEPDIRS-ldpc = $(core-libs)
>
> I also added these lines in the common_base file:
> CONFIG_RTE_LIBRTE_PMD_BBDEV_LDPC=y
>
> My guess is that the error has something to do with vdev and that my
> baseband_ldpc doesnt get registered as a valid vdev.
>
> My command for running the app is:
> ./build/bbdev --vdev='baseband_ldpc' --vdev='net_tap0' --no-pci
>
Did you add your driver to the mk/rte.app.mk file?
> I hope that you can help with this problem.
>
> Best regards,
> Oscar
prev parent reply other threads:[~2019-01-31 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 10:42 Oscar Pap
2019-01-31 17:00 ` Wiles, Keith [this message]
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=B7B6CDB5-8B08-4D71-AC7E-E4FAD79956BA@intel.com \
--to=keith.wiles@intel.com \
--cc=oscarpap94@gmail.com \
--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).