From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, jaswinder@infradead.org
Subject: Re: [PATCH] ip2: use request_firmware()
Date: Mon, 16 Jun 2008 17:39:54 -0400 [thread overview]
Message-ID: <4856DDAA.1080707@garzik.org> (raw)
In-Reply-To: <20080616212111.406f9c96@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> Extracting the firmware: good
>>
>> Scattering a /single/ driver across multiple directories in the kernel
>> tree: bad
>
> I'd equally argue that putting all the firmware in one place is more
> logical than smearing it around the tree.
Logical for whom? Drivers have always been self-contained... until now.
This separation certainly does not make things _easier_ for users, our
reason for existence. This separation certainly does not make it easier
to drop in a driver with a firmware, i.e. not easier on driver
developers. It is one more PITA detail when copying a driver from one
kernel to another, or shipping the driver out of tree.
There are good reasons why the Makefile rules, Kconfig rules, C source
code and headers for a driver all live together... moving the firmware
elsewhere is strangely, given that a driver simply /does not work/
without the firmware.
I like the goal, but see little effort in the area of "make this
transition painless for users."
Jeff
next prev parent reply other threads:[~2008-06-16 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 9:49 [PATCH] ip2: use request_firmware() David Woodhouse
2008-06-16 10:59 ` Alan Cox
2008-06-16 12:06 ` David Woodhouse
2008-06-16 20:02 ` Jeff Garzik
2008-06-16 19:56 ` Alan Cox
2008-06-16 20:05 ` Jeff Garzik
2008-06-16 19:58 ` Alan Cox
2008-06-16 20:21 ` Jeff Garzik
2008-06-16 20:21 ` Alan Cox
2008-06-16 21:39 ` Jeff Garzik [this message]
2008-06-16 21:34 ` Alan Cox
2008-06-16 22:01 ` David Woodhouse
2008-06-16 20:12 ` Jeff Garzik
2008-06-16 20:00 ` Alan Cox
2008-06-16 20:22 ` Jeff Garzik
2008-06-16 20:21 ` 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=4856DDAA.1080707@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=jaswinder@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.