Subject: Re: [dpdk-dev] [PATCH v4 2/2] bus/auxiliary: introduce auxiliary bus
23/06/2021 16:52, Xueming(Steven) Li:
> From: Thomas Monjalon
> > 23/06/2021 01:50, Xueming(Steven) Li:
> > > From: Thomas Monjalon
> > > > 13/06/2021 14:58, Xueming Li:
> > > > &
23/06/2021 16:52, Xueming(Steven) Li:
> From: Thomas Monjalon
> > 23/06/2021 01:50, Xueming(Steven) Li:
> > > From: Thomas Monjalon
> > > > 13/06/2021 14:58, Xueming Li:
> > > > > --- /dev/null
> > > > > +++ b/drivers/bus/auxiliary/version.map
> > > > > @@ -0,0 +1,7 @@
> > > > > +EXPERIMENTAL {
>
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, June 23, 2021 4:15 PM
> To: Xueming(Steven) Li
> Cc: Parav Pandit ; dev@dpdk.org; Wang Haiyue
> ; Kinsella Ray ;
> david.march...@redhat.com; ferruh.yi...@intel.com
> Subject: Re: [dpdk-dev] [PAT
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, June 23, 2021 4:22 PM
> To: Parav Pandit ; Xueming(Steven) Li
> Cc: dev@dpdk.org; Wang Haiyue ; Kinsella Ray
> ; david.march...@redhat.com;
> ferruh.yi...@intel.com
> Subject: Re: [dpdk-dev] [PAT
23/06/2021 01:50, Xueming(Steven) Li:
> From: Thomas Monjalon
> > 13/06/2021 14:58, Xueming Li:
> > > + struct rte_auxiliary_driver *driver; /**< driver used in probing */
> >
> > Why in probing?
> > I suggest "Device driver"
>
> A SF device could be probed by a class driver t then another
23/06/2021 01:50, Xueming(Steven) Li:
> From: Thomas Monjalon
> > 13/06/2021 14:58, Xueming Li:
> > > --- /dev/null
> > > +++ b/drivers/bus/auxiliary/version.map
> > > @@ -0,0 +1,7 @@
> > > +EXPERIMENTAL {
> > > + global:
> > > +
> > > + # added in 21.08
> > > + rte_auxiliary_register;
> > > + rte
> -Original Message-
> From: Thomas Monjalon
> Sent: Tuesday, June 22, 2021 12:11 AM
> To: Parav Pandit ; Xueming(Steven) Li
> Cc: dev@dpdk.org; Wang Haiyue ; Kinsella Ray
> ; david.march...@redhat.com;
> ferruh.yi...@intel.com
> Subject: Re: [dpdk-dev] [PAT
13/06/2021 14:58, Xueming Li:
> 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/b
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 syntax of a
9 matches
Mail list logo