On Fri, Jun 26, 2009 at 1:28 PM, Robert Krakora<rob.krakora@xxxxxxxxxxxxxxxxxxxxx> wrote: > Yes, it is run after mplayer initially tunes it. However, what is the > difference between mplayer tuning and v4l-ctl tuning? They are both > submitting the same IOCTLs to the driver to accomplish the same end > result; or is mplayer probably submitting some additional IOCTLS to > "wake" the device? The issue is that the tuner gets powered down when the v4l device is closed. So, when running mplayer first, and then v4l-ctl is being used to tune, the file handle is held active by mplayer. But if you run v4l-ctl first, the v4l-ctl opens the handle, tunes successfully, and then closes the handle (which powers down the tuner). Then when running mplayer (or whatever app), the handle gets reopened but the tuner is not tuned to the target frequency that v4l-ctl set. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
