From: Jeff Garzik <jeff@garzik.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/18] firmware: moving drivers to request_firmware()
Date: Thu, 05 Jun 2008 17:33:23 -0400 [thread overview]
Message-ID: <48485BA3.60809@garzik.org> (raw)
In-Reply-To: <1212268943.2534.16.camel@shinybook.infradead.org>
David Woodhouse wrote:
> On Thu, 2008-06-05 at 17:01 -0400, Jeff Garzik wrote:
>> If the sha1 sum of what is in the kernel tree differs from what the
>> vendor provided, then it is OBVIOUSLY more difficult to verify that
>> you have the original firmware as provided by the vendor.
>>
>> Put the binary blobs into the git tree, __without modification or
>> wrapping__.
>
> We don't have them in that form right now. Of the firmware blobs I've
> encountered so far -- even the ones which were in a file on their own --
> none of them are in binary form; they're _all_ in some ASCII
> representation which can be processed with 'diff'. That includes char
> arrays, arrays of larger integers which need endian-awareness, 'hex
> record' structures, and probably a bunch of other abominations I have
> yet to encounter as I work through them.
>
> None of them have just been binary files in the source tree.
Right. And now you are creating Yet Another Format, rather than
rendering the firmware back into the preferred format: binary blob.
_If_ you are changing form of current in-tree firmwares at all, there is
no excuse not use direct binary blob -- the least common denominator for
all relevant operations.
Storing the firmware in .ihex is just as bad as storing the firmware in
source code -- it's a pointless wrapper that makes firmware verification
and updates far more difficult than they should be.
Jeff
next prev parent reply other threads:[~2008-06-05 21:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 9:52 [PATCH 00/18] firmware: moving drivers to request_firmware() David Woodhouse
2008-05-23 12:52 ` [PATCH 01/18] firmware: allow firmware files to be built into kernel image David Woodhouse
2008-05-23 12:58 ` [PATCH 02/18] firmware: Add CONFIG_BUILTIN_FIRMWARE option David Woodhouse
2008-05-26 22:01 ` [PATCH 04/18] firmware: convert korg1212 driver to use firmware loader exclusively David Woodhouse
2008-05-29 8:01 ` [PATCH 03/18] firmware: Add 'firmware_install' make target David Woodhouse
2008-05-29 11:48 ` [PATCH 05/18] firmware: convert maestro3 driver to use firmware loader exclusively David Woodhouse
2008-05-29 12:07 ` [PATCH 06/18] firmware: convert ymfpci " David Woodhouse
2008-05-29 13:39 ` [PATCH 07/18] smctr: use request_firmware() David Woodhouse
2008-05-29 14:17 ` [PATCH 08/18] kaweth: " David Woodhouse
2008-05-29 16:50 ` [PATCH 09/18] ttusb-budget: " David Woodhouse
2008-05-30 10:57 ` [PATCH 10/18] ihex.h: binary representation of ihex records David Woodhouse
2008-06-05 12:26 ` Clemens Ladisch
2008-05-31 22:20 ` David Woodhouse
2008-05-30 12:15 ` [PATCH 14/18] keyspan_pda: use request_firmware() David Woodhouse
2008-05-30 15:49 ` [PATCH 17/18] ti_usb_3410_5052: " David Woodhouse
2008-05-30 22:35 ` [PATCH 18/18] whiteheat: " David Woodhouse
2008-05-31 12:07 ` [PATCH 12/18] ihex: add ihex2fw tool for converting HEX files into firmware images David Woodhouse
2008-05-31 12:20 ` [PATCH 11/18] ihex: request_ihex_firmware() function to load and validate firmware David Woodhouse
2008-06-05 10:07 ` [PATCH 00/18] firmware: moving drivers to request_firmware() Arkadiusz Miskiewicz
2008-06-05 10:09 ` David Woodhouse
2008-06-05 12:26 ` Clemens Ladisch
2008-06-05 19:16 ` Jeff Garzik
2008-06-05 19:54 ` David Woodhouse
2008-06-05 20:12 ` Jeff Garzik
2008-06-05 20:53 ` David Woodhouse
2008-06-05 21:01 ` Jeff Garzik
2008-05-31 21:22 ` David Woodhouse
2008-06-05 21:33 ` Jeff Garzik [this message]
2008-05-31 22:15 ` David Woodhouse
2008-06-05 22:11 ` Jeff Garzik
2008-05-31 22:18 ` David Woodhouse
2008-06-05 22:39 ` Jeff Garzik
2008-05-31 22:45 ` David Woodhouse
2008-06-06 9:15 ` Alan Cox
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=48485BA3.60809@garzik.org \
--to=jeff@garzik.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@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