DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	Selwin Sebastian <Selwin.Sebastian@amd.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3] drivers: add a HW quirk for register definitions
Date: Tue, 14 Jan 2020 13:18:15 +0000	[thread overview]
Message-ID: <ab8e8feb-aeb2-246f-2c51-c23a6b5a16ce@intel.com> (raw)
In-Reply-To: <CAJFAV8xCDsUF7kaY=sGxbtXSWL1Br9N6dc60Q1JQ6C684-Oa3g@mail.gmail.com>

On 1/14/2020 12:35 PM, David Marchand wrote:
> On Tue, Jan 14, 2020 at 12:58 PM Selwin Sebastian
> <Selwin.Sebastian@amd.com> wrote:
>>
>> V1000/R1000 processors are using the same PCI ids for the network
>> device as SNOWYOWL processor but has altered register definitions
>> for determining the window settings for the indirect PCS access.
>> Add support to check for this hardware and if found use the new
>> register values.
>>
>> Added a new routine rte_pci_search_device to pci driver to search
>> for a device.
> 
> You can already iterate on a bus devices.
> 
> struct rte_bus *pci_bus = rte_bus_find_by_name("pci");
> return pci_bus != NULL && pci_bus->find_device(NULL, callback, args) != NULL;
> 
> See: https://git.dpdk.org/dpdk/tree/drivers/bus/pci/pci_params.c#n38
> 

Nice, this looks better approach.

  reply	other threads:[~2020-01-14 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 17:30 Selwin Sebastian
2020-01-14 12:30 ` Ferruh Yigit
2020-01-14 12:35 ` David Marchand
2020-01-14 13:18   ` Ferruh Yigit [this message]
2020-01-20  7:14     ` Sebastian, Selwin

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=ab8e8feb-aeb2-246f-2c51-c23a6b5a16ce@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Selwin.Sebastian@amd.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --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).