From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: time to kill rte_pci_dev_ids.h
Date: Wed, 06 Jan 2016 02:40:38 +0100
Message-ID: <5405012.WIUT4XHNxg@xps13>
References: <20160105113723.6d2b85e5@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: Stephen Hemminger <stephen@networkplumber.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com
 [209.85.192.179]) by dpdk.org (Postfix) with ESMTP id A59BD941C
 for <dev@dpdk.org>; Wed,  6 Jan 2016 02:42:18 +0100 (CET)
Received: by mail-pf0-f179.google.com with SMTP id e65so176554330pfe.1
 for <dev@dpdk.org>; Tue, 05 Jan 2016 17:42:18 -0800 (PST)
In-Reply-To: <20160105113723.6d2b85e5@xeon-e3>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-01-05 11:37, Stephen Hemminger:
> Has anyone looked at getting rid of rte_pci_dev_ids.h?
> The current method with #ifdef's and putting all devices in one file
> really doesn't scale well. Something more like other OS's where
> the data is only in each device driver would be better.

I agree.
The PCI ids should be embedded in drivers.
If I remember well, it's already the case for some of them.
I would love to see a tool able to list the supported devices
by reading a binary libraries.