From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
To: linux-dvb@linuxtv.org
Cc: kernelnewbies <kernelnewbies@nl.linux.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh <jaswinder@infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [linux-dvb] [PATCH] Remove fdump tool for av7110 firmware
Date: Sun, 06 Jul 2008 09:09:19 +0000 [thread overview]
Message-ID: <48708BBF.9050400@cadsoft.de> (raw)
In-Reply-To: <200807060315.51736@orion.escape-edv.de>
On 07/06/08 03:15, Oliver Endriss wrote:
> Jaswinder Singh wrote:
>> There's no point in this, since the user can use the BUILTIN_FIRMWARE
>> option to include arbitrary firmware files directly in the kernel image.
>
> NAK! This option allows to compile the firmware into the _driver_,
> which is very useful if you want to test various driver/firmware
> combinations. Having the firmware in the _kernel_ does not help!
I strongly support Oliver's request!
Working with various driver versions is much easier with the
firmware compiled into the driver!
Klaus
> Well, I am tired to fight for this option in the kernel every other
> month. :-(
>
> @Mauro:
> Is there a way to strip this stuff from Kconfig/Makefile/av7110*.[ch]
> for submission to the kernel? Basically I don't care whether and how
> they cripple the driver in the kernel. But I would like to keep the code
> 'as is' in the linuxtv repositories.
>
> CU
> Oliver
WARNING: multiple messages have this Message-ID (diff)
From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
To: linux-dvb@linuxtv.org
Cc: kernelnewbies <kernelnewbies@nl.linux.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh <jaswinder@infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [linux-dvb] [PATCH] Remove fdump tool for av7110 firmware
Date: Sun, 06 Jul 2008 11:09:19 +0200 [thread overview]
Message-ID: <48708BBF.9050400@cadsoft.de> (raw)
In-Reply-To: <200807060315.51736@orion.escape-edv.de>
On 07/06/08 03:15, Oliver Endriss wrote:
> Jaswinder Singh wrote:
>> There's no point in this, since the user can use the BUILTIN_FIRMWARE
>> option to include arbitrary firmware files directly in the kernel image.
>
> NAK! This option allows to compile the firmware into the _driver_,
> which is very useful if you want to test various driver/firmware
> combinations. Having the firmware in the _kernel_ does not help!
I strongly support Oliver's request!
Working with various driver versions is much easier with the
firmware compiled into the driver!
Klaus
> Well, I am tired to fight for this option in the kernel every other
> month. :-(
>
> @Mauro:
> Is there a way to strip this stuff from Kconfig/Makefile/av7110*.[ch]
> for submission to the kernel? Basically I don't care whether and how
> they cripple the driver in the kernel. But I would like to keep the code
> 'as is' in the linuxtv repositories.
>
> CU
> Oliver
WARNING: multiple messages have this Message-ID (diff)
From: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
To: linux-dvb@linuxtv.org
Cc: kernelnewbies <kernelnewbies@nl.linux.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh <jaswinder@infradead.org>,
David Woodhouse <dwmw2@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [linux-dvb] [PATCH] Remove fdump tool for av7110 firmware
Date: Sun, 06 Jul 2008 11:09:19 +0200 [thread overview]
Message-ID: <48708BBF.9050400@cadsoft.de> (raw)
In-Reply-To: <200807060315.51736@orion.escape-edv.de>
On 07/06/08 03:15, Oliver Endriss wrote:
> Jaswinder Singh wrote:
>> There's no point in this, since the user can use the BUILTIN_FIRMWARE
>> option to include arbitrary firmware files directly in the kernel image.
>
> NAK! This option allows to compile the firmware into the _driver_,
> which is very useful if you want to test various driver/firmware
> combinations. Having the firmware in the _kernel_ does not help!
I strongly support Oliver's request!
Working with various driver versions is much easier with the
firmware compiled into the driver!
Klaus
> Well, I am tired to fight for this option in the kernel every other
> month. :-(
>
> @Mauro:
> Is there a way to strip this stuff from Kconfig/Makefile/av7110*.[ch]
> for submission to the kernel? Basically I don't care whether and how
> they cripple the driver in the kernel. But I would like to keep the code
> 'as is' in the linuxtv repositories.
>
> CU
> Oliver
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-07-06 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 12:54 [PATCH] Remove fdump tool for av7110 firmware Jaswinder Singh
2008-06-22 13:06 ` Jaswinder Singh
2008-06-22 12:54 ` [linux-dvb] " Jaswinder Singh
2008-07-06 1:15 ` Oliver Endriss
2008-07-06 1:15 ` Oliver Endriss
2008-07-06 5:04 ` Jaswinder Singh
2008-07-06 5:16 ` Jaswinder Singh
2008-07-06 9:09 ` Klaus Schmidinger [this message]
2008-07-06 9:09 ` Klaus Schmidinger
2008-07-06 9:09 ` Klaus Schmidinger
2008-07-06 11:17 ` David Woodhouse
2008-07-06 11:17 ` David Woodhouse
2008-07-06 11:17 ` David Woodhouse
2008-07-06 14:29 ` Devin Heitmueller
2008-07-06 14:29 ` Devin Heitmueller
2008-07-06 14:29 ` Devin Heitmueller
2008-07-06 14:48 ` David Woodhouse
2008-07-06 14:48 ` David Woodhouse
2008-07-06 14:48 ` David Woodhouse
2008-07-07 2:52 ` Oliver Endriss
2008-07-07 2:52 ` Oliver Endriss
2008-07-07 2:52 ` Oliver Endriss
2008-07-07 21:02 ` Mauro Carvalho Chehab
2008-07-07 21:02 ` Mauro Carvalho Chehab
2008-07-07 21:02 ` Mauro Carvalho Chehab
2008-07-07 20:45 ` Alan Cox
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=48708BBF.9050400@cadsoft.de \
--to=klaus.schmidinger@cadsoft.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--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 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.