<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ennonymous</title>
	<atom:link href="http://ennonymous.de/feed/" rel="self" type="application/rss+xml" />
	<link>http://ennonymous.de</link>
	<description></description>
	<lastBuildDate>Wed, 11 Aug 2010 09:14:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>&#8220;Inception&#8221; as self-modifying code</title>
		<link>http://ennonymous.de/2010/08/11/inception-as-self-modifying-code/</link>
		<comments>http://ennonymous.de/2010/08/11/inception-as-self-modifying-code/#comments</comments>
		<pubDate>Wed, 11 Aug 2010 08:54:42 +0000</pubDate>
		<dc:creator>ennonymous</dc:creator>
				<category><![CDATA[Hacking]]></category>
		<category><![CDATA[Movies]]></category>

		<guid isPermaLink="false">http://ennonymous.de/?p=67</guid>
		<description><![CDATA[  The movie &#8220;Inception&#8221; seems to have gathered quite a following among the technology-affine crowd, similar to what happened when Matrix came out &#8212; which is not all that surprising since both movies have quite a bit in common. Now, however, some very dedicated folks have implemented Inception&#8217;s plot as a multithreaded C application, where characters are represented [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"> <a href="http://ennonymous.de/wp-content/uploads/2010/08/screenshot.png"><img class="aligncenter size-full wp-image-74" title="screenshot" src="http://ennonymous.de/wp-content/uploads/2010/08/screenshot.png" alt="" width="528" height="375" /></a><a href="http://ennonymous.de/wp-content/uploads/2010/08/screenshot.png"></a></p>
<p>The movie &#8220;<a title="Inception at IMDB" href="http://www.imdb.com/title/tt1375666/" target="_blank">Inception</a>&#8221; seems to have gathered quite a following among the technology-affine crowd, similar to what happened when Matrix came out &#8212; which is not all that surprising since both movies have quite a bit in common.</p>
<p>Now, however, some very dedicated folks have implemented Inception&#8217;s plot as a <a title="Inception at GitHub" href="http://github.com/karthick18/inception" target="_blank">multithreaded C application</a>, where characters are represented by separate but interacting threads, sharing functions (the dream levels) but performing different actions within the dreams. Analogous to the movie, the code actually uses x86 code morphing techniques to &#8220;implant&#8221; modified instructions into the Fischer thread&#8217;s instruction stream.</p>
<p>This is crazy on so many levels. And to think that I already had trouble following the movie&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://ennonymous.de/2010/08/11/inception-as-self-modifying-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reducing rSoC synthesis turnaround times with xstcache</title>
		<link>http://ennonymous.de/2010/08/09/reducing-rsoc-synthesis-times-with-xstcache/</link>
		<comments>http://ennonymous.de/2010/08/09/reducing-rsoc-synthesis-times-with-xstcache/#comments</comments>
		<pubDate>Mon, 09 Aug 2010 14:06:05 +0000</pubDate>
		<dc:creator>ennonymous</dc:creator>
				<category><![CDATA[FPGA]]></category>

		<guid isPermaLink="false">http://ennonymous.de/?p=26</guid>
		<description><![CDATA[Working with complex reconfigurable SoC designs in Xilinx EDK can be a tedious process &#8212; especially, when you&#8217;re tweaking single VHDL source files of a single pcore, just to have all the pcores resynthesized by a twitchy makefile within the EDK build process. To cut down on design turnaround times, we&#8217;ve written a simple Python [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: center;"><a href="http://ennonymous.de/wp-content/uploads/2010/08/turnaround.jpg"><img class="aligncenter size-full wp-image-28" title="turnaround" src="http://ennonymous.de/wp-content/uploads/2010/08/turnaround.jpg" alt="" width="283" height="239" /></a></p>
<p>Working with complex reconfigurable SoC designs in Xilinx EDK can be a tedious process &#8212; especially, when you&#8217;re tweaking single VHDL source files of a single pcore, just to have all the pcores resynthesized by a twitchy makefile within the EDK build process.</p>
<p>To cut down on design turnaround times, we&#8217;ve written a simple Python script called <em>xstcache</em>, which does the same what <em>ccache</em> does for C sources. It looks at the input files, synthesis parameters and the environment, and, if the same combination has been used for a previous synthesis run, re-uses the result (the netlist) of that synthesis iteration without actually running XST.</p>
<p>For typical EDK projects, this reduces the time for the syntesis step considerably, as most pcore sources do not change between synthesis iterations.</p>
<p>You can find <em>xstcache</em> at <a href="http://github.com/luebbers/xstcache/" target="_blank">GitHub</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://ennonymous.de/2010/08/09/reducing-rsoc-synthesis-times-with-xstcache/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
