<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/Documentation/devicetree/bindings/arm/xilinx.txt, branch linux-4.3.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.3.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-4.3.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2014-07-30T11:26:54Z</updated>
<entry>
<title>ARM: zynq: DT: Clarify Xilinx Zynq platform</title>
<updated>2014-07-30T11:26:54Z</updated>
<author>
<name>Michal Simek</name>
<email>michal.simek@xilinx.com</email>
</author>
<published>2014-07-25T07:01:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=6a3246c02e7bcb16a58f3fcee4662a9b36ea80e9'/>
<id>urn:sha1:6a3246c02e7bcb16a58f3fcee4662a9b36ea80e9</id>
<content type='text'>
ep107 was emulation platform and compatible string
have been changed long time ago.

"ARM: zynq: dts: split up device tree"
(sha1: e06f1a9ed7ebff170ba05d2606d079fb36c6a52d)

Signed-off-by: Michal Simek &lt;michal.simek@xilinx.com&gt;
</content>
</entry>
<entry>
<title>ARM: Xilinx: Adding Xilinx board support</title>
<updated>2011-06-20T17:52:30Z</updated>
<author>
<name>John Linn</name>
<email>john.linn@xilinx.com</email>
</author>
<published>2011-06-20T17:47:27Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=b85a3ef4ac65169b65fd2fe9bec7912bbf475ba4'/>
<id>urn:sha1:b85a3ef4ac65169b65fd2fe9bec7912bbf475ba4</id>
<content type='text'>
The 1st board support is minimal to get a system up and running
on the Xilinx platform.

This platform reuses the clock implementation from plat-versatile, and
it depends entirely on CONFIG_OF support.  There is only one board
support file which obtains all device information from a device tree
dtb file which is passed to the kernel at boot time.

Signed-off-by: John Linn &lt;john.linn@xilinx.com&gt;
</content>
</entry>
</feed>
