From: Bastian Blank <waldi@debian.org>
To: Michael Chan <mchan@broadcom.com>
Cc: Rick Jones <rick.jones2@hp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] bnx2: Use request_firmware()
Date: Tue, 24 Mar 2009 08:42:14 +0100 [thread overview]
Message-ID: <20090324074213.GA4576@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <1237857085.18617.47.camel@HP1>
On Mon, Mar 23, 2009 at 06:11:25PM -0700, Michael Chan wrote:
> On Mon, 2009-03-23 at 17:14 -0700, Rick Jones wrote:
> > Michael Chan wrote:
> > > May be I'll break up each firmware section into a
> > > different file and the file name will be updated with each version.
> > > This will allow different sections to be updated separately and older
> > > kernels will still have access to the older firmware.
> > Is that really necessary? It is enough "fun" finding just the one firmware file
> > as it is.
> If all the firmware sections are in the same file, much of the firmware
> file will be duplicated in a new file when we update just one section.
What is the advantage of this? I always saw updates to more than one
firmware at once in the past. The question is not: is it possible, but:
it is necessary.
Bastian
--
Our way is peace.
-- Septimus, the Son Worshiper, "Bread and Circuses",
stardate 4040.7.
next prev parent reply other threads:[~2009-03-24 7:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 22:29 [PATCH] bnx2: Use request_firmware() Ben Hutchings
2009-03-19 23:04 ` Michael Chan
2009-03-19 23:25 ` Bastian Blank
2009-03-20 22:50 ` David Miller
2009-03-23 21:47 ` Michael Chan
2009-03-23 22:02 ` David Miller
2009-03-23 22:29 ` Bastian Blank
2009-03-23 23:24 ` Michael Chan
2009-03-24 0:14 ` Rick Jones
2009-03-24 1:11 ` Michael Chan
2009-03-24 1:26 ` Rick Jones
2009-03-24 1:44 ` Michael Chan
2009-03-24 4:27 ` Ben Hutchings
2009-03-24 7:42 ` Bastian Blank [this message]
2009-03-24 15:27 ` Michael Chan
2009-03-23 22:32 ` Bastian Blank
2009-03-23 23:28 ` Michael Chan
2009-04-01 18:01 ` Michael Chan
2009-04-02 8:05 ` David Miller
[not found] <1238778120-8132-1-git-send-email-mchan@broadcom.com>
2009-04-04 23:51 ` David Miller
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=20090324074213.GA4576@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.