<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Power-Consumption on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/power-consumption/</link><description>Recent content in Power-Consumption on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Sat, 16 Jun 2012 18:49:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/power-consumption/index.xml" rel="self" type="application/rss+xml"/><item><title>Code vs. power consumption</title><link>http://karpoke.ignaciocano.com/2012/06/16/code-vs-power-consumption/</link><pubDate>Sat, 16 Jun 2012 18:49:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/06/16/code-vs-power-consumption/</guid><description>&lt;blockquote&gt;
&lt;p&gt;I’ve been wondering for some time whether the power consumption of an
ATmega varies depending on the code it is running. Obviously, sleep
modes and clock rate changes have a major impact – but how about plain
loops?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» &lt;a href="http://jeelabs.org/2012/06/13/code-vs-power-consumption/"&gt;jeelabs.org&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>