DPDK patches and discussions
 help / color / mirror / Atom feed
From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: dev@dpdk.org
Subject: Drivers, architectures, processor families, etc.
Date: Wed, 2 Aug 2023 15:49:54 -0600	[thread overview]
Message-ID: <45384262-9744-4975-B5FB-D5D26608DF5B@redfish-solutions.com> (raw)

Hi,

I'm trying to come up with some Kconfig logic for OpenWRT packaging to help users select the right build options for their hardware.

Most OpenWRT developers typically cross-compile, so we obviously can't rely on detection on the build host as that's rarely the same as the target machine.

Looking in the DPDK repo, I don't see any description of the available architectures, drivers, etc. and what I had seen previously was (if I remember) only for x86_64 hardware, and even that I can't seem to locate again.

Would it make sense to put some of these definitions into the repo itself, so that when new drivers are added, that stands out (at least in the commit logs) and we can capture the permutations of what driver goes with which SoC on what architecture, etc?

Thanks,

-Philip


             reply	other threads:[~2023-08-02 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 21:49 Philip Prindeville [this message]
2023-08-02 22:47 ` Stephen Hemminger
2023-08-03  8:17   ` Bruce Richardson
2023-08-05 21:32     ` Philip Prindeville
2023-08-08  8:17       ` Bruce Richardson
2023-08-08 16:38         ` Philip Prindeville
2023-08-03 16:40   ` Philip Prindeville
2023-08-08  8:29     ` Bruce Richardson
2023-08-14 15:31 ` Ferruh Yigit

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=45384262-9744-4975-B5FB-D5D26608DF5B@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=dev@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).