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 18:39:01 -0400 [thread overview]
Message-ID: <48486B05.30300@garzik.org> (raw)
In-Reply-To: <1212272337.2534.27.camel@shinybook.infradead.org>
David Woodhouse wrote:
> On Thu, 2008-06-05 at 18:11 -0400, Jeff Garzik wrote:
>> Thus, if you are going to be touching the in-tree firmwares at all, it
>> doesn't make sense to convert from C source to any format other than
>> native binary.
>
> I disagree. But feel free to post patches which get applied and prove me
> wrong. I'm not going to object if you want to go convert a few more
> drivers.
IMO, if-and-only-if you are touching driver firmwares, you should not do
anything but render them into their preferred form.
It is useless churn that increases maintenance annoyances to convert an
in-tree firmware to something other than the form it's in now, so you
might as well get it right.
Jeff
next prev parent reply other threads:[~2008-06-05 22:39 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
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 [this message]
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=48486B05.30300@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 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.