From: Bastian Blank <waldi@debian.org>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] bnx2: Use request_firmware()
Date: Mon, 23 Mar 2009 23:29:15 +0100 [thread overview]
Message-ID: <20090323222915.GA29609@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <1237844879.18617.20.camel@HP1>
On Mon, Mar 23, 2009 at 02:47:59PM -0700, Michael Chan wrote:
> I'd also like to add the version information to the bnx2_fw_file_entry
> struct instead of embedding it in the file name. It is more flexible
> this way as each section can have different versions and can be updated
> separately. So it will look something like:
>
> struct bnx2_fw_file_entry {
> __be32 start_addr;
> __be32 version;
> struct bnx2_fw_file_section text;
> struct bnx2_fw_file_section data;
> struct bnx2_fw_file_section sbss;
> struct bnx2_fw_file_section bss;
> struct bnx2_fw_file_section rodata;
> };
And how do you want to handle the compatibility? One firmware file have
to work with many kernels, which was always described as impossible.
Bastian
--
Women are more easily and more deeply terrified ... generating more
sheer horror than the male of the species.
-- Spock, "Wolf in the Fold", stardate 3615.4
next prev parent reply other threads:[~2009-03-23 22:29 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 [this message]
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
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=20090323222915.GA29609@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--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 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.