<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Hardwarebug</title>
	<atom:link href="http://hardwarebug.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://hardwarebug.org</link>
	<description>Everything is broken</description>
	<lastBuildDate>Mon, 30 Aug 2010 09:33:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Countryside by lu_zero</title>
		<link>http://hardwarebug.org/2010/08/17/countryside/comment-page-1/#comment-1230</link>
		<dc:creator>lu_zero</dc:creator>
		<pubDate>Mon, 30 Aug 2010 09:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=541#comment-1230</guid>
		<description>Wonderful pictures and places. Where are them?</description>
		<content:encoded><![CDATA[<p>Wonderful pictures and places. Where are them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IJG swings again, and misses by Mans</title>
		<link>http://hardwarebug.org/2010/02/01/ijg-swings-again-and-misses/comment-page-1/#comment-1229</link>
		<dc:creator>Mans</dc:creator>
		<pubDate>Thu, 26 Aug 2010 12:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=234#comment-1229</guid>
		<description>The tests I performed used the settings suggested in the manual, downscaling on encode and upscaling on decode.</description>
		<content:encoded><![CDATA[<p>The tests I performed used the settings suggested in the manual, downscaling on encode and upscaling on decode.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IJG swings again, and misses by Ben R-G</title>
		<link>http://hardwarebug.org/2010/02/01/ijg-swings-again-and-misses/comment-page-1/#comment-1227</link>
		<dc:creator>Ben R-G</dc:creator>
		<pubDate>Wed, 25 Aug 2010 20:36:48 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=234#comment-1227</guid>
		<description>I don&#039;t think this IJG has much to do with the IJG of the 1990s. Tom Lane (the former organizer of the IJG) was not involved in v7 and later releases as far as I know. I think they&#039;re almost solely the work of Guido Vollbeding, who does seem to be a bit kooky.

I think you&#039;ve missed the point of &quot;SmartScale&quot;. As far as I can tell, the idea is to use smaller block sizes than 8x8. You can simulate this in the v7 library by scaling by 8/n on encode, with n less than 8, then scaling by n/8 on decode (you can even simulate it in version 6b with n=1,2,4). &quot;SmartScale&quot; stores the n/8 factor in the file so it can be automatically applied when decoding, kind of like EXIF rotation, and also suppresses the AC coefficients that are always zero. It doesn&#039;t add support for larger DCTs with more than 64 outputs; when you scaled by 8/n with n greater than 8 you simply lost the high-frequency components with predictable results.

There is an ITU-T recommendation, T.851, which adds 16-bit samples and a new arithmetic coding mode to T.81. I had assumed that the promised improvements in v8 would be an implementation of that standard, but apparently not.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think this IJG has much to do with the IJG of the 1990s. Tom Lane (the former organizer of the IJG) was not involved in v7 and later releases as far as I know. I think they&#8217;re almost solely the work of Guido Vollbeding, who does seem to be a bit kooky.</p>
<p>I think you&#8217;ve missed the point of &#8220;SmartScale&#8221;. As far as I can tell, the idea is to use smaller block sizes than 8&#215;8. You can simulate this in the v7 library by scaling by 8/n on encode, with n less than 8, then scaling by n/8 on decode (you can even simulate it in version 6b with n=1,2,4). &#8220;SmartScale&#8221; stores the n/8 factor in the file so it can be automatically applied when decoding, kind of like EXIF rotation, and also suppresses the AC coefficients that are always zero. It doesn&#8217;t add support for larger DCTs with more than 64 outputs; when you scaled by 8/n with n greater than 8 you simply lost the high-frequency components with predictable results.</p>
<p>There is an ITU-T recommendation, T.851, which adds 16-bit samples and a new arithmetic coding mode to T.81. I had assumed that the promised improvements in v8 would be an implementation of that standard, but apparently not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking the Popcorn Hour C-200 by ANSI FATE &#124; Breaking Eggs And Making Omelettes</title>
		<link>http://hardwarebug.org/2010/05/03/hacking-the-popcorn-hour-c-200/comment-page-1/#comment-1225</link>
		<dc:creator>ANSI FATE &#124; Breaking Eggs And Making Omelettes</dc:creator>
		<pubDate>Tue, 24 Aug 2010 05:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=479#comment-1225</guid>
		<description>[...] list. This one reports itself as running on 74kf CPU. Googling for this processor quickly brings up Mans&#8217; post about the Popcorn Hour device. So, congratulations to him for getting the mundane box to serve a higher purpose. Perhaps one day, [...]</description>
		<content:encoded><![CDATA[<p>[...] list. This one reports itself as running on 74kf CPU. Googling for this processor quickly brings up Mans&#8217; post about the Popcorn Hour device. So, congratulations to him for getting the mundane box to serve a higher purpose. Perhaps one day, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ARM inline asm secrets by Stian Skjelstad</title>
		<link>http://hardwarebug.org/2010/07/06/arm-inline-asm-secrets/comment-page-1/#comment-1193</link>
		<dc:creator>Stian Skjelstad</dc:creator>
		<pubDate>Sat, 31 Jul 2010 19:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=493#comment-1193</guid>
		<description>Using undocumented features that might change in future gcc versions isn&#039;t pure evil as some people claim.

If you need some fancy features in an project you are working on, you probably lock down which versions of libraries and tools-chains that you work on. Jumping for gcc3.x to gcc4.x for instance is normally not recommended in a live project, especially in the embedded world</description>
		<content:encoded><![CDATA[<p>Using undocumented features that might change in future gcc versions isn&#8217;t pure evil as some people claim.</p>
<p>If you need some fancy features in an project you are working on, you probably lock down which versions of libraries and tools-chains that you work on. Jumping for gcc3.x to gcc4.x for instance is normally not recommended in a live project, especially in the embedded world</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking the Popcorn Hour C-200 by Mans</title>
		<link>http://hardwarebug.org/2010/05/03/hacking-the-popcorn-hour-c-200/comment-page-1/#comment-1179</link>
		<dc:creator>Mans</dc:creator>
		<pubDate>Fri, 23 Jul 2010 23:01:31 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=479#comment-1179</guid>
		<description>I used latest from git.  There are some MIPS fixes there which I don&#039;t think have made it into a release yet.</description>
		<content:encoded><![CDATA[<p>I used latest from git.  There are some MIPS fixes there which I don&#8217;t think have made it into a release yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking the Popcorn Hour C-200 by Andy</title>
		<link>http://hardwarebug.org/2010/05/03/hacking-the-popcorn-hour-c-200/comment-page-1/#comment-1178</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 23 Jul 2010 13:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=479#comment-1178</guid>
		<description>Thanks, a lot, I&#039;ve successfully built the kernel. But loading it with kexec userspace tool (latest version from kernel.org, 2.0.1) fails with 

Invalid memory segment 0x4000000 - 0x42d3fff

What kexec binary did you use?</description>
		<content:encoded><![CDATA[<p>Thanks, a lot, I&#8217;ve successfully built the kernel. But loading it with kexec userspace tool (latest version from kernel.org, 2.0.1) fails with </p>
<p>Invalid memory segment 0&#215;4000000 &#8211; 0x42d3fff</p>
<p>What kexec binary did you use?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking the Popcorn Hour C-200 by Mans</title>
		<link>http://hardwarebug.org/2010/05/03/hacking-the-popcorn-hour-c-200/comment-page-1/#comment-1177</link>
		<dc:creator>Mans</dc:creator>
		<pubDate>Thu, 22 Jul 2010 20:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=479#comment-1177</guid>
		<description>http://www.networkedmediatank.com/download/firmware/nmt/gpl/linux-2.6.22.19.tar.bz2</description>
		<content:encoded><![CDATA[<p><a href="http://www.networkedmediatank.com/download/firmware/nmt/gpl/linux-2.6.22.19.tar.bz2" rel="nofollow">http://www.networkedmediatank.com/download/firmware/nmt/gpl/linux-2.6.22.19.tar.bz2</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking the Popcorn Hour C-200 by Andy</title>
		<link>http://hardwarebug.org/2010/05/03/hacking-the-popcorn-hour-c-200/comment-page-1/#comment-1174</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 22 Jul 2010 11:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=479#comment-1174</guid>
		<description>The problem is that Sigma patches are not applicable to 2.6.22.19 kernel sources from linux-mips.org. Patches can be applied to vanilla sources from kernel.org, but kernel config is not suitable there. 
Also, I&#039;m not sure that mips kernel can possibly be built from sources at kernel.org.

Rebuilding firmware kernel is much less preferrable for me.

So, what exact sources did you use?</description>
		<content:encoded><![CDATA[<p>The problem is that Sigma patches are not applicable to 2.6.22.19 kernel sources from linux-mips.org. Patches can be applied to vanilla sources from kernel.org, but kernel config is not suitable there.<br />
Also, I&#8217;m not sure that mips kernel can possibly be built from sources at kernel.org.</p>
<p>Rebuilding firmware kernel is much less preferrable for me.</p>
<p>So, what exact sources did you use?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking the Popcorn Hour C-200 by Mans</title>
		<link>http://hardwarebug.org/2010/05/03/hacking-the-popcorn-hour-c-200/comment-page-1/#comment-1173</link>
		<dc:creator>Mans</dc:creator>
		<pubDate>Wed, 21 Jul 2010 17:02:10 +0000</pubDate>
		<guid isPermaLink="false">http://hardwarebug.org/?p=479#comment-1173</guid>
		<description>You need the Sigma patches.</description>
		<content:encoded><![CDATA[<p>You need the Sigma patches.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
