From: Chris Rankin <rankincj@btinternet.com>
To: crope@iki.fi
Cc: linux-media@vger.kernel.org
Subject: Re: DVB ioctl FE_GET_EVENT behaviour broken in 3.3
Date: Fri, 06 Apr 2012 13:06:09 +0100 [thread overview]
Message-ID: <4F7EDC31.4010001@btinternet.com> (raw)
In-Reply-To: <4F7ED7E9.203@iki.fi>
> Before LOCK you cannot know many parameters at all and frequency also
> can be changed a little bit during tuning process (ZigZag tuning algo).
But surely the point of calling poll() on the front end's descriptor is either
to be notified once the tuning algorithm has locked, or to be told that LOCK has
failed? This would certainly seem to have been xine's assumption for the past
10+ years.
> Could you try to git bisect to find out patch causing that regression?
I don't have a git tree to bisect with, so I expect I'll have to resort to more
"old fashioned" methods.
> I suspect it is some change done for DVB core
Me too, because this bug is affecting *every* DVB adapter that I own. (All USB,
but anyway...)
Cheers,
Chris
next prev parent reply other threads:[~2012-04-06 12:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 23:00 Is xine DVB broken with Linux 3.3.1? Chris Rankin
2012-04-04 23:33 ` Chris Rankin
2012-04-06 10:49 ` DVB ioctl FE_GET_EVENT behaviour broken in 3.3 Chris Rankin
2012-04-06 11:47 ` Antti Palosaari
2012-04-06 12:06 ` Chris Rankin [this message]
2012-04-06 14:59 ` Chris Rankin
2012-04-06 20:06 ` [REGRESSION] Linux 3.3 DVB userspace ABI broken for xine (FE_SET_FRONTEND) Chris Rankin
2012-04-06 20:21 ` [PATCH] " Chris Rankin
2012-04-06 22:38 ` [PATCH v2] " Chris Rankin
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=4F7EDC31.4010001@btinternet.com \
--to=rankincj@btinternet.com \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).