<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/dtoc/fdt_select.py, branch v2017.03</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/dtoc/fdt_select.py?h=v2017.03</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/dtoc/fdt_select.py?h=v2017.03'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2016-10-09T15:30:32Z</updated>
<entry>
<title>dtoc: Add a way for tests to request the fallback library</title>
<updated>2016-10-09T15:30:32Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-09-25T21:52:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3cb44ba80c0379eb7d0eadd1b9b58e66fe2da03e'/>
<id>urn:sha1:3cb44ba80c0379eb7d0eadd1b9b58e66fe2da03e</id>
<content type='text'>
We need to test both the normal (Python libfdt module) and fallback (fdtget)
implementations of the Fdt class. Add a way to select which implementation
to use.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Create a base class for Fdt</title>
<updated>2016-09-19T03:04:38Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-07-26T00:59:04Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a06a34b2031e0797892e188595bfb305cd9719ab'/>
<id>urn:sha1:a06a34b2031e0797892e188595bfb305cd9719ab</id>
<content type='text'>
At present we have two separate implementations of the Fdt library, one which
uses fdtget/fdtput and one which uses libfdt (via swig).

Before adding more functionality it makes sense to create a base class for
these. This will allow common functions to be shared, and make the Fdt API
a little clearer.

Create a new fdt.py file with the base class, and adjust fdt_normal.py and
fdt_fallback.py to use it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Rename fdt.py to fdt_normal.py</title>
<updated>2016-09-19T03:04:38Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-07-26T00:59:03Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=66051b1f59dfba48566dc3e0eee4c093e1104590'/>
<id>urn:sha1:66051b1f59dfba48566dc3e0eee4c093e1104590</id>
<content type='text'>
In preparation for creating an Fdt base class, rename this file to indicate
it is the normal Fdt implementation.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Move the fdt library selection into fdt_select</title>
<updated>2016-09-19T03:04:38Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2016-07-26T00:59:02Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ba482585661431dde74eb69c7a94ac2d5a772d9f'/>
<id>urn:sha1:ba482585661431dde74eb69c7a94ac2d5a772d9f</id>
<content type='text'>
Rather than have dtc worry about which fdt library to use, move this into
a helper file. Add a function which creates a new Fdt object and scans it,
regardless of the implementation.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
