From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet Subject: Re: [PATCH v2 04/13] bus/vdev: add device matching field driver Date: Fri, 21 Sep 2018 13:53:12 +0200 Message-ID: <20180921115312.sdegsb3ko2mbf7hc@bidouze.vm.6wind.com> References: <2305853.Xkr2rJqqKv@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-wm1-f67.google.com (mail-wm1-f67.google.com [209.85.128.67]) by dpdk.org (Postfix) with ESMTP id 546521041 for ; Fri, 21 Sep 2018 13:53:31 +0200 (CEST) Received: by mail-wm1-f67.google.com with SMTP id f21-v6so2749175wmc.5 for ; Fri, 21 Sep 2018 04:53:31 -0700 (PDT) Content-Disposition: inline In-Reply-To: <2305853.Xkr2rJqqKv@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Sep 20, 2018 at 06:11:44PM +0200, Thomas Monjalon wrote: > 19/09/2018 18:03, Gaetan Rivet: > > The vdev bus parses a field "driver", matching > > a vdev driver name with one passed as follows: > > > > "bus=vdev,driver=xxxx" > > I think the property should be "name". > We already have a "driver" category. > So it may be "bus=vdev,name=mytap/driver=tap" > > Until now we were using the name of the driver as a prefix for > the device name because it was the only way of knowing the driver to use. > With a richer syntax like above, this restriction can be removed. Do you want all buses to read the driver= key and use it to know which driver to probe, or is it an exception of the vdev bus? -- Gaëtan Rivet 6WIND