Francesco Pham authored 3 years ago and Stefan Schmidt committed 3 years ago

Adding ovmf to runqemu commands since we switched to GRUB+EFI as boot solution. 

Without this argument it does not boot properly and remains stuck in "Booting from Hard Disk..."

Signed-off-by: Francesco Pham <francesco.pham@huawei.com>

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>

Eilís Ní Fhlannagáin authored 3 years ago and Eilís Ní Fhlannagáin committed 3 years ago

Looking at allscenarios-image-common.inc I see some devel/dbg packages
in there. These really should be pulled into a development or debug
image as images that endusers would build off of for a production
environment should only contain the minimal packages needed to run the system.

This patch removes gdbserver and packagegroup-net-tools (iperf3) from common
and puts them along with other useful EXTRA_IMAGE_FEATURES into two new images:

allscenarios-image-base-dev
allscenarios-image-extra-dev

Due to the size of the dbg-pkgs and dev-pkgs,
allscenarios-image-extra-dev needs a bump of it's ROOT_PARTITION_SIZE
else wic creation explodes.

Closes <issues 123>

Signed-off-by: Eilís Ní Fhlannagáin <elizabeth.flanagan@huawei.com>

Ever since we've landed
https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/merge_requests/147 the way
to invoke `runqemu` has changed slightly. Update stale documentation
sections that were left out.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/67


Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

The OS will start to depend on a specific partition table and having to
maintain multiple qemu setups might not prove useful. Also, we have
encountered issues trying to boot wic images (disk images as opposed to
root filesystems) with qemu ARM machines.

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

This bundles a rather large rename of all the recipes, descriptions and
comments, with the exception of repositories referenced from gitee or
other third party system (e.g. launchpad PPAs or COPR repositories).

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@huawei.com>

Add general description of MACHINE and add bblayers to template.

Signed-off-by: Ettore Chimenti <ettore.chimenti@seco.com>

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Make a default machine first on the list and in bold (in README.md)
to avoid ambiguity.

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Since the default images have changed, switch to
the new ones recommended for OpenHarmony.

Signed-off-by: Zbigniew Bodek <zbigniew.bodek@huawei.com>

Having core-image-minimal as a default first-on-the-list image
can be misleading when adding new boards to the build system
as this image allows only to boot-up minimal system without
any features that the board may support in terms of connectivity, etc.

core-image-full-cmdline, likewise, does not include "kernel-modules"
and can cause similar confusion.

Closes: https://git.ostc-eu.org/OSTC/OHOS/meta-ohos/-/issues/7


Signed-off-by: Robert Drab <robert.drab@huawei.com>

Signed-off-by: Robert Drab <robert.drab@huawei.com>

Add required meta-layers to bblayers.conf.sample.
Add dependencies to local.conf.sample that provide necessary
packages to enable Ethernet, WiFi and Bluetooth connectivity.
Mention the board in README.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>

Copy of Poky sample files with default distro set
to poky and meta-ohos-foundation layer added

Signed-off-by: Robert Drab <robert.drab@huawei.com>