<?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 Embedded Bits</title>
	<atom:link href="http://www.embedded-bits.co.uk/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.embedded-bits.co.uk</link>
	<description>Understanding the embedded world bit by bit</description>
	<lastBuildDate>Wed, 28 Mar 2012 18:19:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Turning on an ARM MMU and Living to tell the tale: The code by Andrew Murray</title>
		<link>http://www.embedded-bits.co.uk/2011/mmucode/#comment-32037</link>
		<dc:creator>Andrew Murray</dc:creator>
		<pubDate>Wed, 28 Mar 2012 18:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=827#comment-32037</guid>
		<description>Hi Igor,

The start of the page table is 0x40200000, each entry is 4 bytes long and each entry corresponds to a 1MB section of memory. The first entry in the page table (0x40200000) represents what happens when you try to access memory between the range of 0x00000000 to 0x00100000, the second entry (4 bytes into the table at 0x40200004) represents the memory range 0x00100000 to 0x00200000, etc. 

Therefore to find the page table associated with area of memory 0x40200000 to 0x40200000+1MB (which is the 402nd MB of memory) - you need to traverse the page table list by 402 entries - but each entry is 4 bytes long therefore you need to time this number by 4.

Does that make sense?

Andy</description>
		<content:encoded><![CDATA[<p>Hi Igor,</p>
<p>The start of the page table is 0&#215;40200000, each entry is 4 bytes long and each entry corresponds to a 1MB section of memory. The first entry in the page table (0&#215;40200000) represents what happens when you try to access memory between the range of 0&#215;00000000 to 0&#215;00100000, the second entry (4 bytes into the table at 0&#215;40200004) represents the memory range 0&#215;00100000 to 0&#215;00200000, etc. </p>
<p>Therefore to find the page table associated with area of memory 0&#215;40200000 to 0&#215;40200000+1MB (which is the 402nd MB of memory) &#8211; you need to traverse the page table list by 402 entries &#8211; but each entry is 4 bytes long therefore you need to time this number by 4.</p>
<p>Does that make sense?</p>
<p>Andy</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Turning on an ARM MMU and Living to tell the tale: The code by Igor</title>
		<link>http://www.embedded-bits.co.uk/2011/mmucode/#comment-31062</link>
		<dc:creator>Igor</dc:creator>
		<pubDate>Sun, 18 Mar 2012 12:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=827#comment-31062</guid>
		<description>Hi... thx for ur work.. I m a noob (and maybe a bit stupid too...) but really I don&#039;t understand the:
&quot;the destination address is the offset in the page table which corresponds to the 1MB of memory which includes the SRAM (table base + 0×402 * 4).&quot;

I thought the first entry should be on the :
&quot;tlb_l1_base: .word 0x40200000&quot;

And so, where that 0x402*4 comes from??

Did I miss something? Thank u very much..</description>
		<content:encoded><![CDATA[<p>Hi&#8230; thx for ur work.. I m a noob (and maybe a bit stupid too&#8230;) but really I don&#8217;t understand the:<br />
&#8220;the destination address is the offset in the page table which corresponds to the 1MB of memory which includes the SRAM (table base + 0×402 * 4).&#8221;</p>
<p>I thought the first entry should be on the :<br />
&#8220;tlb_l1_base: .word 0&#215;40200000&#8243;</p>
<p>And so, where that 0&#215;402*4 comes from??</p>
<p>Did I miss something? Thank u very much..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Writing an MLO for a BeagleBoard XM by johnson</title>
		<link>http://www.embedded-bits.co.uk/2011/writeanmlo/#comment-29017</link>
		<dc:creator>johnson</dc:creator>
		<pubDate>Thu, 23 Feb 2012 06:37:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=636#comment-29017</guid>
		<description>I like details,It really shot me!</description>
		<content:encoded><![CDATA[<p>I like details,It really shot me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on cat /proc/meminfo : MemTotal by Linux系统内存相关信息获取 &#124; Erlang非业余研究</title>
		<link>http://www.embedded-bits.co.uk/2011/cat-procmeminfo-memtotal/#comment-28643</link>
		<dc:creator>Linux系统内存相关信息获取 &#124; Erlang非业余研究</dc:creator>
		<pubDate>Sun, 19 Feb 2012 06:09:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=369#comment-28643</guid>
		<description>[...] 详细描述可参考这里 比如： NUMA: Using 30 for the hash shift. Bootmem setup node 0 0000000000000000-0000000340000000 [...]</description>
		<content:encoded><![CDATA[<p>[...] 详细描述可参考这里 比如： NUMA: Using 30 for the hash shift. Bootmem setup node 0 0000000000000000-0000000340000000 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hardware Environment for a BeagleBoard XM with JTAG by Suresh Acharya</title>
		<link>http://www.embedded-bits.co.uk/2011/beagleboardxmjtaghardwar/#comment-28370</link>
		<dc:creator>Suresh Acharya</dc:creator>
		<pubDate>Thu, 16 Feb 2012 07:44:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=538#comment-28370</guid>
		<description>For the beagleboard Xm – do we have any startup initialization code to flash using xds100, if we are not using any bootloader or linux image and want to perform some board diagnostics?</description>
		<content:encoded><![CDATA[<p>For the beagleboard Xm – do we have any startup initialization code to flash using xds100, if we are not using any bootloader or linux image and want to perform some board diagnostics?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I2C in the 2.6.32 Linux Kernel by kakaburra</title>
		<link>http://www.embedded-bits.co.uk/2009/i2c-in-the-2632-linux-kernel/#comment-28330</link>
		<dc:creator>kakaburra</dc:creator>
		<pubDate>Wed, 15 Feb 2012 16:51:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=174#comment-28330</guid>
		<description>thanks a lot .. it cleared up a lot of doubts</description>
		<content:encoded><![CDATA[<p>thanks a lot .. it cleared up a lot of doubts</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I2C in the 2.6.32 Linux Kernel by Vinesh Balan</title>
		<link>http://www.embedded-bits.co.uk/2009/i2c-in-the-2632-linux-kernel/#comment-26611</link>
		<dc:creator>Vinesh Balan</dc:creator>
		<pubDate>Fri, 27 Jan 2012 11:31:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=174#comment-26611</guid>
		<description>Nice one, I&#039;ve been pondering for the basics of I2C for a while, got it finally. Thanks a ton!</description>
		<content:encoded><![CDATA[<p>Nice one, I&#8217;ve been pondering for the basics of I2C for a while, got it finally. Thanks a ton!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Init Call Mechanism in the Linux Kernel by Nobel</title>
		<link>http://www.embedded-bits.co.uk/2008/init-call-mechanism/#comment-25433</link>
		<dc:creator>Nobel</dc:creator>
		<pubDate>Sat, 14 Jan 2012 12:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=72#comment-25433</guid>
		<description>Nice Blog for Linus&#039;s beginners</description>
		<content:encoded><![CDATA[<p>Nice Blog for Linus&#8217;s beginners</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I2C in the 2.6.32 Linux Kernel by Michel Benoit</title>
		<link>http://www.embedded-bits.co.uk/2009/i2c-in-the-2632-linux-kernel/#comment-22288</link>
		<dc:creator>Michel Benoit</dc:creator>
		<pubDate>Fri, 09 Dec 2011 12:00:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=174#comment-22288</guid>
		<description>Thanks for the article.  It saved me a lot of time ...</description>
		<content:encoded><![CDATA[<p>Thanks for the article.  It saved me a lot of time &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I2C in the 2.6.32 Linux Kernel by ebanezar</title>
		<link>http://www.embedded-bits.co.uk/2009/i2c-in-the-2632-linux-kernel/#comment-21989</link>
		<dc:creator>ebanezar</dc:creator>
		<pubDate>Tue, 06 Dec 2011 13:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.embedded-bits.co.uk/?p=174#comment-21989</guid>
		<description>nice article........Thanks for it....</description>
		<content:encoded><![CDATA[<p>nice article&#8230;&#8230;..Thanks for it&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

