From: Willy Tarreau <w@1wt.eu>
To: David Miller <davem@davemloft.net>
Cc: albcamus@gmail.com, chris@arachsys.com, mchan@broadcom.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] bnx2: update bnx2-mips-09 firmware to bnx2-mips-09-6.2.1b
Date: Wed, 8 Aug 2012 08:17:58 +0200 [thread overview]
Message-ID: <20120808061758.GA15255@1wt.eu> (raw)
In-Reply-To: <20120807.225800.1450928472652058111.davem@davemloft.net>
On Tue, Aug 07, 2012 at 10:58:00PM -0700, David Miller wrote:
> From: Jike Song <albcamus@gmail.com>
> Date: Wed, 8 Aug 2012 13:50:42 +0800
>
> > On Fri, Jul 13, 2012 at 9:04 PM, Chris Webb <chris@arachsys.com> wrote:
> >> Commit c2c20ef43d00 "bnx2: Update driver to use new mips firmware"
> >> updated the bnx2 driver to use bnx2-mips-09-6.2.1b in place of
> >> bnx2-mips-09-6.2.1a, but didn't replace the copy of bnx2-mips-09-6.2.1a
> >> in firmware/bnx2/ with the new version.
> >>
> >> This means that the bnx2 driver stopped working altogether for users who
> >> use CONFIG_FIRMWARE_IN_KERNEL to compile firmware together with drivers
> >> into their kernel, rather than having a runtime firmware loader.
> >>
> >
> > Still not fixed in mainline? I encountered the same problem with
> > v3.6-rc1-133-g42a579a.
>
> The current firmware for all drivers are not distributed in the kernel
> sources any longer, they are maintained in a completely seperate
> repository.
>
> The old ones are just kept around in the kernel sources for
> compatability.
>
> This is a FAQ.
Well, if the drivers provided with the kernel don't work out of the box
anymore, maybe we should also move them to a separate repository. All it
is going to do otherwise is to cause invalid bug reports because users
don't understand why using the latest driver does not work.
That way it would be clear that an in-kernel driver has to be self-sustaining
to be maintainable, otherwise it has nothing to do there.
Just my 2 cents,
Willy
next prev parent reply other threads:[~2012-08-08 6:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 13:04 [PATCH] bnx2: update bnx2-mips-09 firmware to bnx2-mips-09-6.2.1b Chris Webb
2012-07-13 13:42 ` Eric Dumazet
2012-07-13 14:09 ` Chris Webb
2012-07-13 21:12 ` Michael Chan
2012-07-14 4:27 ` Ben Hutchings
2012-08-08 5:50 ` Jike Song
2012-08-08 5:58 ` David Miller
2012-08-08 6:17 ` Willy Tarreau [this message]
2012-08-08 6:27 ` Eric Dumazet
2012-08-08 6:49 ` Willy Tarreau
2012-08-08 7:00 ` Eric Dumazet
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=20120808061758.GA15255@1wt.eu \
--to=w@1wt.eu \
--cc=albcamus@gmail.com \
--cc=chris@arachsys.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=stable@vger.kernel.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