summaryrefslogtreecommitdiffstats
path: root/meta/classes/image_types.bbclass
AgeCommit message (Collapse)Author
2015-02-11image_types.bbclass: manage 'cpio_append' directoryEnrico Scholz
For cpio images, do_rootfs() can operate on a dirty '${WORKDIR}/cpio_append' directory which contains e.g. files from previous builds. This can cause unwanted files in the image or can break the build. E.g. when there is a cpio_append/init -> /sbin/init symlink symlink, the 'ln -sf' can fail due to SELinux restrictions: | $ ls -la cpio_append/init | lrwxrwxrwx. 1 ensc ensc 10 22. Jan 16:26 cpio_append/init -> /sbin/init | | $ strace ln -sf /sbin/init cpio_append/init | ... | stat("cpio_append/init", 0x7fffbb9ca310) = -1 EACCES (Permission denied) | exit_group(1) = ? Patch cleans up 'cpio_append' before executing the 'do_rootfs' task by adding it to 'cleandirs'. An alternative implementation (which avoids creation of this empty dir for non-cpio images) might remove it within IMAGE_CMD_cpio, but this might break builds where people rely on the existence of this directory (e.g. to add local files). (From OE-Core rev: 4db3cc2360289c062fa0df4678f2f2ef990f0c1a) (From OE-Core rev: 5a5802b15d965f62bf61697e1dbffab89702da96) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-11image_types.bbclass: fixed 'init' creation for cpio imagesEnrico Scholz
When /init is a dangling symlink or a symlink to a file which can not be stated on the build system (e.g. due to SELinux restrictions), the '[ ! -e .../init ]' test will succeed which causes the manual creation of /init. E.g. here: | $ ls -la cpio_append/init | lrwxrwxrwx. 1 ensc ensc 10 22. Jan 16:26 cpio_append/init -> /sbin/init | | $ strace /bin/test -e cpio_append/init | stat("cpio_append/init", 0x7fff374a9db0) = -1 EACCES (Permission denied) | exit_group(1) = ? To test for the existence of a file, both '-L' and '-e' checks must be executed and to prevent SELinux noise, the '-L' should happen before '-e'. (From OE-Core rev: 2aa5d2880ee3578f4965f245addd365fb7b1c1ca) (From OE-Core rev: f8d3bee7140cade4c70a1c6583fb6d9ef4063b92) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-31image_types.bbclass: Populate cpio /init as symlinkNathan Rossi
For cpio/ramfs the kernel will first attempt to execute /init and will emit the following error as the file is empty: Failed to execute /init (error -13) If /sbin/init exists symlink to it so the kernel can immediately start the correct init executable instead of an empty file. (From OE-Core rev: 3505558e067fdde4ab7aaaf3c50886f292d7c166) (From OE-Core rev: 40bf6d0d71bd534fadcbc07b6fbba856e50bc534) Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-31image_types.bbclass: Make ubi depend on ubifsPascal Bach
The ubi command assumes the ubifs file is present. This makes sure this is really the case. (From OE-Core rev: 0a947408f32d7ab10d2004e7d9332296b82191a3) (From OE-Core rev: 0fff562384670b64ed207423b7f596c99baa71c4) Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-08-15Support image type "squashfs-lzo"Mike Looijmans
Add "squashfs-lzo" to the image types. LZO compression support has been in both kernel and squashfs tools for many years, but OE never enabled it. (From OE-Core rev: ab659b1c1e13fd6863893abff86990d88aa36790) Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-06-03image_types: Fix ubi filesystem return codesRichard Purdie
If the first command returns an error, it will not cause the image generation step to fail. Simply split up the statement into multiple lines to avoid this issue, they no longer need to be one line expressions. [YOCTO #6391] (From OE-Core rev: f8125a1e9b6893a12355d55d4df584a8d97f0bff) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-03-27cpio rootfs build: Avoid modifying rootfs dirJonas Eriksson
The Linux kernel requires that initrd images contain a /init file for the image to be used as an initrd, even if it is empty. Adding it into the rootfs directory creates a race, that can upset tar when building both a .tar and .cpio image file ("tar: .: file changed as we read it"). Additionally, whether or not the tar file will contain the /init file is also up to the race condition. To avoid this problem, move the /init addition out from the rootfs directory, and thus only include it in the .cpio image. (From OE-Core rev: 706055503f493a5af73240c0983c46dbe31d8fe9) Signed-off-by: Jonas Eriksson <jonas.eriksson@enea.com> Signed-off-by: Josep Puigdemont <josep.puigdemont@enea.com> Cc: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-03-21image_types.bbclass: use 4096 instead of 8192 bytes-per-inodeRobert Yang
The image not correctly created if 'ptest-pkgs' is in IMAGE_FEATURES, this is because there is no free inode left. We can use 4096 instead of 8192 bytes-per-inode to fix the problem, and most of the distributions us 4096, such as Ubuntu, Suse, Fedora and CentOS. There are another problems: * There are error message when there is no free inode left if we run the mke2fs command manually, but they are not in log.do_rootfs. * The image generation doesn't stop when error happens because mke2fs doesn't return failed for this case. Will fix them in other threads. [YOCTO #5957] (From OE-Core rev: 09ab3a00598d06e3a1bf871811c2ac37359c74da) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-03-07image_types.bbclass: use mke2fs -d to create the ext2/3/4 imageRobert Yang
We used populate-extfs.sh which invoked the debugfs to create the image, now the mke2fs' option "-d root-directory" can do the same thing, and which is more faster, for example, the core-imag-sato: * In the past: $ time mke2fs -t ext4 rootfs.ext4 real 0m0.249s user 0m0.036s sys 0m0.132s $ time populate-extfs.sh /path/to/rootfs/ rootfs.ext4 real 0m29.355s user 0m10.637s sys 0m5.544s * Now: $ time mkfs.ext4 -F -d /path/to/rootfs/ rootfs.ext4 real 0m6.338s user 0m3.824s sys 0m1.356s More than 25 seconds are saved. [YOCTO #4083] (From OE-Core rev: 6338fe9ba338615317a4e7ccc99287b236ac77ae) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-21image_types.bbclass: fix cpio IMAGE_CMD to preserve working directoryJonathan Liu
The working directory is changed in a subshell when executing cpio to preserve the working directory for any subsequent commands. This is to keep the working directory consistent when generating multiple image types. (From OE-Core rev: 5ff6cb920f8be9068a23f7bf0cb1b9a9ff1eda5b) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-20image*.bbclass, bootimg.bbclass: add image type dependenciesLaurentiu Palcu
The following dependencies were manually added in the image creation code. However, in order to have an image dependency mechanism in place, use a new variable, IMAGE_TYPEDEP, to declare that an image type depends on another being already created. The following dependencies are added by this commit: elf -> cpio.gz live -> ext3 vmdk -> ext3 iso -> ext3 hddimg -> ext3 This commit adds also another new variable: IMAGE_TYPES_MASKED. Currently, masking out certain types from IMAGE_FSTYPES was hardcoded in the image creation code. [YOCTO #5830] (From OE-Core rev: 5e2796aa28e02ae3a076c6593c6533753720b13d) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-20image_types: minor, inline CPIO_TOUCH_INIT()Matthieu Crapet
Since generic compression solution has been introduced (see revision b7e4ed41ee480f00b7265341e9e2d2c2b9135143), CPIO_TOUCH_INIT() is only called by IMAGE_CMD_cpio. (From OE-Core rev: e856e04e6134ce98e89027864f69b2ab48d40dcc) Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-18image_types.bbclass: Fix tar IMAGE_CMD to not change directories1.6_M3.final1.6_M3Khem Raj
below commit commit 9d9bca8785911e8ae06d507bbfb99d6a811f072e Author: Jonathan Liu <net147@gmail.com> Date: Mon Feb 17 21:46:28 2014 +1100 lib/oe/image.py: fix working directory The working directory needs to be changed before the image creation commands instead of afterwards. exposed an issue when generating tar images, where it would cd into rootfs and then create the rootfs tarball and remain there since the cmd to cd into deploy dir moved up the immediate following cmd like tar.bz2 or tar.gz were still looking for tarball in current directory which esentially was not deploy dir but IMAGE_ROOTFS instead (From OE-Core rev: 9a98b8bfe13b94d89a9e39cca821f26fdeaeffc3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-14image_types: sum.jffs2 is replaced by jffs2.sumDmitry Eremin-Solenikov
Previous commit added support for sum 'compression' (rather postprocessing) of jffs2 images. Drop support for sum.jffs2 image type. (From OE-Core rev: 295c6c1452c8789a8b1d0090ff09a5cd7cf16507) Signed-off-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-14image_types bbclass: use compression framework for jffs2 sum imagesDmitry Eremin-Solenikov
I got hit by a missing dependency in generation of sum.jffs2 images - at runtime, when images are generated using bitbake pool, it is possible for sum.jffs2 image to be scheduled for generation before jffs2 image is fully generated. Insted of adding additional hacks, reimplement sum.jffs2 generation as a compression scheme on top of plain jffs2 images. For now support for sum.jffs2 images is left in, it will be removed by the subsequent commit. (From OE-Core rev: 2a15a364fdf85b0b18ba63fdb2a745a52b96478e) Signed-off-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-11Activate the new python rootfs/image creation routinesLaurentiu Palcu
This commit will: * remove old bash code common to all backends; * create a new do_rootfs() python function that will use the new rootfs/image creation routines; * allow creation of dpkg based images; * fail for rpm/opkg (not implemented yet); (From OE-Core rev: a83144bac8d67704ff66f5dc0fc56f5b63979694) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-14image_types bbclass: add support for tar.lz4 and cpio.lz4Koen Kooi
(From OE-Core rev: 0a541a0497902ee9993449b47da853b6c6a306d9) Signed-off-by: Koen Kooi <koen.kooi@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-20image_types: newer btrfs.mkfs needs an empty file to build the disk inSaul Wold
(From OE-Core rev: 836396a3450e7bf151956e87bd92f70c5050c995) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-04image_types: Improve dependency handling between types (and use for sum.jffs2)Richard Purdie
We're seeing a pattern of one image type needing to depend on another type. A good example is jffs2 and sum.jffs2. This patch makes sum.jffs2 depend on jffs2 which will then allow a EXTRA_IMGAGECMD to be set for sum.jffs2 individually without changing the jffs2 command. This allows the -pad option to be configured differently. (From OE-Core rev: 4a05f4f03b7d710e9e19a97f5d2c35d101e2c648) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-26image_types.bbclass: fix endiannes for sumtool (jffs2 summary)Andrea Adami
For mkfs.jffs2 endianness can be be expressed in the long or short form with the optional size argument: --little-endian -l Strangely the sumtool has a different syntax and does accept the forms: --littleendian -l Prefer the short form valid for both tools. (From OE-Core rev: be566b6f77423f7f676bc6b0511966651d687871) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-26image_types.bbclass: do not force --no-cleanmarkers for jffs2Andrea Adami
(From OE-Core rev: b3249f238d669f5f2422207f9c4414b64e24eb73) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-14image types: split live into iso and hddimgValentin Popa
Changes to split live into iso and hddimg without adding a new image type class. This patch has only a visible effect on HOB and solves part 2 of #3197 [YOCTO #3197] (From OE-Core rev: f05ae5f57d9d1bd839fae0e3f353d4e0e303a183) Signed-off-by: Valentin Popa <valentin.popa@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-30image_types.bbclass: use mkfs.cramfs instead of makecramfsAndrea Adami
The former is provided by util-linux and the latter is now to be removed for meta-filesystems. This allows to generate cramfs images whithout extra layers. (From OE-Core rev: 451546a9d2f675ac331f72f4e66317685d931aba) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-26image_types.bbclass: replace genext2fs with populate-extfs.shRobert Yang
* The benefits: - Really support ext4 - Support the sparse file (we lost the sparse file in the image in the past, the sparse file became into the common file) - Fix the error reported by fsck: (ext2/ext3) Inode 1025, i_size is 16384, should be 17408. - Have a uniform code for ext2/3/4 generation * Comments from Darren Hart: Basically, genext2fs doesn't support creating ext4 filesystems. It creates, as I understand it, an ext2 filesystem, then adds a journal, and sets some bits. It can't support the newer features like extents. So what we end up with is a bit of a hack for a filesystem. The ext tools (e2fsprogs) unfortunately don't provide an integrated solution for generating prepopulated filesystem images as many other mkfs* tools do. One thing missing was symlink support in libext2fs. I added that support and demonstrated a script which uses the e2fsprogs debugfs tool that can populate the newly formatted filesystem from a directory and without root privileges. [YOCTO #3848] (From OE-Core rev: 40c3e18f43b2f074cec97d21aeb8d21f26dd5048) 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>
2013-06-28image_types.bbclass: set 'filetype' ext4 featureEnrico Scholz
Generating filesystems with this flag allows more efficient directory traversals because getdents() returns the filetype in 'd_type' which allows to avoid an extra lstat() call. Creating ext4 filesystems with 'mkfs.ext4' sets this flag by default too. (From OE-Core rev: 75e077025397f3bde84e60a9da2c0564ade09b39) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-07image_types.bbclass: add ubifs to IMAGE_TYPESAndrea Adami
* the IMAGE_TYPES variable is used exclusively by hob * IMAGE_CMD_ubifs is already present in the class * ubifs images can be flashed on existing ubi volumes with 'ubiupdatevol' (From OE-Core rev: 0dc5a90b2d95ad21025769b0300390a4ff0052ac) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-21image_types.bbclass: remove the old imagesRobert Yang
Remove the old image before the new one generated to save disk space when RM_OLD_IMAGE is set to 1, this is an easy way to keep the DEPLOY_DIR_IMAGE clean. [YOCTO #4391] (From OE-Core rev: b3e2e405c53d63bc71872d41f455507be833e7eb) 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>
2013-05-03image_types: fix default location of kernel when generating elf imagesTomas Frydrych
Generation of elf images fails because kernel images are no longer staged under ${STAGING_DIR_HOST}/kernel, but rather ${STAGING_DIR_HOST}/usr/src/kernel. This patch fixes the path to point to the correct location. (From OE-Core rev: 6e57a3231fb29f869d476b8511d6f4393f82651b) Signed-off-by: Tomas Frydrych <tomas@sleepfive.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-29image_types.bbclass: Replace squashfs-lzma with squashfs-xzMarc Ferland
Booting an image generated with squashfs-lzma results in a kernel error: "Filesystem uses "lzma" compression. This is not supported". Currently (well at least in Linux 3.8) the officially supported decompressors are: * LZO * XZ * ZLIB This change makes sure we use a supported compression algorithm for squashed root filesystems. (From OE-Core rev: d915e2e084257830c43f7f21af3aec24b7e1a211) Signed-off-by: Marc Ferland <ferlandm@sonatest.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-18image_types.bbclass: only create links if the target existsAndreas Oberritter
When creating images containing many partitions, rootfs.$type may not be available. (From OE-Core rev: cf8e9d8942fdddaac21fca46137120da959c814c) Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-16image_types.bbclass: Add and update comments regarding image types.Robert P. J. Day
Explain the elf/cpio.gz snippet of code, and update a comment to reflect the correct variable name. No functional change. (From OE-Core rev: 0ca4a3a25e4495bf6e2e3932c019bd15856faf55) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-19image_types: fix squashfs-lzma image creation1.3_M5.rc1Saul Wold
This removes the dependency on a seperate binary which we don't seem to have. So, use mksquashfs's -comp lzma to replace that functionality [YOCTO #3126] (From OE-Core rev: 8e82713724dfcb40f2ae24a166ec94f50f8b4cd0) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-14image_types.bbclass: Round up ROOTFS_SIZE after base_size checkAndrei Gherzan
If we round up ROOTFS_SIZE to IMAGE_ROOTFS_ALIGNMENT before checking if base_size is greater then IMAGE_ROOTFS_SIZE, we can end up adding an unaligned value to IMAGE_ROOTFS_SIZE. Obviously, if IMAGE_ROOTFS_EXTRA_SPACE was overwritten with an unaligned value. So let's add the round up code after the base_size calculus and it's comparison. (From OE-Core rev: 726c1617077da6b49606ac1a2cae64d2d02e6214) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-07image_types.bbclass: add variable for HobKang Kai
Add a new variable "IMAGE_EXTENSION_live" for Hob to map image type "live" with real image file extension names. This is for Hob to remove the hard-coded maps. (From OE-Core rev: fe0973df7c72b1acec7feae03a4e13c1f49c8b1f) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-19Convert tab indentation in python functions into four-spaceRichard Purdie
(From OE-Core rev: 604d46c686d06d62d5a07b9c7f4fa170f99307d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-17image_types.bbclass: Default XZ_COMPRESSION_LEVEL to -e -6Andrei Gherzan
Having XZ_COMPRESSION_LEVEL on -e -9 and -T 0 will make xz eat more than 6Gb memory. Reduce this to -6 to make xz to use about 471Mb on the tested machine. (From OE-Core rev: cfd201ecda95d00bc5d70aa5045c649b98ffe8b8) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-17image_types.bbclass: Add XZ variable to set number of threads to be used ↵Andrei Gherzan
while compressing Default this variable to 0. This will make xz use as many threads as there are CPU cores on the system. (From OE-Core rev: 81c8e8a81e90ce95042e9fff8bac6fa011c416d1) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-17image_types.bbclass: Fix COMPRESS_CMD for xz to redirect compressed data to fileAndrei Gherzan
Having -c modifier makes xz to output the compressed data to stdout. In this way the needed data will be in the do_rootfs log. Redirect data to ${IMAGE_NAME}.rootfs.${type}.xz . (From OE-Core rev: 7ceea61636d6a6f886002e3c29941da3356157ac) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-04image_types: Add elf image typeRaymond Danks
On x86, an ELF image file may be stored as a coreboot payload. The image file is constructed, using the mkelfimage utility, from a kernel and an initrd. (From OE-Core rev: 93e9de4e27919f59b6783d53f314df6e49ccb436) Signed-off-by: Raymond Danks <ray.danks@se-eng.com> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-05-09image_types.bbclass: redefine EXTRA_IMAGECMD_jffs2 to leverage siteinfoTing Liu
(From OE-Core rev: 7c803cea58737ea0abc62cd21c3813d955f07224) Signed-off-by: Ting Liu <b28495@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-27image_types: remove duplicate setting of -i for inode countSaul Wold
inode count is already set in the EXTRA_IMAGECMD definition (From OE-Core rev: db5a1785615f72a707c139a539c1cfa6c5bd0d23) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-26image_types.bbclass: Define runnable and deployable patternDongxiao Xu
Define runnable image type and machine pattern. Define deployable image type. (From OE-Core rev: 602a0aede00ec961ffb008619cc8f6ee4ae51f58) Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-13image_types: ensure .rootfs.ext3 is created before vmdk is created.Dexuan Cui
In the case of self-hosted-image.bb, IMAGE_FSTYPES = "vmdk", so the variables alltypes and subimages don't contain ext3, and .rootfs.ext3 won't be created, and finally the generated .hddimg and .vmdk don't have an actual rootfs -- the size of the .vmdk file is only about 9MB. [YOCTO #2067] (From OE-Core rev: 39f14c66d5df226689238810b759f502644deb5c) Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-08image_types: add IMAGE_ROOTFS_ALIGNMENTKen Werner
Introduce a new variable called IMAGE_ROOTFS_ALIGNMENT that allows to control the aligment of the size of the rootfs. Its default value is set to 1KiB so that the existing behaviour is not changed. In case the SD card emulation of a QEMU system emulator gets used you may set the alignment to 2MiB. (From OE-Core rev: 99128c209e3de3e9e175eacb3acf0f06857043fe) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-02image_types: Ensure duplicate compressed types aren't createdRichard Purdie
This allows IMAGE_FSTYPES = "tar.bz2 tar.bz2" to work (and now is faster since it will only do it once). (From OE-Core rev: b24d4bcde21b013e48eaffea5f3a70d8b1df1047) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-02image_types.bbclass: We need to preserve order in the types variable and ↵Richard Purdie
avoid set() (From OE-Core rev: c547169f7dfe043affc2ddc5ae0a9091379df6de) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-02image_types: Ensure dependencies for compression types containing multiple ↵Richard Purdie
dots are handled correctly This ensures dependencies for image types like ext2.gz.u-boot are handled correctly. (From OE-Core rev: d94cb18f7f17a492c7a948337d7d2d1d0785573f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-01image-vmdk: Create image_vmdk class and setup image and image_types to use itSaul Wold
This creates a new image_vmdk class similar to live. The image_vmdk class needs to have a hddimg created by the image-live class, so it inherits it directly. The changes to image_types is to ensure that both live and vmdk images get the ext3 tools and dependencies. (From OE-Core rev: aa961e112b07d42c272e01f2d69f3c139e9ae70f) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-02-29image_types: Correctness fixesRichard Purdie
* Add a newline to improve the output formatting * Use set() to turn the list into a set of unique items to prevnt the same image code running twice (for e.g. IMAGE_FSTYPES = "tar.gz tar.bz2") * Support multiple compression extensions such as ".gz.u-boot" * Fix basetype/type typo and fix multiple image generation (From OE-Core rev: eacedb4f2afa98dbd2f5ea7a9f52e6ea952a72d2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-02-29image_types.bbclass: fix bzip2 and xz compression commandsOtavio Salvador
We need to use -f (force) or the command fails in the image file already exists. (From OE-Core rev: 419ddab8266ecfd6da1841d38a451a9fc5be49b0) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-27 08:32:55 +0000