| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| | |
Use IMGDEPLOYDIR
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Do not write directly to the IMAGE_DEPLOY_DIR but to the new
deploy directory IMGDEPLOYDIR.
Also change the image ending to match the image type name (from
otaimg to ota-ext4). This allows to use the automatic symlinking
and output artefact management too.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Do not write directly to the IMAGE_DEPLOY_DIR but to the new
deploy directory IMGDEPLOYDIR. This allows to use the automatic
symlinking too.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|\ \
| |/
|/| |
Extend ostree support
|
| |
| |
| |
| |
| |
| |
| | |
Use OSTREE_UPDATE_SUMMARY to automatically update summary after committing
to ostree repo
Signed-off-by: Luka Pivk <luka.pivk@toradex.com>
|
| |
| |
| |
| |
| |
| |
| | |
Use OSTREE_COMMIT_BODY write custom text to ostree body
Use OSTREE_COMMIT_SUBJECT to write custom subject
Signed-off-by: Luka Pivk <luka.pivk@toradex.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Almost all code in create_ota is either tar or ext4 specific. Move
the code directly into the respective IMAGE_CMD_ functions. This
gets rid of unnecessary work for the tar image and simplifies code.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|/
|
|
|
|
|
| |
OpenEmbedded makes sure that IMAGE_CMD_type gets only called if the
type is in IMAGE_FSTYPE. There is no need to explicitly check for it.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
|
|
| |
should be provisioned
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
From poky master
This fixes image builds but does not boot yet...
|
|
|
|
|
|
|
| |
Without this the build fails because the initramfs hasn't been build
before do_image_ostree. There should be a dependency through
virtual/kernel:do_deploy, but there is clearly some reason why this
isn't enough.
|
|
|
|
| |
Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reasoning here is to allow initramfs generated by this recipe
to be included in FIT.
To do so w/o changing openembedded-core (it allows only cpio format) -
init script should be able to execute from a rootfs (i.e. true initramfs),
not ramdisk (initrd).
See [1] for more information on these keywords.
The gist of this change is switch from `pivot_root` to `switch_root`.
This also allows to get rid of some clutter, since `switch_root` handles
transition to new sysroot all by itself.
Again, see [1] for details on these utility/syscall.
[1] https://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt
Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue is that when only vmlinuz-* file is present
(the case when both DTB and initramfs are in FIT),
libostree will assume that there is no initramfs at all and will supply
different init= parameter on the kernel command line
(aimed to boot directly from sysroot).
This effectively breaks boot process as init specified
on the kernel cmdline is not present in initramfs.
Solution is to basically create an empty initramfs-* file
when we use FIT.
The proper solution would be to make libostree aware of whether
we use FIT or not.
Note, to actually boot with initramfs in FIT - a change to u-boot
script (env) is needed which will remove explicit usage of initramfs.
Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
|
|
|
|
|
|
|
|
| |
This will reduce the level of indirection and improve compatibility
with the rest of OE.
For example, FIT that includes initramfs may now be built.
Signed-off-by: Yevgeny Popovych <yevgenyp@pointgrab.com>
|
| |
|
| |
|
|\
| |
| | |
image_types_ostree: no need to create boot/loader folders when creating ostree repo
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ostree repo
The boot/loader folders are only required at the deploy stage, which is
already created by image_types_ota.bbclass.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
| | |
|
|/
|
|
|
|
|
| |
Make garage-push logs more useful in case of errors when pushing to the
OTA+ server.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
| |
|
|
|
|
| |
See https://github.com/advancedtelematic/meta-updater-minnowboard/pull/6
|
|
|
|
| |
It needs a plain compressed file system and not an u-boot legacy image
|
|
|
|
|
|
|
| |
Make sure to use the custom target version when creating
installed_versions if defined by the user.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
|
| |
/boot/grub2/grub.cfg should reflect the grub.cfg used by the boot process
instead of being an empty file.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
|
|
|
|
| |
User is able to customize the init script via OSTREE_INITRAMFS_IMAGE but
there is no way to set INITRAMFS_FSTYPES as it gets defined by
sota.bbclass. Create a new variable called OSTREE_INITRAMFS_IMAGE to
handle the INITRAMFS_FSTYPES update, and also allow the user to override
it.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RAMDISK_EXT and IMAGE_FSTYPES of initramfs-ostree-image should not be
defined separately, because they are representing the same fstype of
a same initramfs image, or else, they turn out to be inconsistent if
the users change one of them.
So we use INITRAMFS_FSTYPES already defined in bitbake.conf, to be able
to set fstype for initramfs. And it should default to ext4.gz.u-boot or
ext4.gz depending on what OSTREE_BOOTLOADER is being set.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
|
|
| |
It can not determine the init manager is systemd by checking if
DISTRO_FEATURES contains 'systemd', change it to check
VIRTUAL-RUNTIME_init_manager instead.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
| |
Avoid exposing the sign repo after the build is completed.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
|
| |
Both values can be defined by the user, allowing a custom version id and
URL, which is specially useful for CI builds.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
| |
sota_raspberrypi can handle the rpi differences if required.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
|
| |
As a image_types_* bbclass, it does not have to inherit image class, it
is sort of redundant code.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
|
| |
As a image_types_* bbclass, it does not have to inherit image class, it
is sort of redundant code.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
| |
We should also do this in the recipes
|
|\
| |
| | |
Stop forcing Linux 4.4 on qemux86-64
|
| |
| |
| |
| | |
The mentioned issue doesn't seem to exist anymore
|
|/
|
|
|
|
| |
Includes the suggestion for using /etc/sota/sota.env if it exists as
recommended by the discussion here:
https://github.com/advancedtelematic/meta-updater/pull/275
|
|\
| |
| | |
Use FIT image on RPi
|
| | |
|
|/
|
| |
calculate_size had a typo that made one of the cases fail. This patch fixes it.
|
|\ |
|
| |\
| | |
| | | |
Deploy initial primary version information
|
| | | |
|
| |/
| |
| |
| | |
Additionally don't create extra images to save space and not confuse the user
|