From: Andreas Oberritter <obi@linuxtv.org>
To: Chris Rankin <rankincj@yahoo.com>
Cc: linux-media@vger.kernel.org, Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: Is DVB ioctl FE_SET_FRONTEND broken?
Date: Fri, 26 Aug 2011 14:13:21 +0200 [thread overview]
Message-ID: <4E578DE1.80706@linuxtv.org> (raw)
In-Reply-To: <1314358307.50448.YahooMailClassic@web121706.mail.ne1.yahoo.com>
On 26.08.2011 13:31, Chris Rankin wrote:
> --- On Fri, 26/8/11, Andreas Oberritter <obi@linuxtv.org> wrote:
>> I first thought that you were talking about a
>> regression in Linux 3.0.x.
>
> Heh, yes and no. I am talking about a regression that I am definitely seeing in 3.0.x. However, I cannot say which kernel the problem first appeared in.
[...]
> Debugging the problem has shown that the first event received after a FE_SET_FRONTEND ioctl() has frequency == 0, which is considered an error.
OK, this is actually the problem, which the proposed patch tries to
address: https://patchwork.kernel.org/patch/1036132/
What you're observing is the stale data mentioned in the patch
description. You should definitely try the patch.
>> Yes. The patch is restoring a different old behaviour. The
>> behaviour you're referring to has never been in the kernel. ;-)
>
> Yikes! Documentation bug, anyone?
Large parts of the documentation haven't been updated since about 10
years, besides some renamed enums and functions here and there, when it
was merged into Linux 2.5. Contributions are welcome, of course.
Regards,
Andreas
prev parent reply other threads:[~2011-08-26 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 23:27 Is DVB ioctl FE_SET_FRONTEND broken? Chris Rankin
2011-08-25 23:43 ` Andreas Oberritter
2011-08-26 8:50 ` Chris Rankin
2011-08-26 9:49 ` Andreas Oberritter
2011-08-26 11:31 ` Chris Rankin
2011-08-26 12:13 ` Andreas Oberritter [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=4E578DE1.80706@linuxtv.org \
--to=obi@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rankincj@yahoo.com \
/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.