Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=1.4_M3.rc2 2013-01-20T13:05:39+00:00 2013-01-20T13:05:39+00:00 Tom Zanussi tom.zanussi@intel.com 2013-01-18T18:27:13+00:00 urn:sha1:37d295c81692a8145cb7a235ebf9556e9b902df5 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 <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2013-01-20T13:05:39+00:00 Tom Zanussi tom.zanussi@intel.com 2013-01-18T18:27:12+00:00 urn:sha1:1ca4b36445a5471e9d12ee50708946df9f6baf52 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 <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2013-01-20T13:05:39+00:00 Tom Zanussi tom.zanussi@intel.com 2013-01-18T18:27:11+00:00 urn:sha1:7b0026ea1250b170ac70e1212d12bb86698e79e9 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 <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2013-01-20T13:05:39+00:00 Tom Zanussi tom.zanussi@intel.com 2013-01-18T18:27:10+00:00 urn:sha1:93d37a261b1c6cc91451b3d197c7f28a3f6123b1 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 <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2013-01-20T13:05:39+00:00 Tom Zanussi tom.zanussi@intel.com 2013-01-18T18:27:09+00:00 urn:sha1:bd1cb7b36dd1ba61a7d18520d85d09b215d6dfba This is essentially 'the documentation' for the yocto-layer tool. (From meta-yocto rev: 34229b931bad8fc0e4d4431bb5cb46fccbea03bf) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2013-01-20T13:05:38+00:00 Tom Zanussi tom.zanussi@intel.com 2013-01-18T18:27:07+00:00 urn:sha1:792b1bf0147a72613e76ce8f88764e99c51b80eb 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 <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2013-01-16T12:08:01+00:00 Tom Zanussi tom.zanussi@intel.com 2013-01-15T22:59:57+00:00 urn:sha1:a746719a46e9277a118fd7d4a6342bb667034132 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 <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-12-13T16:54:35+00:00 Tom Zanussi tom.zanussi@intel.com 2012-12-13T04:56:41+00:00 urn:sha1:0be41d6e30e6dfd9d77e7b8b7ca11ab0b8474cbb With the addition of custom kernel support, we also need to handle the normal PR format found in .bb files. (From meta-yocto rev: e17570b6bbd36a731f546f800ef5f271ed5c3697) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-12-13T16:54:34+00:00 Tom Zanussi tom.zanussi@intel.com 2012-12-13T04:56:40+00:00 urn:sha1:76b2ef26e7ee23cbf05051c3978a37f0ee4062b9 We no longer have to include patches in the SRC_URI, since things now work using only patch in the .scc file, so remove anything to do with maintaining patches in the SRC_URI and fix up all previous users of that code. (From meta-yocto rev: 8f3cd1f80f898d963797bc96b3fe599f7f8ea343) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-12-13T16:54:34+00:00 Tom Zanussi tom.zanussi@intel.com 2012-12-13T04:56:39+00:00 urn:sha1:8a1d25cdce6dd7e3f03587382127676f95dadf30 Previously we assumed we were always dealing with .bbappends. With custom kernels, we now have SRC_URIs in .bb files, so add .bb files to the list of file types we examine and modify. (From meta-yocto rev: 4200c5c99b7d61e05b0d9d1580e267e7d6d49760) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>