25/06/2021 05:26, Xueming(Steven) Li:
> From: Thomas Monjalon
> > 23/06/2021 02:03, Xueming Li:
> > > +static int
> > > +auxiliary_parse(const char *name, void *addr) {
> > > + struct rte_auxiliary_driver *drv = NULL;
> > > + const char **out = addr;
> > > +
> > > + /* Allow dummy name to prevent
> -Original Message-
> From: Thomas Monjalon
> Sent: Friday, June 25, 2021 12:19 AM
> To: Xueming(Steven) Li
> Cc: dev@dpdk.org; Wang Haiyue ; Kinsella Ray
>
> Subject: Re: [dpdk-dev] [PATCH v5 2/2] bus/auxiliary: introduce auxiliary bus
>
> 2
23/06/2021 02:03, Xueming Li:
> +static int
> +rte_auxiliary_probe_one_driver(struct rte_auxiliary_driver *drv,
> +struct rte_auxiliary_device *dev)
[...]
> + AUXILIARY_LOG(DEBUG, "Probe driver: %s", drv->driver.name);
I think the debug log above is useless given th
Auxiliary bus [1] provides a way to split function into child-devices
representing sub-domains of functionality. Each auxiliary device
represents a part of its parent functionality.
Auxiliary device is identified by unique device name, sysfs path:
/sys/bus/auxiliary/devices/
Devargs legacy synt
4 matches
Mail list logo
