From: <tp...@ke...> - 2006-07-19 16:29:32
|
CVS Root: /cvs/gstreamer Module: gstreamer Changes by: tpm Date: Wed Jul 19 2006 12:41:06 UTC Log message: * docs/pwg/advanced-scheduling.xml: * gst/gstpad.c: Fix typos (#348000). Modified files: . : ChangeLog docs/pwg : advanced-scheduling.xml gst : gstpad.c Links: http://freedesktop.org/cgi-bin/viewcvs.cgi/gstreamer/gstreamer/ChangeLog.diff?r1=1.2680&r2=1.2681 http://freedesktop.org/cgi-bin/viewcvs.cgi/gstreamer/gstreamer/docs/pwg/advanced-scheduling.xml.diff?r1=1.10&r2=1.11 http://freedesktop.org/cgi-bin/viewcvs.cgi/gstreamer/gstreamer/gst/gstpad.c.diff?r1=1.519&r2=1.520 ====Begin Diffs==== Index: ChangeLog =================================================================== RCS file: /cvs/gstreamer/gstreamer/ChangeLog,v retrieving revision 1.2680 retrieving revision 1.2681 diff -u -d -r1.2680 -r1.2681 --- ChangeLog 18 Jul 2006 20:38:45 -0000 1.2680 +++ ChangeLog 19 Jul 2006 12:40:54 -0000 1.2681 @@ -1,3 +1,9 @@ +2006-07-19 Tim-Philipp Müller <tim at centricular dot net> + + * docs/pwg/advanced-scheduling.xml: + * gst/gstpad.c: + Fix typos (#348000). 2006-07-18 Tim-Philipp Müller <tim at centricular dot net> * docs/pwg/intro-basics.xml: Index: advanced-scheduling.xml RCS file: /cvs/gstreamer/gstreamer/docs/pwg/advanced-scheduling.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -d -r1.10 -r1.11 --- advanced-scheduling.xml 19 Jan 2006 10:39:27 -0000 1.10 +++ advanced-scheduling.xml 19 Jul 2006 12:40:54 -0000 1.11 @@ -3,7 +3,7 @@ <para> Scheduling is, in short, a method for making sure that every element gets called once in a while to process data and prepare data for the next - element. Likewise, a kernel has a scheduler to for processes, and your + element. Likewise, a kernel has a scheduler for processes, and your brain is a very complex scheduler too in a way. Randomly calling elements' chain functions won't bring us far, however, so you'll understand that the schedulers in &GStreamer; are a bit more complex @@ -11,8 +11,8 @@ </para> So far, we have only discussed <function>_chain ()</function>-operating - elements, i.e. elements that have a chain-function set on their sinkpad - and push buffers on their sinkpad. Pads (or elements) can also operate + elements, i.e. elements that have a chain-function set on their sink pad + and push buffers on their source pad(s). Pads (or elements) can also operate in two other scheduling modes, however. In this chapter, we will discuss what those scheduling modes are, how they can be enabled and in what cases they are useful. The other two scheduling modes are random access Index: gstpad.c RCS file: /cvs/gstreamer/gstreamer/gst/gstpad.c,v retrieving revision 1.519 retrieving revision 1.520 diff -u -d -r1.519 -r1.520 --- gstpad.c 11 Jul 2006 16:20:09 -0000 1.519 +++ gstpad.c 19 Jul 2006 12:40:54 -0000 1.520 @@ -1622,7 +1622,7 @@ * This check is required so that we don't try to link * pads from elements in different bins without ghostpads. * - * The LOCK should be helt on both pads + * The LOCK should be held on both pads */ static gboolean gst_pad_link_check_hierarchy (GstPad * src, GstPad * sink) @@ -3111,7 +3111,7 @@ #endif /* GST_DISABLE_LOADSAVE */ /* - * should be called with pad OBJECT_LOCK and STREAM_LOCK helt. + * should be called with pad OBJECT_LOCK and STREAM_LOCK held. * GST_PAD_IS_BLOCK (pad) == TRUE when this function is * called. @@ -3125,7 +3125,7 @@ * Two methods are available for notifying the application of the * block: * - the callback method, which happens in the STREAMING thread with - * the STREAM_LOCK helt. With this method, the most usefull way of + * the STREAM_LOCK held. With this method, the most usefull way of * dealing with the callback is to post a message to the main thread * where the pad block can then be handled outside of the streaming * thread. With the last method one can perform all operations such |