All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Ralph Metzler <rjkm@metzlerbros.de>, linux-media@vger.kernel.org
Subject: Re: [PATCH 1/2] [media] drxk: Make the QAM demodulator command configurable.
Date: Fri, 29 Jun 2012 13:13:18 -0300	[thread overview]
Message-ID: <4FEDD41E.3000608@redhat.com> (raw)
In-Reply-To: <CAFBinCApTRMdut01wPqT08ViOW=++57UHBY2ok=k=EfQSaEVCQ@mail.gmail.com>

Em 29-06-2012 12:58, Martin Blumenstingl escreveu:
> Hi Ralph,
> 
>> are you sure about this?
>>  From what I have been told, the 2 parameter command is in the
>> firmware ROM and older loadable/patch firmwares.
>> Newer firmwares provided the 4 parameter command.
> The firmwares in the ROM are a good point.
> 
> I discussed with  Mauro Carvalho Chehab before I started writing my patch,
> and he told me that the only (loadable) firmware that uses the old command
> is the "drxk_a3.mc" one.
>
> But you are right, there is some firmware (for DVB-C, afaik it's NOT for DVB-T)
> stored in the ROM.
> 
> If  I find out that the ROM uses the "old" command then I'll probably try
> making this smart:
> old_qam_demod_cmd will be an int with the following possible values:
> * -1: unknown - trial and error approach will be used
> (afterwards this will be updated to either 0 or 1)
> * 0: use the 2-parameter command
> * 1: use the 4-parameter command
> 
> I'll also try to guess a smart default value:
> -1 will be used if no firmware was given.
> Otherwise 0 will be the default.
> The remaining two drxk_config instances that are still using the old
> firmware will be set to 1 (like in my first patch).

I didn't tell "old command", or at least not in the sense of old firmware. I told
that the first drivers (ddbridge and mantis), based on drxk_ac3.mc firmware, use the
4-parameters variant, while the other drivers use the 2-parameters variant.

Anyway, using the name "old" for such parameter is not a good idea. IMHO, you
should use something like qam_demod_needs_4_parameters for this config data,
or, maybe "number_of_qam_demod_parameters".

If number_of_qam_demod_parameters is not 2 or 4, try both ways. So, a device driver
that won't specify it will be auto-probed.

> 
> If everything goes right then I'll be able to test and update my patch tonight.
> 
> Regards,
> Martin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Regards,
Mauro

  reply	other threads:[~2012-06-29 16:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 21:20 [media] drxk: Minor cleanup (basically logging related) Martin Blumenstingl
2012-06-28 21:20 ` [PATCH 1/2] [media] drxk: Make the QAM demodulator command configurable Martin Blumenstingl
2012-06-29  8:31   ` Ralph Metzler
2012-06-29 15:58     ` Martin Blumenstingl
2012-06-29 16:13       ` Mauro Carvalho Chehab [this message]
2012-06-29 16:32         ` Martin Blumenstingl
2012-06-30 22:32   ` [PATCH 1/2] [media] drxk: Make the QAM demodulator command parameters configurable Martin Blumenstingl
2012-06-30 22:32   ` Martin Blumenstingl
2012-07-01  2:46     ` Mauro Carvalho Chehab
2012-07-04 21:36     ` [PATCH 1/2] [media] drxk: Make the QAM demodulator command parameters configurable. [v3] Martin Blumenstingl
2012-07-04 21:36       ` [PATCH 1/2] [media] drxk: Make the QAM demodulator command parameters configurable Martin Blumenstingl
2012-06-28 21:20 ` [PATCH 2/2] [media] drxk: Improve logging Martin Blumenstingl
2012-06-30 22:42   ` [2/2,media] " Martin Blumenstingl
2012-06-30 22:42   ` [PATCH 2/2] [media] " Martin Blumenstingl
2012-07-04 21:38     ` [PATCH 2/2] [media] drxk: Improve logging. [v3] Martin Blumenstingl
2012-07-04 21:38       ` [PATCH 2/2] [media] drxk: Improve logging Martin Blumenstingl

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=4FEDD41E.3000608@redhat.com \
    --to=mchehab@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=rjkm@metzlerbros.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 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.