Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=1.2_M1 2011-11-30T22:18:08+00:00 2011-11-30T22:18:08+00:00 Darren Hart dvhart@linux.intel.com 2011-11-24T07:35:43+00:00 urn:sha1:77d5a0c4c47d18d7a477fa79dcf982a001201801 Condition building PCBIOS legacy images on MACHINE_FEATURES containing "pcbios" or not containing "efi". This ensures existing BSPs will continue to get the old PCBIOS legacy-only images. New BSPs can add "efi", "pcbios", or both. The images created likewise support one or the other or both. EFI-only ISO images are untested. (From OE-Core rev: be3fc8c07e84c654f55c5d09934dfbdc7ff7e2b6) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-11-30T22:18:08+00:00 Darren Hart dvhart@linux.intel.com 2011-11-24T01:56:12+00:00 urn:sha1:eb4aa3483b1129a7137983ed54596030a5ccba2b Create a new grub-efi.bbclass and integrate it into bootimg alongside the syslinux support. This new class uses the output from the grub-efi-native recipe. Thanks goes to Josef Ahmad <josef.ahmad@intel.com> for the original build_grub_cfg() routine. The EFI features are only added to the image if MACHINE_FEATURES contains "efi". The resulting images are therefor either legacy boot only (like they were originally) or legacy boot and EFI boot. A new "dummy.bbclass" was added to allow for the conditional include of grub-efi. This makes it so if efi support is not to be built in, we don't spend time building grub-efi-native just because the include adds the dependency. There is a bug in the mkdosfs tool from the dosfstools package which causes it to crash when the directory passed with the -d parameter contains sub-directories. An /EFI/BOOT directory is required for a proper EFI installation. Until it is fixed, we install to the top level directory for the hddimg. (From OE-Core rev: be95f54495bf9e03062f86b929c66cab6e385a03) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Josef Ahmad <josef.ahmad@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-11-30T22:18:08+00:00 Darren Hart dvhart@linux.intel.com 2011-11-24T00:41:32+00:00 urn:sha1:bcbd57aae576fa262c83f435bccf3bc3184e5506 Working towards a more generic bootimg.bbclass, pull out all syslinux specific bits and let syslinux.bbclass manage them directly. This introduces no functional changes to the images constructed and the behavior remains unchanged. (From OE-Core rev: 1915293688d348a765aa0bcdf01168c9fecd9842) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-11-30T22:18:07+00:00 Darren Hart dvhart@linux.intel.com 2011-11-24T00:01:21+00:00 urn:sha1:4cdd02fe10fb31c6506db1d29b82afb210b94b8a Separate the construction of the ISO image from that of the hddimg. This is part of the groundwork for creating a much more flexible live image builder. (From OE-Core rev: 2da25c7c6649757350782a939bcc7553c5c86570) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-11-18T14:24:52+00:00 Damien Lespiau damien.lespiau@intel.com 2011-11-10T18:29:50+00:00 urn:sha1:e1d4f7b871a2499ef7c1620a9c57fa24c84327a4 It's possible to create an "hybrid" iso image that you can both burn to a CD-Rom and dd to a USB key. isohybrid will create a valid boot sector for the USB key case. [YOCTO #1763] (From OE-Core rev: 321a7dc9d934f31aae27828ff8c56d6c69ecc665) Signed-off-by: Damien Lespiau <damien.lespiau@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-10-24T16:27:14+00:00 Otavio Salvador otavio@ossystems.com.br 2011-10-19T18:36:49+00:00 urn:sha1:29886aa676481deb594c17af3dca6a8aef7c0059 If an image sets NOHDD = "1" the HDD image won't be build. (From OE-Core rev: 23c5a83e877efe6d86618898dd181bb75f44aa71) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-10-04T22:11:11+00:00 Otavio Salvador otavio@ossystems.com.br 2011-10-02T17:20:38+00:00 urn:sha1:b6b2ca051be32566df2c5289a2ab5ba4a6b03aa8 (From OE-Core rev: 780685bbaf6d6f74aed77c412686592d6b9cf8e5) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-01-25T12:25:46+00:00 Dongxiao Xu dongxiao.xu@intel.com 2011-01-18T08:18:42+00:00 urn:sha1:7f41f1a8888a1f7f091101d19b9b0c4787f5a6fc This commit changes the sysroots path to be machine specific. Changes includes: 1) STAGING_DIR_TARGET and STRAGING_DIR_HOST points to machine specific paths. 2) task stamp files. Adding ${MACHINE} info into stamp files for do_populate_sysroots and do_package tasks. Add a BB_STAMPTASK_BLACKLIST to keep native, nativesdk, crosssdk, and cross-canadian stamp unchanged. 3) siteconfig path. Separate the site config path for different machines to avoid one machine adopting the cache file of another machine. 4) sstate. Add machine name to sstate manifest file. Change relocation code for sstate paths since sysroot is machine. Keep native, nativesdk, crosssdk, and cross-canadian unchanged. 5) toolchain scripts. Change the environment path to point to machine specific sysroots in toolchain scripts bbclass. 6) Relocate la files when populating to a different machine of the same architecture. 7) Exclude STAGING_DIR_TARGET and STAGING_DIR_HOST parameter from sstate siginfo since they contain ${MACHINE} information. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> 2010-03-25T17:09:15+00:00 Richard Purdie rpurdie@linux.intel.com 2010-03-25T17:09:15+00:00 urn:sha1:c328f161f8875dfcdc97da71d99782891ecf1ea4 Signed-off-by: Richard Purdie <rpurdie@linux.intel.com> 2010-03-25T14:09:06+00:00 Richard Purdie rpurdie@linux.intel.com 2010-03-25T14:09:06+00:00 urn:sha1:f89cd3158a95890e15c97de4009e688bee8bc087 Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>