From: Adrian Bunk <bunk@stusta.de>
To: Oliver Endriss <o.endriss@gmx.de>
Cc: v4l-dvb-maintainer@linuxtv.org,
Trent Piepho <xyzzy@speakeasy.org>,
linux-kernel@vger.kernel.org
Subject: Re: [v4l-dvb-maintainer] [2.6 patch] remove DVB_AV7110_FIRMWARE
Date: Fri, 1 Dec 2006 13:34:38 +0100 [thread overview]
Message-ID: <20061201123437.GA11084@stusta.de> (raw)
In-Reply-To: <200611300158.32934@orion.escape-edv.de>
On Thu, Nov 30, 2006 at 01:58:32AM +0100, Oliver Endriss wrote:
> Adrian Bunk wrote:
> > On Tue, Nov 28, 2006 at 08:45:56PM -0800, Trent Piepho wrote:
> > > On Wed, 29 Nov 2006, Adrian Bunk wrote:
> > > > On Tue, Nov 28, 2006 at 01:06:02PM -0800, Trent Piepho wrote:
> > > > > On Sun, 26 Nov 2006, Adrian Bunk wrote:
> > > > > > DVB_AV7110_FIRMWARE was (except for some OSS drivers) the only option
> > > > > > that was still compiling a binary-only user-supplied firmware file at
> > > > > > build-time into the kernel.
> > > > > >
> > > > > > This patch changes the driver to always use the standard
> > > > > > request_firmware() way for firmware by removing DVB_AV7110_FIRMWARE.
> > > > >
> > > > > Doesn't this also prevent the AV7110 module from getting compiled
> > > > > into the kernel? Shouldn't the Kconfig file be adjusted so
> > > > > that 'y' can't be selected anymore and it depends on MODULES?
> > > >
> > > > No.
> > > > No.
> > > >
> > > > request_firmware() works fine for built-in drivers.
> > >
> > > Wouldn't that require loading the firmware file before the filesystems are
> > > mounted?
> >
> > Sure.
>
> And you have to create an initrd for the firmware!
>
> As I wrote before:
> I NAK any attempt to remove this option.
>
> The option _is_ useful because it allows a user to build an av7110 driver
> without hotplug, initrd etc.
>
> Nobody has to use this option, but it should be possible to do so.
Sorry, but the direction of kernel development is to replace statically
into the kernel compiled firmware (that also brings some non-trivial
legal questions - is distributing such a kernel a violation of the GPL?)
with request_firmware().
> CU
> Oliver
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2006-12-01 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 0:45 [2.6 patch] remove DVB_AV7110_FIRMWARE Adrian Bunk
2006-11-28 21:06 ` [v4l-dvb-maintainer] " Trent Piepho
2006-11-29 3:06 ` Adrian Bunk
2006-11-29 4:45 ` Trent Piepho
2006-11-29 5:07 ` Adrian Bunk
2006-11-30 0:58 ` Oliver Endriss
2006-12-01 12:34 ` Adrian Bunk [this message]
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=20061201123437.GA11084@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=o.endriss@gmx.de \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=xyzzy@speakeasy.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