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 5327042FBA; Thu, 3 Aug 2023 00:48:10 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DB42A406BA; Thu, 3 Aug 2023 00:48:09 +0200 (CEST) Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mails.dpdk.org (Postfix) with ESMTP id 65BDE406B8 for <dev@dpdk.org>; Thu, 3 Aug 2023 00:48:08 +0200 (CEST) Received: by mail-pl1-f178.google.com with SMTP id d9443c01a7336-1bc0d39b52cso3042125ad.2 for <dev@dpdk.org>; Wed, 02 Aug 2023 15:48:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1691016487; x=1691621287; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=0Q0VSxdCWYaDl5KK8d4MO+i71Nc2YaUp7VkHP76z0C4=; b=YL8cBjXjazh1axFbuLZSQQTow7RVQe75QAfYDaDmwftapQSuhYqa21PnP+luvRx4RS 3MO/8WlDDOW6EsCF8GU7B7puW5xoO+nFhItRmxlkhiqhs1LdmNkCIwQD7bVCisgF+Wad a8o/3YK9CuF5i2RCAvl4jofUP0v2rilWsz4xBTxjZpaifcHQa8P2EDAgv/JTAu+xv7k1 s9FRbEfWH76fmcooSs3qxPf9yySw8akNvC4c4MleV85dkyYBT9GY8tGBtsKBdz5LgMCJ Ksi0MIeUh7LKWy8P0rgxpXXDozIA5nqPQBDdFHN5RJuT4gpRK8eYjSpFCZhZfNDh2WBy Y5wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691016487; x=1691621287; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=0Q0VSxdCWYaDl5KK8d4MO+i71Nc2YaUp7VkHP76z0C4=; b=Bj2nuvq5tcZ2TrdruX4e+JOSX3gdft5JCwRoCk/CTYVoct3lErS+eDRtcgrLvGBTNN lU9HJ/FkWc5tOFc3KWbQE8BVbM+KPpIc/sR73cO7+LcOK4/ibAiJ5J2linVnbVlRMrLA A2ITxP+Az3gvquGd9udwEhnPr2F3G+nY5L5iLtYkrCdCKOY+L8HcPLduOiUu7O+z+ICa azbxG21qrm+gatDGmmAlmHfiF3roJPYmKh/LfEx92qsIDwEYgIJHPm28ZzH2suvNyM41 O0f1wGtwWXf/VZZMex6vEPNi6eIeTJHypEMXi45qUg+q8nCf+aSu8g0V7zxE3zl6CFbp XZyQ== X-Gm-Message-State: ABy/qLb01xtteDZoRUJqKoMhrJ4INrE0fYzXxQmapK+GvZ4SVDxk3om6 1W2jlK0zGA4qBzJ12qRBM1UcZQ== X-Google-Smtp-Source: APBJJlEUj8G0UNQJNZOKR+To3+SIZojYTlVhdg7Panis6QHOwV9R58YsB3w+SzUakL7k3o7y4ut4wA== X-Received: by 2002:a17:902:e744:b0:1b2:5d5b:e871 with SMTP id p4-20020a170902e74400b001b25d5be871mr17847482plf.59.1691016487449; Wed, 02 Aug 2023 15:48:07 -0700 (PDT) Received: from hermes.local (204-195-127-207.wavecable.com. [204.195.127.207]) by smtp.gmail.com with ESMTPSA id 12-20020a170902e9cc00b001b05e96d859sm12925196plk.135.2023.08.02.15.48.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 02 Aug 2023 15:48:07 -0700 (PDT) Date: Wed, 2 Aug 2023 15:47:59 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: Philip Prindeville <philipp_subx@redfish-solutions.com> Cc: dev@dpdk.org Subject: Re: Drivers, architectures, processor families, etc. Message-ID: <20230802154759.0befb39c@hermes.local> In-Reply-To: <45384262-9744-4975-B5FB-D5D26608DF5B@redfish-solutions.com> References: <45384262-9744-4975-B5FB-D5D26608DF5B@redfish-solutions.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Wed, 2 Aug 2023 15:49:54 -0600 Philip Prindeville <philipp_subx@redfish-solutions.com> wrote: > 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 > DPDK now uses meson which by default builds everything available on the build architecture. There is intentionally no way to disable drivers, you can disable some libraries though.