On Sat, Jun 10, 2017 at 10:50:12AM +0200, Jan Blunck wrote:
> On Thu, Jun 8, 2017 at 2:51 PM, Gaëtan Rivet wrote:
> > On Thu, Jun 08, 2017 at 01:40:46PM +0200, Jan Blunck wrote:
> >> On Thu, Jun 8, 2017 at 1:36 PM, Gaëtan Rivet
> >> wrote:
> >> > On Thu, Jun 08, 2017 at 12:45:17PM +0200, Jan Blu
On Thu, Jun 8, 2017 at 2:51 PM, Gaëtan Rivet wrote:
> On Thu, Jun 08, 2017 at 01:40:46PM +0200, Jan Blunck wrote:
>> On Thu, Jun 8, 2017 at 1:36 PM, Gaëtan Rivet wrote:
>> > On Thu, Jun 08, 2017 at 12:45:17PM +0200, Jan Blunck wrote:
>> >> On Wed, Jun 7, 2017 at 10:03 PM, Gaëtan Rivet
>> >> wro
On Thu, Jun 08, 2017 at 01:40:46PM +0200, Jan Blunck wrote:
> On Thu, Jun 8, 2017 at 1:36 PM, Gaëtan Rivet wrote:
> > On Thu, Jun 08, 2017 at 12:45:17PM +0200, Jan Blunck wrote:
> >> On Wed, Jun 7, 2017 at 10:03 PM, Gaëtan Rivet
> >> wrote:
> >> > On Wed, Jun 07, 2017 at 07:28:07PM +0200, Jan Bl
On Thu, Jun 8, 2017 at 1:36 PM, Gaëtan Rivet wrote:
> On Thu, Jun 08, 2017 at 12:45:17PM +0200, Jan Blunck wrote:
>> On Wed, Jun 7, 2017 at 10:03 PM, Gaëtan Rivet wrote:
>> > On Wed, Jun 07, 2017 at 07:28:07PM +0200, Jan Blunck wrote:
>> >> On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet
>> >> wr
On Thu, Jun 08, 2017 at 12:45:17PM +0200, Jan Blunck wrote:
> On Wed, Jun 7, 2017 at 10:03 PM, Gaëtan Rivet wrote:
> > On Wed, Jun 07, 2017 at 07:28:07PM +0200, Jan Blunck wrote:
> >> On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet
> >> wrote:
> >> > Find which bus should be able to parse this dev
On Wed, Jun 7, 2017 at 10:03 PM, Gaëtan Rivet wrote:
> On Wed, Jun 07, 2017 at 07:28:07PM +0200, Jan Blunck wrote:
>> On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet wrote:
>> > Find which bus should be able to parse this device name into an internal
>> > device representation.
>> >
>>
>> No, pleas
On Wed, Jun 07, 2017 at 07:28:07PM +0200, Jan Blunck wrote:
> On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet wrote:
> > Find which bus should be able to parse this device name into an internal
> > device representation.
> >
>
> No, please don't add this. One should know to what bus a device
> belo
On Wed, May 24, 2017 at 5:12 PM, Gaetan Rivet wrote:
> Find which bus should be able to parse this device name into an internal
> device representation.
>
No, please don't add this. One should know to what bus a device
belongs to before plugging it. Artificially encoding the parent bus
into the d
Find which bus should be able to parse this device name into an internal
device representation.
Signed-off-by: Gaetan Rivet
---
lib/librte_eal/bsdapp/eal/rte_eal_version.map | 1 +
lib/librte_eal/common/eal_common_bus.c | 15 +++
lib/librte_eal/common/include/rte_bus.h
9 matches
Mail list logo