Re: DVB ioctl FE_GET_EVENT behaviour broken in 3.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux