public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Manu Abraham <abraham.manu@gmail.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] DVBFE_SET_PARAMS / delsys from fe_info ioctl ?
Date: Mon, 03 Mar 2008 02:43:33 +0400	[thread overview]
Message-ID: <47CB2D95.6040602@gmail.com> (raw)
In-Reply-To: <20080301161419.GB12800@paradigm.rfc822.org>

Florian Lohoff wrote:
> Hi,
> i was wondering why i have a problem in my application that i need to
> run scan once after loading the module, otherwise my DVBFE_SET_PARAMS
> fails - I couldnt explain it until i looked into the kernel code - In
> the dvb_frontend.c i see this code:
> 
> 1738         case DVBFE_SET_PARAMS: {
> 1739                 struct dvb_frontend_tune_settings fetunesettings;
> 1740                 enum dvbfe_delsys delsys = fepriv->fe_info.delivery;
> ...
> 1783                 } else {
> 1784                         /* default values */
> 1785                         switch (fepriv->fe_info.delivery) {
> ...
> 1817                         default:
> 1818                                 up(&fepriv->sem);
> 1819                                 return -EINVAL;
> 1820                         }
> 
> Should the code use fepriv->feparam.delivery instead of
> fepriv->fe_info.delivery to sense the right delivery system ?

Which demodulator driver are you using to test your application ?

Though a bug, but that won't make any difference to what you are looking at,
since the delay and others are used in the case of swzigzag, which 
doesn't exist
at least for the existing demods using the track() callback at all.

This would be a fix for any demod drivers using the set_params() callback.

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-03-02 22:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01 16:14 [linux-dvb] DVBFE_SET_PARAMS / delsys from fe_info ioctl ? Florian Lohoff
2008-03-02 22:43 ` Manu Abraham [this message]
2008-03-02 23:36   ` Florian Lohoff
2008-03-03  0:22     ` Manu Abraham
2008-03-03  8:52       ` Florian Lohoff
2008-03-03 11:09         ` Manu Abraham
2008-03-03 11:26           ` Florian Lohoff
2008-03-03 12:03             ` Manu Abraham
2008-03-03 13:21               ` Florian Lohoff
2008-03-03 13:41                 ` Manu Abraham
2008-03-03 13:44                   ` Florian Lohoff
2008-03-03 13:55                     ` Manu Abraham
2008-03-03 14:00                       ` Florian Lohoff
2008-03-03 13:49                   ` Manu Abraham
2008-03-03 13:48                     ` Florian Lohoff
2008-03-03 14:04                       ` Manu Abraham
2008-03-03 14:03                         ` Florian Lohoff
2008-03-03 14:17                           ` Manu Abraham
2008-03-03 14:13                             ` Florian Lohoff
2008-03-03 14:24                               ` Manu Abraham
2008-03-03 14:23                                 ` Florian Lohoff
2008-03-03 21:13                 ` Christoph Pfister
2008-03-04  0:52                   ` hermann pitton

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=47CB2D95.6040602@gmail.com \
    --to=abraham.manu@gmail.com \
    --cc=flo@rfc822.org \
    --cc=linux-dvb@linuxtv.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