From: David Woodhouse <dwmw2@infradead.org>
To: Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>
Cc: linux-dvb@linuxtv.org, kernelnewbies <kernelnewbies@nl.linux.org>,
kernel-janitors <kernel-janitors@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh <jaswinder@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 12:17:02 +0100 [thread overview]
Message-ID: <1215343022.10393.945.camel@pmac.infradead.org> (raw)
In-Reply-To: <48708BBF.9050400@cadsoft.de>
On Sun, 2008-07-06 at 11:09 +0200, Klaus Schmidinger wrote:
> 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!
That's strange; I've found exactly the opposite to be the case.
If I want to test permutations of driver and firmware, as I've done for
the libertas driver a number of times, I find it _much_ better to
preserve the modularity. I can build each version of the driver and can
test that against various firmware versions without having to rebuild
it, and with much less chance of something going wrong so that I'm not
actually testing what I think I'm testing.
Perhaps I'm missing something that would help me work better? Please
could you help me understand how you currently work, and I'll attempt to
make it easier for you. Can you talk me through an example of a session
where you had to do this testing of 'various driver/firmware
combinations'?
--
dwmw2
next prev parent reply other threads:[~2008-07-06 11:18 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 [this message]
2008-07-06 14:29 ` Devin Heitmueller
2008-07-06 14:48 ` David Woodhouse
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=1215343022.10393.945.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=Klaus.Schmidinger@cadsoft.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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®