<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Hell Labs &#187; en</title>
	<atom:link href="http://helllabs.org/blog/category/en/feed" rel="self" type="application/rss+xml" />
	<link>http://helllabs.org/blog</link>
	<description>Go to heaven for the climate, hell for the company</description>
	<pubDate>Fri, 27 Jun 2008 00:04:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Grüner Tee</title>
		<link>http://helllabs.org/blog/20080626/gruner-tee/</link>
		<comments>http://helllabs.org/blog/20080626/gruner-tee/#comments</comments>
		<pubDate>Thu, 26 Jun 2008 21:31:37 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[en]]></category>

		<category><![CDATA[toomuchfreetime]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/?p=82</guid>
		<description><![CDATA[No, I am your father is so lame. Green tea is much better.
	
	
	
	7 comments
	]]></description>
			<content:encoded><![CDATA[<p><a href="http://noiamyourfather.org/">No, I am your father</a> is so lame. <a href="http://helllabs.org/greentea/">Green tea</a> is much better.</p>
	<p></p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080626/gruner-tee/#comments">7 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080626/gruner-tee/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Killing a stuck nash-hotplug</title>
		<link>http://helllabs.org/blog/20080313/killing-a-stuck-nash-hotplug/</link>
		<comments>http://helllabs.org/blog/20080313/killing-a-stuck-nash-hotplug/#comments</comments>
		<pubDate>Thu, 13 Mar 2008 03:00:41 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[eeepc]]></category>

		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[patch]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20080313/killing-a-stuck-nash-hotplug/</guid>
		<description><![CDATA[&#8220;What is nash-hotplug and why is it consuming 100% CPU?&#8220;, someone asked in a Xen-related message I found after experiencing similar problems booting Mandriva 2008.1 with finit in the Asus Eeepc. This situation seems to be especially common in different Linux distributions running as Xen guests and the usual advice is to just kill nash-plugin [...]]]></description>
			<content:encoded><![CDATA[<p>&#8220;<a href="http://forums.vpslink.com/showthread.php?t=2466">What is nash-hotplug and why is it consuming 100% CPU?</a>&#8220;, someone asked in a Xen-related message I found after experiencing similar problems booting Mandriva 2008.1 with <a href="http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/">finit</a> in the Asus Eeepc. This situation seems to be especially common in different Linux distributions running as Xen guests and the usual advice is to <a href="http://www.mail-archive.com/fedora-xen@redhat.com/msg00214.html">just</a> <a href="http://www.darkrune.org/blog/?p=154">kill</a> <a href="http://lynema.com/2007/04/18/some-more-xen-caveats">nash-plugin</a> after the system boots. Instead of doing that ugly workaround, we decided to investigate and find out what&#8217;s happening. Whatever nash-hotplug is supposed to do, I can&#8217;t say it keeps running consuming 100% of your cpu because it&#8217;s a well-written program (notice the bizarre IPC protocol, how it tries to read from a descriptor after closing it and how easily it can get trapped in infinite loops). Use the following quick fix to avoid the problem.</p>
<ul>
<li><a href="/patch/20080312_mkinitrd/mkinitrd-6.0.34-nash-hotplug.patch">mkinitrd-6.0.34-nash-hotplug.patch</a>
</ul>
<p>Die, nash, die.</p>
	<p></p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080313/killing-a-stuck-nash-hotplug/#comments">2 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080313/killing-a-stuck-nash-hotplug/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Cloudbook screen, wifi and boot issues</title>
		<link>http://helllabs.org/blog/20080222/cloudbook-screen-wifi-and-boot-issues/</link>
		<comments>http://helllabs.org/blog/20080222/cloudbook-screen-wifi-and-boot-issues/#comments</comments>
		<pubDate>Fri, 22 Feb 2008 11:45:43 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[cloudbook]]></category>

		<category><![CDATA[eeepc]]></category>

		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20080222/cloudbook-screen-wifi-and-boot-issues/</guid>
		<description><![CDATA[Having read the (not so enthusiastic) reviews of the first Cloudbook users, it seems that most software-related complaints of early Cloudbookers revolve around screen resolution, wifi performance and slow boot. While I offer no ready-to-use solution for these problems, here are some pointers that could help hobbyists or desperate users:

VIA video of course won&#8217;t run [...]]]></description>
			<content:encoded><![CDATA[<p>Having read the (not so enthusiastic) reviews of the first <a href="http://www.umpcportal.com/products/product.php?id=167">Cloudbook</a> users, it seems that most software-related complaints of early Cloudbookers revolve around <a href="http://blog.laptopmag.com/cloudbook-blows-so-far">screen resolution</a>, <a href="http://forum.cloudbooker.com/viewtopic.php?id=197">wifi performance</a> and <a href="http://blog.laptopmag.com/cloudbook-takes-almost-3-minutes-to-boot">slow boot</a>. While I offer no ready-to-use solution for these problems, here are some pointers that could help hobbyists or desperate users:</p>
<ul>
<li>VIA video of course won&#8217;t run with <a href="http://www.intel.com/design/intarch/swsup/graphics_faq.htm">IEGD</a>, but the (somewhat ugly) <a href="http://forum.eeeuser.com/viewtopic.php?id=14588&#038;p=1">VNC-based hack</a> for the Eeepc could work. <a href="http://helllabs.org/blog/20080214/thoughts-on-eeepc-screen-rescaling/">X compositing or RandR</a> could work depending on 3D performance, availability of RandR 1.2 for VIA graphic chips and quality compromises, but both solutions require development (i.e. possible but not available yet).
<li>Wifi performance issues may be related to <a href="http://www.spinics.net/lists/linux-wireless/msg07541.html">RTL8187 rate control</a> not working properly (it always tries to use the highest possible bitrate reducing range dramatically). Using a recent Windows driver with ndiswrapper should solve most problems, or reducing the bitrate manually should increase range using the native driver.
<li>Faster boot can be achived using <a href="http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/">finit</a> (a reimplementation of the Eeepc fastinit), but some customization to finit-alt will be necessary to boot Ubuntu.
</ul>
<p>On a side note, finit-alt worked quite well booting Mandriva 2008 with Enlightenment in the <a href="http://www.pioneercomputers.com.au/products/info.asp?c1=3&#038;c2=12&#038;id=2458">Dreambook IL1</a>, another VIA-based mini-laptop (possibly booting even faster than the Eeepc because the Intel driver for Xorg takes a while to initialize).</p>
	<p></p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080222/cloudbook-screen-wifi-and-boot-issues/#comments">No comment</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080222/cloudbook-screen-wifi-and-boot-issues/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Thoughts on Eeepc screen rescaling</title>
		<link>http://helllabs.org/blog/20080214/thoughts-on-eeepc-screen-rescaling/</link>
		<comments>http://helllabs.org/blog/20080214/thoughts-on-eeepc-screen-rescaling/#comments</comments>
		<pubDate>Fri, 15 Feb 2008 01:38:04 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[eeepc]]></category>

		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20080214/thoughts-on-eeepc-screen-rescaling/</guid>
		<description><![CDATA[While I was updating the fastinit reimplementation with Metalshark&#8217;s patches, rallying enthusiast and Eeepc owner Ednilson Miura pointed me to a discussion in EeeUser about increasing screen resolution of the Eeepc display, basically by scaling down a higher resolution desktop to the native 800&#215;480 Eeepc display. We&#8217;ve seen different approaches to solve the low resolution [...]]]></description>
			<content:encoded><![CDATA[<p>While I was updating the <a href="http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/">fastinit reimplementation</a> with Metalshark&#8217;s patches, rallying enthusiast and Eeepc owner <a href="http://www.rallyzeiros.com.br/joomla/index.php?option=com_gallery2&#038;Itemid=27">Ednilson Miura</a> pointed me to a discussion in <a href="http://www.eeeuser.com">EeeUser</a> about <a href="http://forum.eeeuser.com/viewtopic.php?id=14588&#038;p=1">increasing screen resolution</a> of the Eeepc display, basically by scaling down a higher resolution desktop to the native 800&#215;480 Eeepc display. We&#8217;ve seen different approaches to solve the low resolution problem, from the traditional viewport to a larger virtual desktop to real screen rescaling (Intel has a driver-based rescaler for its <a href="http://en.wikipedia.org/wiki/Classmate_PC">Classmate PC</a>, and there are similar resampling technologies used in other manufacturers with Eeepc-similar offerings usually with quality ranging from barely readable to unreadable). The aforementioned discussion presents a somewhat novel approach: a VNC connection to the local host. I think we could get a similar effect with a more elegant and less resource-intensive solution: X compositing. It would also be one of the first non-frivolous utilities for desktop compositing, previously used almost only for eye-candy. RandR and driver-based rescaling approaches are also discussed below.</p>
<p></p>
	<p>(...)<br/>Read the rest of <a href="http://helllabs.org/blog/20080214/thoughts-on-eeepc-screen-rescaling/">Thoughts on Eeepc screen rescaling</a> (573 words)</p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080214/thoughts-on-eeepc-screen-rescaling/#comments">3 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080214/thoughts-on-eeepc-screen-rescaling/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Eeepc fastinit reimplementation update</title>
		<link>http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/</link>
		<comments>http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/#comments</comments>
		<pubDate>Tue, 05 Feb 2008 13:51:42 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[eeepc]]></category>

		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/</guid>
		<description><![CDATA[There is a number of updates in the Eeepc fastinit reimplementation that you might be interested in:

It works, as confirmed by Eeepc users that tested the program.
Metalshark fixed a bug in the reimplementation that prevented it to load the shutdown splash screen.
Kept finit.c as an accurate reimplementation of the original Eeepc fastinit, and spawned finit-mod.c [...]]]></description>
			<content:encoded><![CDATA[<p>There is a number of updates in the <a href="http://helllabs.org/blog/20071231/asus-eeepc-fastinit-reimplementation/">Eeepc fastinit reimplementation</a> that you might be interested in:</p>
<ul>
<li>It works, as confirmed by Eeepc users that tested the program.
<li>Metalshark fixed a bug in the reimplementation that prevented it to load the shutdown splash screen.
<li>Kept <em>finit.c</em> as an accurate reimplementation of the original Eeepc fastinit, and spawned <em>finit-mod.c</em> as a modified/optimized version intended to be a drop-in replacement for fastinit. A third version, <em>finit-alt.c</em>, contains changes to allow alternative Linux distributions to boot in the Eeepc (currently supports Mandriva 2008).
</ul>
<p>Read on for details and results of booting Mandriva 2008 on a regular (non-Eeepc) laptop using finit-alt.</p>
<p></p>
	<p>(...)<br/>Read the rest of <a href="http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/">Eeepc fastinit reimplementation update</a> (238 words)</p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/#comments">51 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080205/eeepc-fastinit-reimplementation-update/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Fix for VC0323 webcam</title>
		<link>http://helllabs.org/blog/20080204/fix-for-vc0323-webcam/</link>
		<comments>http://helllabs.org/blog/20080204/fix-for-vc0323-webcam/#comments</comments>
		<pubDate>Mon, 04 Feb 2008 13:30:02 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[patch]]></category>

		<category><![CDATA[webcam]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20080204/fix-for-vc0323-webcam/</guid>
		<description><![CDATA[Last week I came across a no-brand, very cheap-looking USB webcam with id 0ac8:0323 and recognized by Linux as a &#8220;Z-Star Microelectronics Corp. Luxya WC-1200 USB 2.0 Webcam&#8221;, which seems to be misleading in this case.

From the USB ID it is supposed to contain a Vimicro VC0323 controller, and it was recognized as so by [...]]]></description>
			<content:encoded><![CDATA[<p>Last week I came across a no-brand, very cheap-looking USB webcam with id 0ac8:0323 and recognized by Linux as a &#8220;Z-Star Microelectronics Corp. Luxya WC-1200 USB 2.0 Webcam&#8221;, which seems to be misleading in this case.</p>
<p><img class="centered" src='http://helllabs.org/blog/wp-content/uploads/2008/02/vc0323-webcam.jpg' alt='vc0323-webcam.jpg' /></p>
<p>From the USB ID it is supposed to contain a <a href="http://www.vimicro.com/english/product/d_vc0323.htm#">Vimicro VC0323</a> controller, and it was recognized as so by the <a href="http://mxhaard.free.fr/">GSPCA</a> driver. This camera, however, seems to have a number of quirks that cause the driver to <a href='http://helllabs.org/blog/wp-content/uploads/2008/02/vc0323.png' alt='vc0323.png'/>decode the image incorrectly</a>: the image is fed as YUV instead of Jpeg (like the VC0321), image start offset is different from what the driver expects for VC0323 or VC0321, and finally the sensor appears to be mounted upside-down inside the camera. Read on for fix details and GSPCA patches.</p>
<p></p>
	<p>(...)<br/>Read the rest of <a href="http://helllabs.org/blog/20080204/fix-for-vc0323-webcam/">Fix for VC0323 webcam</a> (158 words)</p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080204/fix-for-vc0323-webcam/#comments">7 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080204/fix-for-vc0323-webcam/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Codecgraph</title>
		<link>http://helllabs.org/blog/20080116/codecgraph/</link>
		<comments>http://helllabs.org/blog/20080116/codecgraph/#comments</comments>
		<pubDate>Wed, 16 Jan 2008 23:15:02 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[alsa]]></category>

		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20080116/codecgraph/</guid>
		<description><![CDATA[For those interested in Linux HDA sound troubleshooting, Eduardo Habkost&#8217;s Codecgraph tool finally gains a tarball and page.

Codecgraph is a tool to generate a graph based on the ALSA description of a  High Definition Audio codec. The generated graph depicts the HDA codec layout and node connections, helping driver troubleshooting and maintenance. Codecgraph&#8217;s parser [...]]]></description>
			<content:encoded><![CDATA[<p>For those interested in Linux HDA sound troubleshooting, Eduardo Habkost&#8217;s <a href="http://helllabs.org/codecgraph/">Codecgraph tool</a> finally gains a tarball and page.</p>
<blockquote><p>
Codecgraph</em> is a tool to generate a graph based on the <a href="http://alsa-project.org/">ALSA</a> description of a <a href="http://www.intel.com/design/chipsets/hdaudio.htm"> High Definition Audio</a> codec. The generated graph depicts the HDA codec layout and node connections, helping driver troubleshooting and maintenance. Codecgraph&#8217;s parser reads the codec description from <tt>/proc/asound/card*/codec#0</tt> and parsed data is sent to <a href="http://graphviz.org">Graphviz</a> for actual graph generation.
</p></blockquote>
<p>I mentioned codecgraph before as the tool used to fix 5.1 sound in six and threestack ALC888-based HP systems, and recently it was used to fix 5.1/7.1 sound in the <a href="http://helllabs.org/blog/20080114/alsa-patch-for-dell-inspiron-530/">Dell Inspiron 530</a>.</p>
	<p></p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080116/codecgraph/#comments">One comment</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080116/codecgraph/feed/</wfw:commentRss>
		</item>
		<item>
		<title>ALSA patch for Dell Inspiron 530</title>
		<link>http://helllabs.org/blog/20080114/alsa-patch-for-dell-inspiron-530/</link>
		<comments>http://helllabs.org/blog/20080114/alsa-patch-for-dell-inspiron-530/#comments</comments>
		<pubDate>Mon, 14 Jan 2008 22:57:50 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[alsa]]></category>

		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[patch]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20080114/alsa-patch-for-dell-inspiron-530/</guid>
		<description><![CDATA[On New Year&#8217;s Eve a loose heatsink fried my old Asus motherboard northbridge, so I replaced the entire system with a nice and inexpensive Dell Inspiron 530. It&#8217;s a G33/ICH9-based system, which runs almost out-of-the box with Linux 2.6.23, except for the ethernet controller (you&#8217;ll need an upgraded e1000 driver from Intel) and HDA sound [...]]]></description>
			<content:encoded><![CDATA[<p>On New Year&#8217;s Eve a loose heatsink fried my old Asus motherboard northbridge, so I replaced the entire system with a nice and inexpensive Dell Inspiron 530. It&#8217;s a G33/ICH9-based system, which runs almost out-of-the box with Linux 2.6.23, except for the ethernet controller (you&#8217;ll need an upgraded <a href="http://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/9180/eng/e1000-7.6.12.tar.gz&#038;agr=&#038;ProductID=838&#038;DwnldId=9180&#038;strOSs=&#038;OSFullName=&#038;lang=eng">e1000 driver</a> from Intel) and HDA sound (multichannel and headphone detection not working). Use the following ALSA patch to fix both sound problems:</p>
<ul>
<li><a href="/patch/20080113_alsa/0001-Fix-5.1-sound-in-Dell-6stack-ALC888-HDA.patch">Hg patch for alsa-kernel</a>: fixes 5.1 sound and headphone detection in the Dell Inspiron 530
<li><a href="/patch/20080113_alsa/linux-2.6.23.12-sound-hda-dell.patch">Patch  for Linux 2.6.23.12</a>: same patch as above, backported to Linux 2.6.23.12
</ul>
<p>It adds the ALC888 6stack-dell mode for the Inspiron 530 and hopefully for other Dell systems based on the ALC888. The patch has already been submited upstream and should show up in the next kernel version. The patch has also been added to the current Mandriva Cooker kernel.</p>
	<p></p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20080114/alsa-patch-for-dell-inspiron-530/#comments">4 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20080114/alsa-patch-for-dell-inspiron-530/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Asus Eeepc fastinit reimplementation</title>
		<link>http://helllabs.org/blog/20071231/asus-eeepc-fastinit-reimplementation/</link>
		<comments>http://helllabs.org/blog/20071231/asus-eeepc-fastinit-reimplementation/#comments</comments>
		<pubDate>Mon, 31 Dec 2007 11:58:04 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[code]]></category>

		<category><![CDATA[eeepc]]></category>

		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[reverseengineer]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20071231/asus-eeepc-fastinit-reimplementation/</guid>
		<description><![CDATA[Slow booting plagues most Linux distributions today, and while this is not a such big issue for systems that are booted once a year, it becomes an annoyance in laptops or other computers you initialize every day. Different solutions for this problem have been proposed, but booting of a typical Linux system today still takes [...]]]></description>
			<content:encoded><![CDATA[<p>Slow booting plagues most Linux distributions today, and while this is not a such big issue for systems that are booted once a year, it becomes an annoyance in laptops or other computers you initialize every day. Different solutions for this problem have been proposed, but booting of a typical Linux system today still takes too much time. It has been said that the <a href="http://en.wikipedia.org/wiki/Eeepc">Asus Eeepc</a> boots remarkably faster than regular Linux distributions, thanks to its &#8220;fastinit&#8221; system initialization program. A quick analysis of its workings shows what it essentally does, and it&#8217;s quite obvious: start the user interface as fast as possible, and initialize the rest later.  A more detailed analysis allowed us to rewrite it, and even find a couple of bugs in the original code.</p>
<p></p>
	<p>(...)<br/>Read the rest of <a href="http://helllabs.org/blog/20071231/asus-eeepc-fastinit-reimplementation/">Asus Eeepc fastinit reimplementation</a> (267 words)</p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20071231/asus-eeepc-fastinit-reimplementation/#comments">6 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20071231/asus-eeepc-fastinit-reimplementation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>UVC quirk for Syntek webcam</title>
		<link>http://helllabs.org/blog/20071227/uvc-quirk-for-syntek-webcam/</link>
		<comments>http://helllabs.org/blog/20071227/uvc-quirk-for-syntek-webcam/#comments</comments>
		<pubDate>Thu, 27 Dec 2007 16:19:09 +0000</pubDate>
		<dc:creator>claudio</dc:creator>
		
		<category><![CDATA[en]]></category>

		<category><![CDATA[linux]]></category>

		<category><![CDATA[patch]]></category>

		<category><![CDATA[webcam]]></category>

		<guid isPermaLink="false">http://helllabs.org/blog/20071227/uvc-quirk-for-syntek-webcam/</guid>
		<description><![CDATA[The following patch allows the Syntek 174f:5212 camera found in some HP laptops (including the Compaq Presario C700 series) to be used in Linux with the linux-uvc driver. The image quality is fairly good, with decent colors, white balance and frame rate in luvcview. The patch is a bit intrusive since it requires quirk testing [...]]]></description>
			<content:encoded><![CDATA[<p>The following patch allows the Syntek 174f:5212 camera found in some HP laptops (including the Compaq Presario C700 series) to be used in Linux with the <a href="http://linux-uvc.berlios.de/">linux-uvc</a> driver. The image quality is fairly good, with decent colors, white balance and frame rate in luvcview. The patch is a bit intrusive since it requires quirk testing at the start of the isochronous payload frame decoding to completely bypass synchronization, but it seems to work very well. This patch is against revision 158 of the linux-uvc subversion repository.</p>
<ul>
<li><strike><a href="/patch/20071227_uvc/0001-Add-quirk-for-Syntek-174f-5212-camera.patch">Add quirk for Syntek 174f:5212 UVC camera</a></strike> Wrong! Use <strike>Herton&#8217;s</strike> Laurent&#8217;s patch below.
<li><strike><a href="/patch/20071227_uvc/0002-Add-quirk-for-Syntek-174f-5212-camera.patch">Add quirk for Syntek 174f:5212 UVC camera</a> (fixed version)</strike>
<li><a href="/patch/20071227_uvc/stream-no-fid.patch">Laurent Pinchart&#8217;s final patch</a>
</ul>
<p>Syntek camera framegrabs: <a href="/patch/20071227_uvc/P-12:26:2007-19:14:14.png">1</a>, <a href="/patch/20071227_uvc/P-12:27:2007-15:31:15.png">2</a>.</p>
<p><strong>Update:</strong> <strike>Posted Herton Krzesinski&#8217;s fixed version.</strike> Posted Laurent Pinchart&#8217;s final version.</p>
	<p></p>
	<hr noshade style="margin:0;height:1px" />
	<small>
	<a href="http://helllabs.org/blog/20071227/uvc-quirk-for-syntek-webcam/#comments">2 comments</a>
	</small></p>]]></content:encoded>
			<wfw:commentRss>http://helllabs.org/blog/20071227/uvc-quirk-for-syntek-webcam/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
