From: "Michael Chan" <mchan@broadcom.com>
To: "maximilian attems" <max@stro.at>
Cc: "David Miller" <davem@davemloft.net>, "netdev" <netdev@vger.kernel.org>
Subject: Re: [PATCH 6/7][BNX2]: Update firmware.
Date: Tue, 29 Jan 2008 18:29:56 -0800 [thread overview]
Message-ID: <1201660196.19087.29.camel@dell> (raw)
In-Reply-To: <20080129234615.GB25253@stro.at>
On Wed, 2008-01-30 at 00:46 +0100, maximilian attems wrote:
> happily omitted diffstat:
> drivers/net/bnx2_fw.h | 1499 +++++++++++++++++++--------------------
> drivers/net/bnx2_fw2.h | 464 ++++++------
> 2 files changed, 982 insertions(+), 981 deletions(-)
>
>
> when can bnx2 grow up to proper request_firmware() usage?
>
Didn't we beat this topic to death last time?
Once again, the driver is tightly coupled with the firmware. We don't
want things to break when users upgrade or downgrade the kernel. Coding
the driver to deal with different firmware versions will add a lot of
complexity.
next prev parent reply other threads:[~2008-01-30 1:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 0:20 [PATCH 6/7][BNX2]: Update firmware Michael Chan
2008-01-29 23:46 ` maximilian attems
2008-01-30 2:29 ` Michael Chan [this message]
2008-01-30 5:16 ` David Miller
2008-01-30 5:38 ` 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=1201660196.19087.29.camel@dell \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=max@stro.at \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).