mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaswinder Singh <jaswinder@infradead.org>
To: Oliver Endriss <o.endriss@gmx.de>
Cc: linux-dvb@linuxtv.org, LKML <linux-kernel@vger.kernel.org>,
	kernelnewbies <kernelnewbies@nl.linux.org>,
	kernel-janitors <kernel-janitors@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David Woodhouse <dwmw2@infradead.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [linux-dvb] [PATCH] Remove fdump tool for av7110 firmware
Date: Sun, 06 Jul 2008 10:34:25 +0530	[thread overview]
Message-ID: <1215320665.2768.15.camel@jaswinder.satnam> (raw)
In-Reply-To: <200807060315.51736@orion.escape-edv.de>

Hello Oliver,

On Sun, 2008-07-06 at 03:15 +0200, 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! 

I think you are watching two weeks old patch.

Please check updated patch from :-

http://git.infradead.org/users/dwmw2/firmware-2.6.git?a=commitdiff;h=cf852ae7e54eaf8944e1e734321fa6d5285379f1

And give us your valuable comments.

> This option allows to compile the firmware into the _driver_,

We also compile firmware without fdump.

> which is very useful if you want to test various driver/firmware
> combinations. Having the firmware in the _kernel_ does not help!
> 

For testing purpose kernel/drivers source tree is not suitable.
Please find some other suitable place.

> Well, I am tired to fight for this option in the kernel every other
> month. :-(
> 

yeah I understand, fighting with Truth is not easy ;)

Thank you,

Jaswinder Singh.


  reply	other threads:[~2008-07-06  5:11 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 [this message]
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
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=1215320665.2768.15.camel@jaswinder.satnam \
    --to=jaswinder@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dwmw2@infradead.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=o.endriss@gmx.de \
    /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®