<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to patches</title><link>https://sourceforge.net/p/mjpg-streamer/patches/</link><description>Recent changes to patches</description><atom:link href="https://sourceforge.net/p/mjpg-streamer/patches/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 09 Mar 2016 21:50:35 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/mjpg-streamer/patches/feed.rss" rel="self" type="application/rss+xml"/><item><title>#16 input_uvc.so refuses to handle symlinks</title><link>https://sourceforge.net/p/mjpg-streamer/patches/16/?limit=25#a8bf</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;See &lt;a href="https://sourceforge.net/p/mjpg-streamer/patches/17/"&gt;https://sourceforge.net/p/mjpg-streamer/patches/17/&lt;/a&gt; - that's a real reason behind symlink handling problems. I successfully use device symlinks after extending devicename buffer.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alno</dc:creator><pubDate>Wed, 09 Mar 2016 21:50:35 -0000</pubDate><guid>https://sourceforge.net655c057d56573fa05679e7c5867786d77379a7ae</guid></item><item><title>Support longer device names</title><link>https://sourceforge.net/p/mjpg-streamer/patches/17/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Current buffer size and name length restriction for device name (12 is a snprintf argument, so real max len is 11) is too short - just enough for names like /dev/video3, but it failes to store longer device names such as /dev/video10 or /dev/video_c270 which may be present in systems with many video devices or custom udev rules.&lt;/p&gt;
&lt;p&gt;Also, the same restriction is a real reason for device symlink problems (as described in &lt;a href="https://sourceforge.net/p/mjpg-streamer/patches/16/"&gt;https://sourceforge.net/p/mjpg-streamer/patches/16/&lt;/a&gt;) as symlinks usually have longer names.&lt;/p&gt;
&lt;p&gt;This patch extends device name buffer size and snprintf call to allow device names up to 31 character, which should be enough for most cases.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alno</dc:creator><pubDate>Wed, 09 Mar 2016 21:48:49 -0000</pubDate><guid>https://sourceforge.net1e062389e7a91e1bfde187271bceb6d68d73f62b</guid></item><item><title>#14 Support 3.16 and 3.17 kernels &amp; then some</title><link>https://sourceforge.net/p/mjpg-streamer/patches/14/?limit=25#72f1</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It seems like the most popular github fork (300+ stars, 150+ forks) is &lt;a href="https://github.com/jacksonliam/mjpg-streamer" rel="nofollow"&gt;https://github.com/jacksonliam/mjpg-streamer&lt;/a&gt; ... seems like it would be good to integrate with that instead. It is missing some of the mjpg-streamer-experimental changes (past October 2012), but it has a lot of good changes too.&lt;br/&gt;
&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dustin Spicuzza</dc:creator><pubDate>Sun, 28 Feb 2016 21:08:12 -0000</pubDate><guid>https://sourceforge.net92873dc7d32e8f8c5783b6308179b314116a5c9c</guid></item><item><title>input_uvc.so refuses to handle symlinks</title><link>https://sourceforge.net/p/mjpg-streamer/patches/16/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;If a symlink to a device is passed to input_uvc.so, mjpg_streamer does not handle it correctly and refuses to start. This is not desirable behavior, as udev rules may be in place to give persistent device names (in the form of symlinks) to multiple attached cameras.&lt;/p&gt;
&lt;p&gt;To fix this, a call to canonicalize_file_name() is needed to resolve the link. I've attached a very minimal patch to do just that, and I am successfully able to compile and run with no warnings.&lt;/p&gt;
&lt;p&gt;Failure cases are handled as well, as init_VideoIn dies gracefully if passed a null from canonicalize_file_name(), which can happen if the user specifies a nonexistent device. Since this would inevitably result in total failure anyway, I don't consider this to be undesirable behavior.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matthew Saunier</dc:creator><pubDate>Fri, 08 May 2015 08:58:28 -0000</pubDate><guid>https://sourceforge.nete6ef6035c7146628dedc74d6d0b88789b7d389a8</guid></item><item><title>Patch for ev3dev linux</title><link>https://sourceforge.net/p/mjpg-streamer/patches/15/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This patch fixes two bugs:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Using NB_BUFFER instead of real number of buffers granted (vd-&amp;gt;rb.count)&lt;br /&gt;
More info &lt;a href="http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-reqbufs.html" rel="nofollow"&gt;http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-reqbufs.html&lt;/a&gt;&lt;br /&gt;
"When the ioctl is called with a pointer to this structure the driver will attempt to allocate the requested number of buffers and it stores the actual number allocated in the count field."&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Using pcontext-&amp;gt;videoIn-&amp;gt;buf.bytesused after buffer has been requeued. It appeares that pcontext-&amp;gt;videoIn-&amp;gt;buf.bytesused value will be 0 after the buffer is requeued. One needs to copy both the buffer content and save buffer size.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andres Kaasik</dc:creator><pubDate>Sun, 21 Dec 2014 12:33:25 -0000</pubDate><guid>https://sourceforge.netc536c383741658e604ad46c8ef662cbe73c511ca</guid></item><item><title>Support 3.16 and 3.17 kernels &amp; then some</title><link>https://sourceforge.net/p/mjpg-streamer/patches/14/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I've imported your SVN tree over on github, maintaining authors as best as I could etc. and added some patches, most recently supporting 3.16 and 3.17 kernels.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/oliv3r/mjpg-streamer" rel="nofollow"&gt;https://github.com/oliv3r/mjpg-streamer/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Pulling this git tree and pushing it to a sourceforge git tree should be without problem ;)&lt;/p&gt;
&lt;p&gt;I'll be adding more patches to clean up the code base and fix issues/improve memory usage.&lt;/p&gt;
&lt;p&gt;Olliver&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Oliver Schinagl</dc:creator><pubDate>Thu, 30 Oct 2014 07:23:51 -0000</pubDate><guid>https://sourceforge.netdce52f46464d1d59b1bef326b390b6359db0b728</guid></item><item><title>#9 timestamp patch - httpd.c.diff</title><link>https://sourceforge.net/p/mjpg-streamer/patches/9/?limit=25#be37</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, exactly the same here.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">johnsmith</dc:creator><pubDate>Mon, 23 Jun 2014 09:10:20 -0000</pubDate><guid>https://sourceforge.net57b473aa45139bff8e546dbb97b6e6e33aac3408</guid></item><item><title>#13 output_cgi plugin: output_http with cgi support</title><link>https://sourceforge.net/p/mjpg-streamer/patches/13/?limit=25#0fcc</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Thank you very much for your contribution!&lt;br /&gt;
A basic CGI functionality had been already added in the experimental branch.&lt;br /&gt;
I have used a different approach, but I like your unbuffered stduot redirection. &lt;/p&gt;
&lt;p&gt;I will do a code cleanup next weekend, include merging the experimental mature features back to the stable branch.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Márton Miklós</dc:creator><pubDate>Sun, 27 Oct 2013 13:18:27 -0000</pubDate><guid>https://sourceforge.net32d59aec722d798f1d73e96f798b9f262756cc76</guid></item><item><title>#13 output_cgi plugin: output_http with cgi support</title><link>https://sourceforge.net/p/mjpg-streamer/patches/13/?limit=25#6880</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I forgot to mention (is there any way to edit tickets?) that it executes any script in the folder (or a subdirectory of the folder) passed as the '-w' parameter, but it could be easily restricted to a subdirectory (like 'cgi-bin'). I'll probably add a '--cgi' parameter that defaults to '/cgi-bin' eventually.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Austin Haigh</dc:creator><pubDate>Sun, 28 Jul 2013 22:29:01 -0000</pubDate><guid>https://sourceforge.net5d0cae6b392bd7d2a7dda1f13098dad594826ae9</guid></item><item><title>output_cgi plugin: output_http with cgi support</title><link>https://sourceforge.net/p/mjpg-streamer/patches/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'm adding cgi to the output_http plugin so it can execute server-side scripts. Right now it's very basic: no extra environment variables are passed to the script (like GET and POST variables), only 1 server can run at a time (but it can run with multiple output_http servers), and there is minimal error checking. Also, if the script handles SIGALRM signals without exiting a script can hang forever (normally SIGALRM is used to kill scripts after a short timeout). That said, it's good enough for its intended purpose, which is to display sensor readings next to a webcam stream.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/austinHaigh/mjpg-streamer-output_cgi" rel="nofollow"&gt;https://github.com/austinHaigh/mjpg-streamer-output_cgi&lt;/a&gt;&lt;br /&gt;
&lt;a href="https://github.com/austinHaigh/mjpg-streamer-output_cgi/archive/master.zip" rel="nofollow"&gt;https://github.com/austinHaigh/mjpg-streamer-output_cgi/archive/master.zip&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Austin Haigh</dc:creator><pubDate>Sun, 28 Jul 2013 22:24:38 -0000</pubDate><guid>https://sourceforge.net958a4acd0a91310820309cfb66cb73b4dea2a8fa</guid></item></channel></rss>