From: Denys Vlasenko <vda.linux@googlemail.com>
To: "Michael Chan" <mchan@broadcom.com>
Cc: "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, "netdev" <netdev@vger.kernel.org>
Subject: Re: bnx2 dirver's firmware images
Date: Wed, 19 Sep 2007 21:29:22 +0100 [thread overview]
Message-ID: <200709192129.23034.vda.linux@googlemail.com> (raw)
In-Reply-To: <1190235642.9540.261.camel@dell>
On Wednesday 19 September 2007 22:00, Michael Chan wrote:
> On Wed, 2007-09-19 at 09:30 +0100, Denys Vlasenko wrote:
> + /* gzip header (1f,8b,08... 10 bytes total + possible asciz filename)
> + * is stripped, 32-bit unpacked size (LE) is prepended instead */
> + sz = *zbuf++;
> + sz = (sz << 8) + *zbuf++;
> + sz = (sz << 8) + *zbuf++;
> + sz = (sz << 8) + *zbuf++;
>
> I don't have a problem with removing the gzip header. It doesn't
> contain very useful information other than a valid header for sanity
> check. But I don't think we need to arbitrarily add the unpacked size
> in front of the gzipped data. The driver knows the size (e.g. the size
> of RAM on the chip) and should pass it to the call. The driver should
> also allocate the memory for the unpacked data instead of allocating the
> memory inside the call and freeing it by the caller. For example, the
> driver may need to use pci_alloc_consistent() if the firmware is to be
> DMA'ed to the chip.
>
> Other than that, everything else looks fine. Thanks.
Are you saying that you successfully run-tested it?
--
vda
next prev parent reply other threads:[~2007-09-19 20:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200709181823.26429.vda.linux@googlemail.com>
2007-09-18 18:45 ` bnx2 dirver's firmware images Michael Chan
2007-09-18 17:55 ` Denys Vlasenko
2007-09-18 19:09 ` Michael Chan
2007-09-18 18:23 ` David Miller
2007-09-18 18:41 ` H. Peter Anvin
2007-09-18 19:20 ` David Miller
2007-09-18 19:27 ` H. Peter Anvin
2007-09-18 20:08 ` David Miller
2007-09-18 20:35 ` Sam Ravnborg
2007-09-18 20:40 ` H. Peter Anvin
2007-09-19 17:10 ` maximilian attems
2007-09-19 17:12 ` H. Peter Anvin
2007-09-19 17:18 ` maximilian attems
2007-09-19 17:37 ` Sam Ravnborg
2007-09-18 20:05 ` Michael Chan
2007-09-18 19:21 ` David Miller
2007-09-18 21:30 ` Willy Tarreau
2007-09-18 21:31 ` David Miller
2007-09-18 21:37 ` Willy Tarreau
2007-09-18 23:14 ` Michael Chan
2007-09-19 13:40 ` Bill Davidsen
2007-09-19 16:09 ` David Miller
2007-09-19 8:30 ` Denys Vlasenko
2007-09-19 21:00 ` Michael Chan
2007-09-19 20:29 ` Denys Vlasenko [this message]
2007-09-19 21:43 ` Michael Chan
2007-09-20 14:49 ` Denys Vlasenko
2007-09-21 2:12 ` Michael Chan
2007-09-19 16:33 ` maximilian attems
2007-09-19 16:38 ` David Miller
2007-09-19 16:51 ` maximilian attems
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=200709192129.23034.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--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).