mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Deti Fliegl <deti@fliegl.de>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-kernel@vger.kernel.org, jaswinder@infradead.org,
	bunk@kernel.org
Subject: Re: [PATCH] dabusb: use request_firmware()
Date: Mon, 23 Jun 2008 12:45:58 +0100	[thread overview]
Message-ID: <1214221558.27974.33.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20080623112004.GA26516@infradead.org>

On Mon, 2008-06-23 at 07:20 -0400, Christoph Hellwig wrote:
> > +config USB_DABUSB_FIRMWARE
> > +	bool "Include firmware images for DABUSB driver"
> > +	depends on USB_DABUSB
> > +	---help---
> > +	Include the firmware for the DABUSB device in the kernel image.
> > +	Say 'N' and let it get loaded from userspace.
> 
> Sorry if I missed a discussion on it in the intial firmware threads, but
> what is the point of all these FOO_FIRMWARE options?  I think we should
> include all firmware that we have a driver for if people want firmware
> built-in and non if not.

That makes a certain amount of sense, I suppose, and would certainly
reduce the litter of new _FIRMWARE options, as well as the pointless
whining that some people like to repeat at _each_ patch when we default
them to 'N'. I could do it something like below...

What was the final conclusion on the need to add 'select FW_LOADER'?
Is that going to go away, too?

--- a/firmware/Makefile
+++ b/firmware/Makefile
@@ -48,10 +48,13 @@
-fw-shipped-$(CONFIG_USB_TI_3410_FIRMWARE) += ti_3410.fw
-fw-shipped-$(CONFIG_USB_TI_5052_FIRMWARE) += ti_5052.fw
+fw-shipped-$(CONFIG_USB_TI) += ti_3410.fw ti_5052.fw
-fw-shipped-$(CONFIG_USB_SERIAL_WHITEHEAT_FIRMWARE) += whiteheat_loader.fw \
+fw-shipped-$(CONFIG_USB_SERIAL_WHITEHEAT) += whiteheat_loader.fw \
 		whiteheat.fw # whiteheat_loader_debug.fw
-fw-shipped-$(CONFIG_ATM_AMBASSADOR_FIRMWARE) += atmsar11.fw
+fw-shipped-$(CONFIG_ATM_AMBASSADOR) += atmsar11.fw
-fw-shipped-$(CONFIG_COMPUTONE_FIRMWARE) += intelliport2.bin
+fw-shipped-$(CONFIG_COMPUTONE) += intelliport2.bin
-fw-shipped-$(CONFIG_VIDEO_CPIA2_FIRMWARE) += cpia2/stv0672_vp4.bin
+fw-shipped-$(CONFIG_VIDEO_CPIA2) += cpia2/stv0672_vp4.bin
+
+ifeq ($(CONFIG_INCLUDE_FIRMWARE),n)
+fw-shipped-y := 
+endif
 
 firmware-y    := $(fw-external-y) $(fw-shipped-y)
 firmware-dirs := $(sort $(patsubst %,$(objtree)/$(obj)/%/,$(dir $(firmware-y))))


-- 
dwmw2


  reply	other threads:[~2008-06-23 11:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 11:06 David Woodhouse
2008-06-23 11:20 ` Christoph Hellwig
2008-06-23 11:45   ` David Woodhouse [this message]
2008-06-25 23:01     ` David Woodhouse
2008-06-26 15:55     ` Adrian Bunk
2008-06-27  5:01       ` Greg KH
2008-06-27 12:36         ` Adrian Bunk

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=1214221558.27974.33.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bunk@kernel.org \
    --cc=deti@fliegl.de \
    --cc=hch@infradead.org \
    --cc=jaswinder@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.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

all inboxes | Powered by JetHome®