DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Wei Huang <wei.huang@intel.com>,
	dev@dpdk.org, rosen.xu@intel.com, qi.z.zhang@intel.com
Cc: stable@dpdk.org, tianfei.zhang@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v11 4/4] examples/ifpga: add example for opae ifpga API
Date: Thu, 21 Jan 2021 16:49:11 +0000	[thread overview]
Message-ID: <f4aad4c6-cdf5-09c3-0228-bf8cc8e4f8e1@intel.com> (raw)
In-Reply-To: <1611209014-4031-5-git-send-email-wei.huang@intel.com>

On 1/21/2021 6:03 AM, Wei Huang wrote:
> +get_property command
> +~~~~~~~~~~~~~~~~~~~~
> +
> +Display property information of specified FPGA. Property type is defined as below.
> +0 - All properties
> +1 - PCI property
> +2 - FME property
> +4 - port property
> +8 - BMC property
> +PCI property is always available, other properties can only be displayed after
> +ifpga driver is probed to the FPGA.
> +
> +.. code-block:: console
> +
> +   opae> get_property 24:00.0 0
> +   PCI:
> +    PCIe s:b:d.f     : 0000:24:00.0
> +    kernel driver    : vfio-pci
> +   FME:
> +    platform         : Vista Creek
> +    DCP version      : DCP 1.2
> +    phase            : Beta
> +    interface        : 2x2x25G
> +    build version    : 0.0.2
> +    ports num        : 1
> +    boot page        : user
> +    pr interface id  : a5d72a3c-c8b0-4939-912c-f715e5dc10ca
> +   PORT0:
> +    access type      : PF
> +    accelerator id   : 8892c23e-2eed-4b44-8bb6-5c88606e07df
> +   BMC:
> +    MAX10 version    : D.2.0.5
> +    NIOS FW version  : D.2.0.12

Are all commands interacting device need to provide the PCI BDF as parameter to 
select the device? Like '24:00.0' in above sample.

Why not get the unique rawdev identifier, like port_id equivalent of the ethdev, 
and use it in the command line, won't it be easier?

  reply	other threads:[~2021-01-21 16:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21  6:03 [dpdk-dev] [PATCH v11 0/4] raw/ifpga: add extra OPAE APIs Wei Huang
2021-01-21  6:03 ` [dpdk-dev] [PATCH v11 1/4] raw/ifpga: add fpga rsu function Wei Huang
2021-01-21 16:30   ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-01-22  2:18     ` Huang, Wei
2021-01-25 10:01       ` Ferruh Yigit
2021-01-25 10:33         ` Xu, Rosen
2021-01-26  1:16           ` Huang, Wei
2021-01-21  6:03 ` [dpdk-dev] [PATCH v11 2/4] raw/ifpga: add fpga property get function Wei Huang
2021-01-21  6:03 ` [dpdk-dev] [PATCH v11 3/4] raw/ifpga: add OPAE API for OpenStack Cyborg Wei Huang
2021-01-21 16:29   ` Ferruh Yigit
2021-01-22  2:43     ` Huang, Wei
2021-01-25 10:07       ` Ferruh Yigit
2021-01-21 16:30   ` Ferruh Yigit
2021-01-22  3:16     ` Huang, Wei
2021-01-21 16:33   ` Ferruh Yigit
2021-01-22  3:25     ` Huang, Wei
2021-01-21  6:03 ` [dpdk-dev] [PATCH v11 4/4] examples/ifpga: add example for opae ifpga API Wei Huang
2021-01-21 16:49   ` Ferruh Yigit [this message]
2021-01-22  3:52     ` [dpdk-dev] [dpdk-stable] " Huang, Wei
2021-01-21  7:08 ` [dpdk-dev] [PATCH v11 0/4] raw/ifpga: add extra OPAE APIs Zhang, Qi Z

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=f4aad4c6-cdf5-09c3-0228-bf8cc8e4f8e1@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=rosen.xu@intel.com \
    --cc=stable@dpdk.org \
    --cc=tianfei.zhang@intel.com \
    --cc=wei.huang@intel.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).