| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1237850656.18617.34.camel@HP1>
Date: Mon, 23 Mar 2009 16:24:16 -0700
From: "Michael Chan" <mchan@...adcom.com>
To: "Bastian Blank" <waldi@...ian.org>
cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] bnx2: Use request_firmware()
On Mon, 2009-03-23 at 15:29 -0700, Bastian Blank wrote:
> 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.
>
I see your point. 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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists