From: David Woodhouse <dwmw2@infradead.org>
To: Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>,
kernelnewbies <kernelnewbies@nl.linux.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh <jaswinder@infradead.org>,
linux-dvb@linuxtv.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [linux-dvb] [PATCH] Remove fdump tool for av7110 firmware
Date: Sun, 06 Jul 2008 15:48:02 +0100 [thread overview]
Message-ID: <1215355682.3189.101.camel@shinybook.infradead.org> (raw)
In-Reply-To: <412bdbff0807060729o639f98b1s383d146856feb6da@mail.gmail.com>
On Sun, 2008-07-06 at 10:29 -0400, Devin Heitmueller wrote:
> Correct me if I'm wrong, but doesn't this also affect those
> distributions that consider kernels with binary firmware blobs to not
> be free software? Those distributions take the stance that the
> firmware must be loadable by userland, in which case the proposed
> patch removes this capability.
No, it doesn't remove that capability.
We're just observing that the trick which fdump.c uses to turn firmware
into a hex array in C source is obsoleted by the generic ability to
include firmware blobs into the kernel using CONFIG_EXTRA_FIRMWARE. If
we just use the generic method, then the conditional code in the driver
can go away, as can the fdump tool.
Yes, that does mean that it's either in the _kernel_ or in userspace,
rather than being in the .ko file -- but if you want modularity and are
already depending on having a functional userspace, it doesn't seem to
make a lot of sense to have this reimplementation of generic
functionality, just so that you can keep the two parts in _one_ file.
--
dwmw2
next prev parent reply other threads:[~2008-07-06 14:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 12:54 Jaswinder Singh
2008-07-06 1:15 ` [linux-dvb] " Oliver Endriss
2008-07-06 5:04 ` Jaswinder Singh
2008-07-06 9:09 ` Klaus Schmidinger
2008-07-06 11:17 ` David Woodhouse
2008-07-06 14:29 ` Devin Heitmueller
2008-07-06 14:48 ` David Woodhouse [this message]
2008-07-07 2:52 ` Oliver Endriss
2008-07-07 21:02 ` Mauro Carvalho Chehab
2008-07-07 20:45 ` 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=1215355682.3189.101.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=Klaus.Schmidinger@cadsoft.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=devin.heitmueller@gmail.com \
--cc=jaswinder@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-dvb@linuxtv.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
all inboxes | Powered by JetHome®