<?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 on: &#8220;Unsupported machine ID&#8221; after upgrading Linux kernel or U-boot</title>
	<atom:link href="http://billauer.se/blog/2014/02/uboot-linux-dtb-fdt-device-tree/feed/" rel="self" type="application/rss+xml" />
	<link>https://billauer.se/blog/2014/02/uboot-linux-dtb-fdt-device-tree/</link>
	<description>Anything I found worthy to write down.</description>
	<lastBuildDate>Thu, 26 Mar 2026 13:15:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Andras Gal</title>
		<link>https://billauer.se/blog/2014/02/uboot-linux-dtb-fdt-device-tree/comment-page-1/#comment-1089</link>
		<dc:creator>Andras Gal</dc:creator>
		<pubDate>Tue, 19 May 2015 08:44:01 +0000</pubDate>
		<guid isPermaLink="false">https://billauer.se/blog/?p=4146#comment-1089</guid>
		<description>Look at this:
http://www.wiki.xilinx.com/Zynq+Linux

&quot;Device Tree In Memory
The kernel has 2 ways it can find a device tree in memory. The 1st and industry standard method is that it expects the address of the device tree to be in register R2 when the boots. Starting in 14.3 this is the default kernel configuration, but it was not previously.

The 2nd method, and the default in the Xilinx kernel configuration, is hard coded such that it expects the device tree at address 0x1000000 (16 MB). This is referred to as Device Tree At Fixed Address in the kernel configuration. The purpose of the fixed address for a device tree is to allow the go command in u-boot (which does not set up R2 to point to the device tree) to continue to be used.

This method can be enabled in the kernel configuration and must be disabled if a device tree is to loaded at other addresses while using the bootm command in u-boot.
Note that the Device Tree At Fixed Address kernel configuration option is only available in the menu when device tree has been enabled in the kernel configuration.&quot;</description>
		<content:encoded><![CDATA[<p>Look at this:<br />
<a href="http://www.wiki.xilinx.com/Zynq+Linux" rel="nofollow">http://www.wiki.xilinx.com/Zynq+Linux</a></p>
<p>&#8220;Device Tree In Memory<br />
The kernel has 2 ways it can find a device tree in memory. The 1st and industry standard method is that it expects the address of the device tree to be in register R2 when the boots. Starting in 14.3 this is the default kernel configuration, but it was not previously.</p>
<p>The 2nd method, and the default in the Xilinx kernel configuration, is hard coded such that it expects the device tree at address 0x1000000 (16 MB). This is referred to as Device Tree At Fixed Address in the kernel configuration. The purpose of the fixed address for a device tree is to allow the go command in u-boot (which does not set up R2 to point to the device tree) to continue to be used.</p>
<p>This method can be enabled in the kernel configuration and must be disabled if a device tree is to loaded at other addresses while using the bootm command in u-boot.<br />
Note that the Device Tree At Fixed Address kernel configuration option is only available in the menu when device tree has been enabled in the kernel configuration.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
