<br><br><div class="gmail_quote">2011/7/23 pl bossart <span dir="ltr"><<a href="mailto:bossart.nospam@gmail.com">bossart.nospam@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">> When meet Overrun or Underrun, PA will increase watermark. Due to some<br>
> hardware limitation, the hw_ptr will not be updated in PA's request latency.<br>
> So there maybe some cases "faked overrun/underrun". Take capture for<br>
> example, when Pulseaudio was waken up to read new capture data from driver,<br>
> and find the "available" area is much more than the record space. Although<br>
> it's fast enough to read out all data in short time, PA regard that as<br>
> "overrun" and increase watermark/latency step by step, that's really<br>
> useless.<br>
> So attached patch used to avoid such case and only increase<br>
> watermark/latency in real "overrun" case.<br>
<br>
</div></div>Humm, it's not clear what problem you are trying to solve and on what<br>
platform. Looks like a very old MRST firmware/driver?<br>
If your driver doesn't update the hw_ptr, then how can you know if<br>
this is a real or a fake overrun?<br></blockquote><div><br></div><div>In fact it's a solution for such firmware hasing low hw_ptr updating rate. </div><div>Pulseaudio use hw_unused field to track the unused buffer, the real overrun </div>
<div>means the "avail" space is geting close to hwbuf_size. </div><div><br></div><div>--xingchao</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
-Pierre<br>
_______________________________________________<br>
pulseaudio-discuss mailing list<br>
<a href="mailto:pulseaudio-discuss@lists.freedesktop.org">pulseaudio-discuss@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss" target="_blank">http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss</a><br>
</blockquote></div><br>