From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 9C16642FBA;
	Wed,  2 Aug 2023 23:50:13 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 3D3C44021E;
	Wed,  2 Aug 2023 23:50:13 +0200 (CEST)
Received: from mail.redfish-solutions.com (mail.redfish-solutions.com
 [24.116.100.90]) by mails.dpdk.org (Postfix) with ESMTP id 3AE134021D
 for <dev@dpdk.org>; Wed,  2 Aug 2023 23:50:12 +0200 (CEST)
Received: from smtpclient.apple (macbook3-8.redfish-solutions.com
 [192.168.8.12] (may be forged)) (authenticated bits=0)
 by mail.redfish-solutions.com (8.17.1/8.16.1) with ESMTPSA id 372Lo8Qd061834
 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
 for <dev@dpdk.org>; Wed, 2 Aug 2023 15:50:09 -0600
From: Philip Prindeville <philipp_subx@redfish-solutions.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Subject: Drivers, architectures, processor families, etc.
Message-Id: <45384262-9744-4975-B5FB-D5D26608DF5B@redfish-solutions.com>
Date: Wed, 2 Aug 2023 15:49:54 -0600
To: dev@dpdk.org
X-Mailer: Apple Mail (2.3731.600.7)
X-Scanned-By: MIMEDefang 3.4.1 on 192.168.8.3
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

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