All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Rémi Cardona" <remi@gentoo.org>
Cc: Antti Palosaari <crope@iki.fi>,
	linux-media@vger.kernel.org,
	Konstantin Dimitrov <kosio.dimitrov@gmail.com>
Subject: Re: [git:v4l-dvb/for_v3.7] [media] ds3000: add module parameter to force firmware upload
Date: Tue, 9 Oct 2012 19:34:45 -0300	[thread overview]
Message-ID: <20121009193445.351aecff@redhat.com> (raw)
In-Reply-To: <1349724224.2142.11.camel@exos>

Em Mon, 08 Oct 2012 21:23:44 +0200
Rémi Cardona <remi@gentoo.org> escreveu:

> Hi Mauro,
> 
> There's indeed a conflict since (as far as I can tell) only patch #6 of
> a 7 patch series was applied.
> 
> The entire patch series is:
>  - http://patchwork.linuxtv.org/patch/14752/
>  - http://patchwork.linuxtv.org/patch/14749/
>  - http://patchwork.linuxtv.org/patch/14753/
>  - http://patchwork.linuxtv.org/patch/14750/
>  - http://patchwork.linuxtv.org/patch/14751/
>  - http://patchwork.linuxtv.org/patch/14747/ (which is somewhat applied)
>  - http://patchwork.linuxtv.org/patch/14748/
> 
> Maybe it would be safer to revert patch #6 to cleanly reapply the entire
> series?

This patch is independent of the other stuff. I don't see a good reason
to revert it.

I'm keeping most of the patches for ds3000 in hold, as this driver should
be broken into two separate drivers. I provided already a feedback on
the patch series that splits this driver. So, I'm waiting for his new
patchset. Only after that change, I'll be handling other patches for ds3000,
as it will make easier to review and understand this driver.

> As for the "force firmware load" patch, the reason for that patch was
> that some cards report already having a firmware (despite having been
> powered off for a while) when in fact they don't. Reloading the ds3000
> module with this new option allows those cards to work properly. Out of
> the thousand S470/471 cards we have in production, only a tiny fraction
> require this option. That's why I didn't change the default behavior.

Wouldn't be better then to add it at the boards configuration, instead of
using a modprobe parameter?

Regards,
Mauro

      reply	other threads:[~2012-10-09 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 19:23 [git:v4l-dvb/for_v3.7] [media] ds3000: add module parameter to force firmware upload Rémi Cardona
2012-10-09 22:34 ` Mauro Carvalho Chehab [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=20121009193445.351aecff@redhat.com \
    --to=mchehab@redhat.com \
    --cc=crope@iki.fi \
    --cc=kosio.dimitrov@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=remi@gentoo.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.