From: Christophe Grosse <christophe.grosse@6wind.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: [dpdk-dev] BCM57414 VF Mode: max_rx_em_flows value is inconsistent
Date: Tue, 17 Dec 2019 16:41:56 +0100 [thread overview]
Message-ID: <2a976877-e00f-83f9-dcd4-0a0dce28d8c3@6wind.com> (raw)
In-Reply-To: <CACZ4nhvohiyfjyUnF_FYu_dX5DbjFeNQRs+NijKQyc3NupT2ZQ@mail.gmail.com>
Thank you for your answer.
On 12/11/19 6:45 PM, Ajit Khaparde wrote:
>>
>> On master, I see that the new calculation for the number of L2 context
>> has been restricted to Whitney chip family.
>> Anyone knows if the chip/FW I am using is compatible with this new
>> calculation ?
>>
>> By the way, I tried to upgrade to FW 214.0.253.5 and Init is falling very
>> early:
>> bnxt_hwrm_func_resc_qcaps(): error 1:0:00000000:00f9
>>
> 214.0.x is older FW as far our releases are concerned.
> I think you will need the following commit from upstream
> to get past the error you are seeing.
> Commit: 89a0deb866dc42ead92b79e6e7159622e1ab8490
> net/bnxt: fix resource qcaps with older FW
I tried the previous commit.
It suppresses a repetitive error message, that I didn't mention before.
Also, I was able to start with firmware 214.0.253.5. But, if you say
it's an old release, i won't use it.
>
> But I believe you will need a newer firmware to get consistent values
> across the ports. Let me see how to get that to you.
>
If you have a new firmware for BCM57414, I would be glad to give it a
try. (I currently have 20.06.01.06)
Best Regards,
Christophe
prev parent reply other threads:[~2019-12-17 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 15:57 Christophe Grosse
2019-12-11 17:45 ` Ajit Khaparde
2019-12-12 20:29 ` Kevin Traynor
2019-12-17 15:41 ` Christophe Grosse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2a976877-e00f-83f9-dcd4-0a0dce28d8c3@6wind.com \
--to=christophe.grosse@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).