No worries Ferruh, the reason is not very interesting so you can stop here.
:) Thanks for rebasing on rc2. But for the record, the cause is the EAL
message:
"EAL: Scan for (fslmc) bus failed."
Which I believe is now removed with this commit which is now in next-net:
https://git.dpdk.org/next/dpdk
monjalon.net>>
> > Sent: Monday, November 11, 2024 3:02 PM
> > To: Stephen Hemminger <mailto:step...@networkplumber.org>>; Gagandeep Singh
> > mailto:g.si...@nxp.com>>; Sachin Saxena (OSS)
> mailto:sachin.sax...@oss.nxp.com>>;
>
t; > Sent: Monday, November 11, 2024 3:02 PM
> > To: Stephen Hemminger ; Gagandeep Singh
> > ; Sachin Saxena (OSS) ;
> > Hemant Agrawal
> > Cc: dev@dpdk.org
> > Subject: Re: Bus scan is too chatty
> > Importance: High
> >
> > 10/11/2024 20:17, Step
> -Original Message-
> From: Thomas Monjalon
> Sent: Monday, November 11, 2024 3:02 PM
> To: Stephen Hemminger ; Gagandeep Singh
> ; Sachin Saxena (OSS) ;
> Hemant Agrawal
> Cc: dev@dpdk.org
> Subject: Re: Bus scan is too chatty
> Importance: High
>
10/11/2024 20:17, Stephen Hemminger:
> DPDK EAL needs to be less verbose for non-existent buses.
> Most users won't have embedded devices, and messages like:
>
> EAL: Scan for (fslmc) bus failed.
>
> will be confusing.
When merging the recent fslmc patches, I've reduced the verbosity
of some fsl
5 matches
Mail list logo
