<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/scripts, branch 1.4_M3.rc2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=1.4_M3.rc2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=1.4_M3.rc2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2013-01-22T16:01:32+00:00</updated>
<entry>
<title>prserv: add LOCALCOUNT to AUTOINCs migration feature</title>
<updated>2013-01-22T16:01:32+00:00</updated>
<author>
<name>Constantin Musca</name>
<email>constantinx.musca@intel.com</email>
</author>
<published>2013-01-22T09:39:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8d6e55bf2192524bda84138b5356a2791adbbe61'/>
<id>urn:sha1:8d6e55bf2192524bda84138b5356a2791adbbe61</id>
<content type='text'>
- use migrate_localcount.bbclass to generate AUTOINC entries
which are exported to LOCALCOUNT_DUMPFILE
- import the generated AUTOINC entries
- one can migrate LOCALCOUNT to AUTOINC by executing:
    bitbake-prserv-tool migrate_localcount

[YOCTO #3071]

(From OE-Core rev: ffab86f13cafb10d8d6273b6af8cd9a3c84eae20)

Signed-off-by: Constantin Musca &lt;constantinx.musca@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bb-matrix: Fix min and max calculations</title>
<updated>2013-01-21T10:22:08+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2013-01-18T23:13:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4287f703413a14d190152e46593bb69b141e80b4'/>
<id>urn:sha1:4287f703413a14d190152e46593bb69b141e80b4</id>
<content type='text'>
The BB and PM ranges were originally intended to use leading 0s to
ensure all the values were the same string length, making for nice log
filenames and columnar dat files. However, not everyone will do this -
especially if it isn't documented.

Document the intent. Make the generation and parsing of dat files robust
to either method.

(From OE-Core rev: 90dc44c8246f2a580fe4a41ce28c201e52307500)

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
Signed-off-by: Saul Wold &lt;sgw@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/lib/bsp/engine.py: add handling for JSON strings</title>
<updated>2013-01-20T13:05:39+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-18T18:27:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=37d295c81692a8145cb7a235ebf9556e9b902df5'/>
<id>urn:sha1:37d295c81692a8145cb7a235ebf9556e9b902df5</id>
<content type='text'>
Normally pre-canned properties are supplied as JSON from a file, which
the user can specify using e.g. the -i option.

We can reuse that basic functionality for dedicated command-line
parameters by sythesizing a JSON string containing those param values
on the fly and passing that in instead.

This adds the ability for the common creation code to accept JSON
strings as well as JSON files.

(From meta-yocto rev: 5a2e840b24822e018de94ec4f554363b59c4e8bd)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-layer: add optional layer priority param</title>
<updated>2013-01-20T13:05:39+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-18T18:27:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1ca4b36445a5471e9d12ee50708946df9f6baf52'/>
<id>urn:sha1:1ca4b36445a5471e9d12ee50708946df9f6baf52</id>
<content type='text'>
If the user specifies a layer priority following the layer name, layer
creation will proceed without further queries using the specified
layer priority and the remaining values defaulted.

(From meta-yocto rev: 84a0bd8940f82fb938972d7b026367d40c9472e7)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/lib/bsp/engine.py: refactor bsp-creation code</title>
<updated>2013-01-20T13:05:39+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-18T18:27:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7b0026ea1250b170ac70e1212d12bb86698e79e9'/>
<id>urn:sha1:7b0026ea1250b170ac70e1212d12bb86698e79e9</id>
<content type='text'>
This does a bit of refactoring of the bsp-generation code to make it
generically reusable for generating non-bsp layers.

The first user remains the existing yocto-bsp tool; these changes
allow a second user, the new yocto-layer tool, to use the same code.

(From meta-yocto rev: 1527a0ee7bce08a527c9d80516531b17816dff17)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-layer: add 'layer' template data</title>
<updated>2013-01-20T13:05:39+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-18T18:27:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=93d37a261b1c6cc91451b3d197c7f28a3f6123b1'/>
<id>urn:sha1:93d37a261b1c6cc91451b3d197c7f28a3f6123b1</id>
<content type='text'>
Add a 'layer' target containing all the data that will be used to
generate a generic yocto layer.

(From meta-yocto rev: 198a85f61ebd6435830285b2a9b1b925aea6779e)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-layer: add help/usage</title>
<updated>2013-01-20T13:05:39+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-18T18:27:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bd1cb7b36dd1ba61a7d18520d85d09b215d6dfba'/>
<id>urn:sha1:bd1cb7b36dd1ba61a7d18520d85d09b215d6dfba</id>
<content type='text'>
This is essentially 'the documentation' for the yocto-layer tool.

(From meta-yocto rev: 34229b931bad8fc0e4d4431bb5cb46fccbea03bf)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-layer: new script</title>
<updated>2013-01-20T13:05:39+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-18T18:27:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=be425050b19bc9f257b31738be3c77d182efdf2e'/>
<id>urn:sha1:be425050b19bc9f257b31738be3c77d182efdf2e</id>
<content type='text'>
Implementation of the 'yocto-layer' command-line tool, for creating
generic layers and listing their input properties.

(From meta-yocto rev: 8170bea55379d1a25acc0fea108675526eeab6f6)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>scripts/lib/bsp/engine.py: add yocto_layer_create()</title>
<updated>2013-01-20T13:05:38+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-18T18:27:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=792b1bf0147a72613e76ce8f88764e99c51b80eb'/>
<id>urn:sha1:792b1bf0147a72613e76ce8f88764e99c51b80eb</id>
<content type='text'>
Add a new yocto_layer_create() function that will be used to generate
a generic yocto layer (for the new 'yocto-layer' command).

(From meta-yocto rev: 44acd01bf47c2e0a777e686c9339a6ff951fc972)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>yocto-bsp: add basic git connectivity check</title>
<updated>2013-01-16T12:08:01+00:00</updated>
<author>
<name>Tom Zanussi</name>
<email>tom.zanussi@intel.com</email>
</author>
<published>2013-01-15T22:59:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a746719a46e9277a118fd7d4a6342bb667034132'/>
<id>urn:sha1:a746719a46e9277a118fd7d4a6342bb667034132</id>
<content type='text'>
yocto-bsp create does a 'git ls-remote
git://git.yoctoproject.org/linux-yocto-3.4.git *heads*' to get the set
of existing branches from the kernel repo.

If the user isn't connected to the network, or if git isn't configured
sanely, yocto-bsp fails with an ugly Python backtrace.

We should try to avoid this by doing a basic sanity check for those
things before actually running the command.

The sanity check can be avoided by specifying -s on the yocto-bsp
command-line:

 $ yocto-bsp create -s test qemu

Fixes [YOCTO #3279]

(From meta-yocto rev: 496e76f9bed2ed5a04ef757724d2e63d05c7a601)

Signed-off-by: Tom Zanussi &lt;tom.zanussi@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
