Hello Aaron,
On Thursday 12 October 2017 06:50 PM, Aaron Conole wrote:
Shreyansh Jain writes:
Hello Aaron,
On Tuesday 10 October 2017 09:30 PM, Aaron Conole wrote:
Shreyansh Jain writes:
Hello Don,
[snip]
[snip]
I am assuming that that aim of this is to have a way so that
appl
Shreyansh Jain writes:
> Hello Aaron,
>
> On Tuesday 10 October 2017 09:30 PM, Aaron Conole wrote:
>> Shreyansh Jain writes:
>>
>>> Hello Don,
>>>
>
> [snip]
>
These practical problems confirm to me that the failure of a bus
scan is more of a strategic issue: when asking "which de
nsh Jain [mailto:shreyansh.j...@nxp.com]
>> >>> Sent: Monday, October 09, 2017 4:10 AM
>> >>> To: Jan Blunck ; Thomas Monjalon
>> >>>
>> >>> Cc: dev ; Hemant Agrawal
>> >>> Subject: Re: [dpdk-dev] [PATCH] eal: bus scan and p
Hello Aaron,
On Tuesday 10 October 2017 09:30 PM, Aaron Conole wrote:
Shreyansh Jain writes:
Hello Don,
[snip]
These practical problems confirm to me that the failure of a bus
scan is more of a strategic issue: when asking "which devices can
I use?", "none" is a perfectly valid answer t
Sent: Monday, October 09, 2017 4:10 AM
> >>> To: Jan Blunck ; Thomas Monjalon
> >>>
> >>> Cc: dev ; Hemant Agrawal
> >>> Subject: Re: [dpdk-dev] [PATCH] eal: bus scan and probe never fail
> >>>
> >>> ...
> >>> This i
11/10/2017 02:03, Don Provan:
> From: Shreyansh Jain [mailto:shreyansh.j...@nxp.com]
> >
> > ...
> >
> > > From the application's point of view, the potential error here
> > > is that the device it wants to use isn't available. I don't see that
> > > either the init function or the probe function
> -Original Message-
> From: Shreyansh Jain [mailto:shreyansh.j...@nxp.com]
> Sent: Monday, October 09, 2017 10:01 PM
> To: Don Provan ; Jan Blunck ;
> Thomas Monjalon
> Cc: dev ; Hemant Agrawal
> Subject: Re: [dpdk-dev] [PATCH] eal: bus scan and probe never fail
>
as Monjalon
>>>
>>> Cc: dev ; Hemant Agrawal
>>> Subject: Re: [dpdk-dev] [PATCH] eal: bus scan and probe never fail
>>>
>>> ...
>>> This is where I have disagreement/doubt.
>>> Reporting error code from rte_bus_scan would do two things
Hello Don,
On Monday 09 October 2017 11:51 PM, Don Provan wrote:
-Original Message-
From: Shreyansh Jain [mailto:shreyansh.j...@nxp.com]
Sent: Monday, October 09, 2017 4:10 AM
To: Jan Blunck ; Thomas Monjalon
Cc: dev ; Hemant Agrawal
Subject: Re: [dpdk-dev] [PATCH] eal: bus scan and
09/10/2017 20:21, Don Provan:
> From: Shreyansh Jain [mailto:shreyansh.j...@nxp.com]
> >...
> > This is where I have disagreement/doubt.
> > Reporting error code from rte_bus_scan would do two things:
> >
> > 1. rte_eal_init is not designed to ignore/log-only these errors - it
> > would quit initi
> -Original Message-
> From: Shreyansh Jain [mailto:shreyansh.j...@nxp.com]
> Sent: Monday, October 09, 2017 4:10 AM
> To: Jan Blunck ; Thomas Monjalon
>
> Cc: dev ; Hemant Agrawal
> Subject: Re: [dpdk-dev] [PATCH] eal: bus scan and probe never fail
>
>
On Friday 06 October 2017 11:04 PM, Jan Blunck wrote:
On Fri, Oct 6, 2017 at 3:37 PM, Thomas Monjalon wrote:
06/10/2017 15:12, Shreyansh Jain:
On Friday 06 October 2017 04:51 AM, Thomas Monjalon wrote:
19/09/2017 20:51, Jan Blunck:
On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal wrote:
Tes
On Fri, Oct 6, 2017 at 3:37 PM, Thomas Monjalon wrote:
> 06/10/2017 15:12, Shreyansh Jain:
>> On Friday 06 October 2017 04:51 AM, Thomas Monjalon wrote:
>> > 19/09/2017 20:51, Jan Blunck:
>> >> On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal
>> >> wrote:
>> >>> Tested-by: Hemant Agrawal
>> >>>
06/10/2017 15:12, Shreyansh Jain:
> On Friday 06 October 2017 04:51 AM, Thomas Monjalon wrote:
> > 19/09/2017 20:51, Jan Blunck:
> >> On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal
> >> wrote:
> >>> Tested-by: Hemant Agrawal
> >>>
> >>>
> >>> On 8/12/2017 3:52 PM, Shreyansh Jain wrote:
>
>
On Friday 06 October 2017 04:51 AM, Thomas Monjalon wrote:
19/09/2017 20:51, Jan Blunck:
On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal wrote:
Tested-by: Hemant Agrawal
On 8/12/2017 3:52 PM, Shreyansh Jain wrote:
Bus scan is responsible for finding devices over *all* buses.
Some of these
19/09/2017 20:51, Jan Blunck:
> On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal
> wrote:
> > Tested-by: Hemant Agrawal
> >
> >
> > On 8/12/2017 3:52 PM, Shreyansh Jain wrote:
> >>
> >> Bus scan is responsible for finding devices over *all* buses.
> >> Some of these buses might not be able to sca
On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal wrote:
> Tested-by: Hemant Agrawal
>
>
> On 8/12/2017 3:52 PM, Shreyansh Jain wrote:
>>
>> Bus scan is responsible for finding devices over *all* buses.
>> Some of these buses might not be able to scan but that should
>> not prevent other buses to b
Tested-by: Hemant Agrawal
On 8/12/2017 3:52 PM, Shreyansh Jain wrote:
Bus scan is responsible for finding devices over *all* buses.
Some of these buses might not be able to scan but that should
not prevent other buses to be scanned.
Same is the case for probing. It is possible that some device
Bus scan is responsible for finding devices over *all* buses.
Some of these buses might not be able to scan but that should
not prevent other buses to be scanned.
Same is the case for probing. It is possible that some devices which
were scanned didn't have a specific driver. That should not preven
19 matches
Mail list logo
