summaryrefslogtreecommitdiffstats
path: root/scripts
Commit message (Collapse)AuthorAgeFilesLines
* runqemu-internal: don't append an empty element to PATHScott Garman2012-09-281-1/+5
| | | | | | | | | | | | | Bitbake fails to run when an empty element exists in $PATH. Avoid creating this situation when $CROSSPATH is not set. This fixes bug [YOCTO #3101] (From OE-Core rev: 1f7f590369eaa76dc970c9cffd1f0db53ce08c00) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-find-native-sysroot: show bitbake errors to userScott Garman2012-09-281-10/+19
| | | | | | | | | | | | | Ran into another bug that was masked by hiding a bitbake error message. This catches this situation and displays the error to the user. Also includes whitespace fixes. (From OE-Core rev: 435ffeefe4a1df53335fd397ff404bed7deae2df) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management: hide error message when one of possible layer ↵Martin Jansa2012-09-271-1/+1
| | | | | | | | | | | location doesn't exist * fixes [YOCTO #3116] (From OE-Core rev: b02d334e0e6a19a1bf3550add68f5770a835c772) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* SDK: trap any IO errors in the relocate scriptLaurentiu Palcu2012-09-261-2/+12
| | | | | | | | | | | | | | | | If the files being relocated are already used by other processes the relocate script will fail with a traceback. This patch will trap any IO errors when opening such a file and gracefully report them to the user. Also change the exit code from 1 to -1 for a better adt-installer user experience (like pointing the user to the adt_installer.log). [YOCTO #3164] (From OE-Core rev: 26daec758b2eaeb208356d5aa8a9a191bd366751) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: work with tap device names that end with a colonScott Garman2012-09-242-2/+2
| | | | | | | | | | | | | On Fedora systems (and likely others), ifconfig returns interface names that end with a colon. Make sure we strip the colon off the tap device name before using it. This fixes [YOCTO #3028] (From OE-Core rev: 85ed217b603a86113dda11d952850e8ceed30795) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86-64: Support for KVM, paravirt and virtio addedCristian Iorga2012-09-211-2/+2
| | | | | | | | | | | | | | | KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86-64. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86-64 core-image-x11 kvm Implements [YOCTO #2550]. (From OE-Core rev: cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemux86: Support for KVM, paravirt and virtio addedCristian Iorga2012-09-212-4/+26
| | | | | | | | | | | | | | | KVM, paravirtualization and virtio drivers are now activated in runqemu using the kvm option flag for qemux86. Host CPU features are also exported to guest OS (Yocto Linux). Usage example: runqemu qemux86 core-image-x11 kvm Implements [YOCTO #2550]. (From OE-Core rev: a35d03e2eb905de4eadc9c7df5b50bff1fb7f897) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: show bitbake errors to userScott Garman2012-09-211-2/+10
| | | | | | | | | | | | | | In certain edge cases, bitbake may fail to run and cause setup_tmpdir() within runqemu to fail, and not give the user a helpful error message. Catch this case and show the user the output of bitbake -e. This fixes [YOCTO #3112] (From OE-Core rev: 465d7b6e66b5a55706535e194b3e44e11ee542c6) Signed-off-by: Scott Garman <scott.a.garman@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk.sh: Add script to do an EFI install on the hostDarren Hart2012-09-211-0/+255
| | | | | | | | | | | | | | | | Sometimes it is convenient to prepare a bootable image from the host rather than using a live-image to install to a disk on the target. This script takes a live image as input, partitions a device, and performs the installation just as the installer would if run on the target. (From OE-Core rev: 7225c6739f9f1e51741a42437692868165aa1dfe) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Replace "echo -e" with "printf" to have the same behavior in dash or bashAndrei Gherzan2012-09-201-1/+1
| | | | | | | | | | | | | | | | | | | | oe-core removed the prerequisite to have sh as bash. POSIX doesn't define any options and furthermore allows 'echo -e' to be the default behavior. This means that in dash 'echo -e' will actually print '-e' and interpret backslashes by default. We use instead 'printf' builtin command with or without '\n' to simulate 'echo -e' or 'echo -n'. 'printf' needs format while 'echo' can be used without any arguments. So 'echo >' was replaced by 'printf "" >'. 'echo' without '-n' flag adds a new line by default so to keep the same behavior of two new lines while using 'echo "\n"', 'printf "\n\n"' is used. [YOCTO #3138] (From OE-Core rev: a19880ad10ccb5d7d909dcf9de5c3dc58a0ebcd3) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/combo-layer: ensure we validate branch/revision on initPaul Eggleton2012-09-141-4/+7
| | | | | | | | | | | | | If both branch and last_revision are specified for a component when combo-layer init is run, ensure that the specified revision is actually on the specified branch and error out if not. Also ensure that the error message mentions the component. (From OE-Core rev: e498257ecbec94cec181d73bda57d44335b4dee0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/combo-layer: use last_revision if specified in initPaul Eggleton2012-09-141-7/+13
| | | | | | | | | | | | | | | | If last_revision is specified for a component when running combo-layer init, then use that revision instead of the latest revision on the branch. Also, remove unnecessary git checkout during init since we specify the revision to all calls to git when dealing with the component repositories. Fixes [YOCTO #3040]. (From OE-Core rev: ff8277cd133e9a02b131977078cff61fa587a1af) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: Explicitly specify MACHINE when calling bitbakeKhem Raj2012-09-141-1/+1
| | | | | | | | | | | | | When using runqemu with distros outside oe-core then MACHINE may not be there in local.conf so use the one thats available in environment of runqemu which is actually the correct one. (From OE-Core rev: 5c3fec058a2d370fbb625901ca1822ce04927ac2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts: change default ARM BSP to use xserver-xorg, not -liteRoss Burton2012-09-121-2/+2
| | | | | | | (From meta-yocto rev: 22cd22813a07c03f47810754a89916f629ce13cd) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: remove packagegroup-core-tools-profile.bbappendTom Zanussi2012-09-101-2/+0
| | | | | | | | | | | | The functionality previously added by these bbappends was already handled in task-core-tools-profile.bb (now packagegroup-core-tools-profile.bb), so remove this. (From meta-yocto rev: e999a6639a711f5c9a64c69d6b89fb478566d34a) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-internal: New qemu calls it qemu-system-i386 for x86Khem Raj2012-09-101-1/+1
| | | | | | | | | | | New qemu calls the x86 system emulator to be qemu-system-i386 which is consistent now so change it in scripts (From OE-Core rev: b1ccf0202ba66f9be76463df177f11719ab589e8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimagetest: modifying the scenario file as per new test casesVeerabrahmam vr2012-09-1010-0/+30
| | | | | | | | | | modified scenario files. (From OE-Core rev: dfd2ead41846c568d251a47c4baa2d9666e0c98f) Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimagetest: add basic function to check syslogdVeerabrahmam vr2012-09-102-0/+71
| | | | | | | | | | one test case to check syslogd is executing on target. (From OE-Core rev: 9286ea7a4eb85ba559d48135458f3b94da7a3866) Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimagetest: add basic function to check enough disk spaceVeerabrahmam vr2012-09-102-0/+79
| | | | | | | | | | one test case to check disk space availability. (From OE-Core rev: d7b549a72a91db41d8b7084b4b3efa162a62a880) Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimagetest: basic function to check bash existsVeerabrahmam vr2012-09-102-0/+70
| | | | | | | | | | | one test case to check bash command availability on qemu target. Signed-off-by: veerabrahmam <veerabrahmamvr@huawei.com> (From OE-Core rev: 357478b624b27fdfce25b6064b0f64717db75fa6) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/cleanup-workdir: change autoconf-nativesdk to nativesdk-autoconfJack Mitchell2012-09-041-1/+1
| | | | | | | | | the autoconf-nativesdk package name was recently changed to nativesdk-autoconf which in turn broke the cleanup-workdir script. Changed the package to the correct name. (From OE-Core rev: 0df6904f8050c4305d90d9bb4c9cac279508d9ca) Signed-off-by: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto: fix for task renamePaul Eggleton2012-09-042-2/+2
| | | | | | | (From meta-yocto rev: da4717580cc06dfc3168acf22fe8e4e2f79f4b95) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: fix remove_duplicated when multiple archs were builtMartin Jansa2012-09-041-25/+27
| | | | | | | | | | | | * The problem is that you're looking for duplicates across all available archs, so armv4t and armv7a populate_sysroot are considered duplicate and only last one is kept, but to rebuild from sstate-cache you need both! (From OE-Core rev: 46309e96300c35f6e8a5f33512a6a38720c629d2) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: add option to enable debug outputMartin Jansa2012-09-041-0/+15
| | | | | | | | (From OE-Core rev: 97a6b51c776bbcde14101834fdf9e1d19ae19185) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: don't hardcode available machines only to qemu*Martin Jansa2012-09-041-1/+3
| | | | | | | | | | * find them dynamically in layers like AVAILTUNES (From OE-Core rev: fb6d838b1b80f26e9261acfd3893a7ef7f9e1940) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: look in meta* above oe-core dir when looking for ↵Martin Jansa2012-09-041-2/+4
| | | | | | | | | | | | available tunes * many layouts have other layers on the same level as oe-core checkout (From OE-Core rev: 6faf27b771176ff691c17a2dbfa98ac7b3ed1fc7) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: fix regexp in AVAILTUNES grepMartin Jansa2012-09-041-1/+1
| | | | | | | | | | | | * it was also picking line openembedded-core/meta/conf/machine/include/README:AVAILTUNES - This is a list of all of the tuning definitions currently filling all_archs with wrong entries (From OE-Core rev: ceeefd964026e11ce0bb3b0285dbf9917533ae5e) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: fix regexp in checksum grepMartin Jansa2012-09-041-1/+1
| | | | | | | | | | * using checksum without recipe/task name doesn't seem like good idea IMHO (From OE-Core rev: ef1044da4b30b9a1264a7c83727a722a4b0b60cc) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename task to packagegroupPaul Eggleton2012-09-041-1/+1
| | | | | | | | | | | | "Package group" is a much more appropriate name for these than task, since we use the word task to describe units of work executed by BitBake. (From OE-Core rev: 424dcf7046e4ad09dcc664eb1992201195247fcf) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add new strip_base() functionTom Zanussi2012-09-021-0/+10
| | | | | | | | | | | Add a strip_base() function to remove '/base' from the branch names presented to the user. (From meta-yocto rev: 216a38f6bb453e8e6617f82c3642151dbde2f377) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add a LICENSE_FLAGS_WHITELIST blurb for emgd to READMETom Zanussi2012-09-021-0/+8
| | | | | | | | | | | | Add a text snippet to the README to say that if emgd-driver-bin is included in the BSP, LICENSE_FLAGS_WHITELIST needs to be set to for a successful build. (From meta-yocto rev: e9437a58a99eefa23402b82a1d9a85e7381e109f) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: update the help regarding the meta-intel layerTom Zanussi2012-09-021-6/+6
| | | | | | | | | | | | | | With move of ia32-base to oe-core, the only case remaining where meta-intel needs to be added to bblayers.conf for a new BSP is the case of an x86 BSP that selects EMGD. Update the documentation to note that fact. (From meta-yocto rev: b63c199c716d68147def036eb06481245e595802) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: include meta-intel.inc if emgd selectedTom Zanussi2012-09-021-0/+2
| | | | | | | | | | | | | | | With move of ia32-base to oe-core, the intel-specific variables were split off into meta-intel.inc, which needs to be included when using components present only in meta-intel. In the case of i386, that's currently just emgd, so conditionally include emgd if emgd is selected as the xserver choice. (From meta-yocto rev: b9cc7ce3407d3bc3909e7cc57c8a1290cb84a58b) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bsp: set default XSERVER for PowerPC and MIPS machines to XorgRoss Burton2012-09-022-4/+10
| | | | | | | | (From meta-yocto rev: f43d6ca8ecd96321d62b11b5db3bb2a6de873939) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* crosstap: new scriptTom Zanussi2012-09-021-0/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This script makes it easy to run a systemtap script on a remote target from a build host. The script itself contains documentation on basic setup and usage - see that for details. In a nutshell, if you have a systemtap script on the build host, this script allows that systemtap script to be compiled and run on the target host and for the output appear on the host terminal. The crosstap script requires to an sdk build of the target (or a build with 'tools-profile' added to EXTRA_IMAGE_FEATURES) because it needs to be able to run the native systemtap built by the systemtap recipe, which in turn needs access to the kernel built for the target in order to build the kernel modules that implement the systemtap probe specified by the systemtap script and which ultimately get shipped to the target and insmod'ed there. The crosstap script also needs to be able to ssh to the target host in order insert the modules on the target, so the target system needs to support incoming ssh connections. (From OE-Core rev: c6da6b648328377ba3590fd38cb12dad26a46a13) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: fix it for downloaded fileRobert Yang2012-08-301-1/+19
| | | | | | | | | | | | | | | | | | Fix it for the downloaded sstate cache file * The downloaded sstate cache file is in SSTATE_DIR, and there is a symlink points to it, the sstate cache file should not be removed if the corresponding symlink is kept, it would be removed when the symlink is removed (with -L option). * Fix a comment line. [YOCTO #2897] (From OE-Core rev: 12ed7e6bb215e70b119d5ce123e36e2fd380ff1e) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: use KBRANCH_DEFAULT in 'newbranch' casesTom Zanussi2012-08-2924-24/+48
| | | | | | | | | | | | | | | The new yocto-kernel way of specifying that the branch sanity check doesn't need to be run is to specify a default kbranch and build that. In the case where we have a new kbranch but it's not yet in the repo, we need to tell it that our new branch is the default and we're building the default and that's how we avoid the sanity check and the subsequent do_validate_branches() failure. (From meta-yocto rev: dadd020c67e901609be3ac13a4ffd8cb28532966) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: remove obsolete referencesTom Zanussi2012-08-297-18/+0
| | | | | | | | | | | | The logbuf-normal feature is obsolete, so remove any references to it. The dmaengine and hpet features have changed, but don't really need to be added by default to i386 - leave that to the BSP developer. Also, remove a couple duplicate feature references in the .scc files. (From meta-yocto rev: 3f37864d474912d680c2e6ee2a962e9fa61df39b) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-export-rootfs and friends: don't put pseudo db in target fsPeter Seebach2012-08-292-7/+10
| | | | | | | | | | | | | | | | | | | | In a few places, we have scripts which use <rootfs>/var/pseudo for the pseudo state directory controlling a given filesystem. This seems possibly risky because it means that stuff running under qemu or whatnot could wipe out the data being used to handle that rootfs. Move this to: <rootfs>/../$(basename_rootfs).pseudo_state to avoid problems. This also solves at least one case (not directly hit by yocto's tree) wherein you could end up trying to remove a rootfs while pseudo was using a database inside that rootfs, and thus the remove would fail. (From OE-Core rev: aa5d6bd006d3b4eede21d8987451876ed3385ab8) Signed-off-by: Peter Seebach <peter.seebach@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: compile tar-replacement firstlyRoy.Li2012-08-291-1/+6
| | | | | | | | | | | | | | | | | | | | | Compiling tar-replacement or not is decided by version of host tar, if the host tar version is lower than 1.23, Compiling tar-replacement is needed. When doing popoluate tar-replacement sysroot to write the tar to sysroot, but writing is not finished. other packages probably use the being written tar to unzip file, which will lead to failure and report the below error: "bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/tar: Text file busy" Now we compile tar-replacement firstly to ensure that a being written tar command will not be used. (From OE-Core rev: 3c1c4719fc96f6f1fbb257413d6baf3d91fdf4e8) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add missing xserver-xf86-config .bbappend for qemuTom Zanussi2012-08-251-0/+2
| | | | | | | | | | Re-add xserver-xf86-config which was inadvertently removed. (From meta-yocto rev: 08c0c5c53ba625f28eb243968c9c3844ba99d780) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: use base branches for qemu 'newbranch' caseTom Zanussi2012-08-254-8/+8
| | | | | | | | | | | The branch updating for the [YOCTO #2587] fix inadvertently changed some of the qemu branch names incorrectly, fix it. (From meta-yocto rev: dde4cd9f88093b8c520a6a42f9dda917f4aff5e4) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: remove YOCTO_KERNEL_EXTERNAL_BRANCH usageTom Zanussi2012-08-2524-82/+0
| | | | | | | | | | | YOCTO_KERNEL_EXTERNAL_BRANCH is now obsolete, so remove it from the templates. (From meta-yocto rev: 0c440984f3f429d5282559208313dfe7492b8b90) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: use emgd 1.14 for i386 templateTom Zanussi2012-08-252-5/+5
| | | | | | | | | | Make i386 template use emgd 1.14, along with associated changes. (From meta-yocto rev: 69f49f7e8370112164b70b9a5ae6f3c0e1ce0bfa) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: update standard branch mappingTom Zanussi2012-08-251-3/+3
| | | | | | | | | | Remove mapping for 3.0 and add mapping for 3.4. (From meta-yocto rev: e4ddfcda2cc6aad0c3e99066d43d69f5c1ab2f18) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add 3.4/remove 3.0 kernel from templatesTom Zanussi2012-08-2523-155/+152
| | | | | | | | | | For 1.3, 3.4 is the preferred kernel and 3.0 isn't supported. (From meta-yocto rev: ef7f8257ec9830e3eab0acec20564105d23a74f7) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: generate default properties even if json specifiedTom Zanussi2012-08-251-2/+2
| | | | | | | | | | | | | Users seem to want to specify incomplete property sets when using json input. Allow this by generating default properties before the user-specified properties are applied; the user will then get the defaults for any unspecified values, and avoid cryptic backtraces. (From meta-yocto rev: 3f0361f77cf64844da93ba4a76c42cd5befff5ad) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: use emgd 1.10 for i386 templateTom Zanussi2012-08-253-4/+9
| | | | | | | | | | | Make i386 template use emgd 1.10 for denzil, along with associated changes. (From meta-yocto rev: 7a93139bcaca7639da0f182356153d2a7539e0c3) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add i586 option for i386Tom Zanussi2012-08-251-2/+5
| | | | | | | | (From meta-yocto rev: e5bc15354dccd7ecff3cc61af4299befb9d2bc86) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add some standard policyTom Zanussi2012-08-254-0/+28
| | | | | | | | | | Add some useful default options to to the i386 and x86_64 templates. (From meta-yocto rev: 2f98c6dfce82d670acf54bb93c827cf142539b98) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 13:03:29 +0000