DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
To: Harish Patil <harish.patil@qlogic.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Updating bnx2x firmware
Date: Thu, 24 Mar 2016 22:31:46 -0300	[thread overview]
Message-ID: <CAJSM8J3AWDSzp=zj2hayQFGqekkahckDwuyjAakgvPxX3mOrGw@mail.gmail.com> (raw)
In-Reply-To: <D319B102.186295%harish.patil@qlogic.com>

On 24 March 2016 at 19:03, Harish Patil <harish.patil@qlogic.com> wrote:

> >
> >Guys,
> >
> > Currently, the bnx2x.c driver looks for the following firmware files
> >(when
> >PMD is enabled for it):
> >
> >---
> >$ ~/sources/dpdk/dpdk-2.2.0/drivers/net/bnx2x$ grep lib\/firmware *
> >bnx2x.c:#define FW_NAME_57711 "/lib/firmware/bnx2x/bnx2x-e1h-7.2.51.0.fw"
> >bnx2x.c:#define FW_NAME_57810 "/lib/firmware/bnx2x/bnx2x-e2-7.2.51.0.fw"
> >---
> >
> > Files bnx2x-e1h-7.2.51.0.fw and bnx2x-e2-7.2.51.0.fw.
> >
> >
> > However, on Ubuntu 16.04, the package linux-firmware comes with:
> >
> >---
> >$ dpkg -L linux-firmware | grep -i bnx2x
> >/lib/firmware/bnx2x/bnx2x-e1h-7.12.30.0.fw
> >/lib/firmware/bnx2x/bnx2x-e1-7.12.30.0.fw
> >/lib/firmware/bnx2x/bnx2x-e1-7.13.1.0.fw
> >/lib/firmware/bnx2x/bnx2x-e2-7.12.30.0.fw
> >/lib/firmware/bnx2x/bnx2x-e1h-7.13.1.0.fw
> >/lib/firmware/bnx2x/bnx2x-e2-7.13.1.0.fw
> >---
> >
> >
> > Is it okay to just point bnx2x.c to a new version and rebuild it ?
> >
> > For example: bnx2x-e1h-7.13.1.0.fw and bnx2x-e2-7.13.1.0.fw ?
> >
> >
> > I would prefer to not manually download old firmware from Github:
> >
> > https://github.com/cernekee/linux-firmware/tree/master/bnx2x
> >
> >
> >Thanks,
> >Thiago
> >
>
> Hi Thiago
> Any reason why you don’t prefer to get the required FW file from other
> source?
>
> You can certainly download it from:
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tre
> e/bnx2x
>
> Any other FW is an untested combination.
>
> Thanks,
> Harish
>

Hi Harish,

 Sure, I can download the firmware files, no problem... I just prefer to
stick with the packages/files from the distribution that I'm using (Ubuntu
16.04) but, on this case, I'll follow your recommendation.

 I don't know why Ubuntu removed the previous firmware files out from
"linux-firmware" package...

 Thanks for posting the git.kernel.org link!

Best,
Thiago

  reply	other threads:[~2016-03-25  1:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 21:53 Martinx - ジェームズ
2016-03-24 22:03 ` Harish Patil
2016-03-25  1:31   ` Martinx - ジェームズ [this message]
2016-03-29  7:26     ` Christian Ehrhardt

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='CAJSM8J3AWDSzp=zj2hayQFGqekkahckDwuyjAakgvPxX3mOrGw@mail.gmail.com' \
    --to=thiagocmartinsc@gmail.com \
    --cc=dev@dpdk.org \
    --cc=harish.patil@qlogic.com \
    /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).