| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 2 - local: '/.gitlab-ci.d/buildtest-template.yml'
4 build-system-alpine:
6 - .native_build_job_template
7 - .native_build_artifact_template
9 - job: amd64-alpine-container
12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu
13 MAKE_CHECK_ARGS: check-build
14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog
16 check-system-alpine:
19 - job: build-system-alpine
[all …]
|
| /openbmc/linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm-test-1-run.sh | 2 # SPDX-License-Identifier: GPL-2.0+
4 # Run a kvm-based test of the specified tree on the specified configs.
8 # because qemu does not seem to like that much.
10 # Usage: kvm-test-1-run.sh config resdir seconds qemu-args boot_args_in
12 # qemu-args defaults to "-enable-kvm -display none -no-reboot", along
19 # Anything you specify for either qemu-args or boot_args_in is appended to
20 # the default values. The "-smp" value is deduced from the contents of
29 T="`mktemp -d ${TMPDIR-/tmp}/kvm-test-1-run.sh.XXXXXX`"
30 trap 'rm -rf $T' 0
36 config_dir=`echo $config_template | sed -e 's,/[^/]*$,,'`
[all …]
|
| H A D | kvm-recheck.sh | 2 # SPDX-License-Identifier: GPL-2.0+
4 # Given the results directories for previous KVM-based torture runs,
5 # check the build and console output for errors. Given a directory
8 # Usage: kvm-recheck.sh resdir ...
16 T=/tmp/kvm-recheck.sh.$$
17 trap 'rm -f $T' 0 2
26 dirs=`find $rd -name Make.defconfig.out -print | sort | sed -e 's,/[^/]*$,,' | sort -u`
29 if test -n "$firsttime"
32 resdir=`echo $i | sed -e 's,/$,,' -e 's,/[^/]*$,,'`
33 head -1 $resdir/log
[all …]
|
| /openbmc/qemu/docs/about/ |
| H A D | build-platforms.rst | 1 .. _Supported-build-platforms:
3 Supported build platforms
6 QEMU aims to support building and executing on multiple host OS
7 platforms. This appendix outlines which platforms are the major build
9 minimum required versions of 3rd party software QEMU depends on. The
14 If a platform is not listed here, it does not imply that QEMU won't
21 support targets, QEMU considers only the version number, and assumes the
24 software in their distro, QEMU upstream code will not add explicit
25 support for those backports, unless the feature is auto-detectable in a
33 ----------------------------
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | gobject-introspection.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 is the standard mechanism for accessing GObject-based software from
20 GObject Introspection Repository (GIR) files go to ``-dev`` packages,
28 Generating this data in a cross-compilation environment is difficult
30 code needs to be executed on the build host. This problem is solved with
31 the OpenEmbedded build system by running the code through QEMU, which
32 allows precisely that. Unfortunately, QEMU does not always work
33 perfectly as mentioned in the ":ref:`dev-manual/gobject-introspection:known issues`"
42 #. Inherit the :ref:`ref-classes-gobject-introspection` class.
46 "gobject-introspection-data" is not in
[all …]
|
| H A D | wic.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 OpenEmbedded build system does not necessarily mean you can boot that
16 OpenEmbedded build artifacts. Image generation is driven by partitioning
21 ":ref:`dev-manual/wic:generate an image using an existing kickstart file`"
22 section. When you apply the command to a given set of build artifacts, the
29 ":ref:`ref-manual/kickstart:openembedded kickstart (\`\`.wks\`\`) reference`"
36 ":ref:`dev-manual/wic:using the wic plugin interface`" section
50 - The name "Wic" is derived from OpenEmbedded Image Creator (oeic). The
54 - Wic is loosely based on the Meego Image Creator (``mic``) framework.
56 of OpenEmbedded build artifacts instead of package installation and
[all …]
|
| /openbmc/docs/development/ |
| H A D | devtool-hello-world.md | 4 in QEMU.
7 [Document](https://github.com/openbmc/docs/blob/master/development/dev-environment.md)
9 ## Clone and Build a Repo
16 [phosphor-state-manager](https://github.com/openbmc/phosphor-state-manager.git)
25 devtool modify phosphor-state-manager
33 vi workspace/sources/phosphor-state-manager/bmc_state_manager_main.cpp
43 @@ -17,6 +18,8 @@ int main(int argc, char**)
55 This will be a much faster build as bitbake will utilize all of the cache
56 from your previous build, only building what is new.
59 bitbake obmc-phosphor-image
[all …]
|
| /openbmc/openbmc/poky/documentation/brief-yoctoprojectqs/ |
| H A D | index.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Yocto Project Quick Build
11 image build using the Yocto Project. The document also introduces how to
12 configure a build for specific hardware. You will use Yocto Project to
13 build a reference embedded OS called Poky.
17 - The examples in this paper assume you are using a native Linux
19 you want to use Yocto Project on to build an image
20 (:term:`Build Host`) is not
23 :ref:`dev-manual/start:setting up to use cross platforms (crops)`
28 - You may use version 2 of Windows Subsystem For Linux (WSL 2) to set
[all …]
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-1.7.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
9 .. _migration-1.7-changes-to-setting-qemu-packageconfig-options:
11 Changes to Setting QEMU ``PACKAGECONFIG`` Options in ``local.conf``
12 -------------------------------------------------------------------
14 The QEMU recipe now uses a number of
18 append to :term:`PACKAGECONFIG` for ``qemu-native`` and ``nativesdk-qemu``
20 QEMU, you should now have these lines in ``local.conf``::
22 PACKAGECONFIG_append_pn-qemu-native = " sdl"
23 PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
25 .. _migration-1.7-minimum-git-version:
[all …]
|
| H A D | migration-2.2.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
9 .. _migration-2.2-minimum-kernel-version:
12 ----------------------
16 AArch64-based targets the version is 3.14. For Nios II-based targets,
24 .. _migration-2.2-staging-directories-in-sysroot-simplified:
27 --------------------------------------------------
33 :oe_lists:`v2 patch series on the OE-Core Mailing List
34 </pipermail/openembedded-core/2016-May/121365.html>`
37 .. _migration-2.2-removal-of-old-images-from-tmp-deploy-now-enabled:
40 -------------------------------------------------------------------
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci-definitions.rst.inc | 5 what is currently used on QEMU.
8 ---------------
19 3. An assertion, comparing the result from the previous call with the expected
25 ------------
34 On QEMU, unit testing is represented by the 'check-unit' target from 'make'.
37 ------------------
46 On QEMU, functional testing is represented by the 'check-qtest' target from
50 --------------
57 testing focuses on interactions, use case-based testing is a practical approach
59 interaction with third-party software, like operating system images, databases,
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-mitchell/conf/templates/default/ |
| H A D | local.conf.sample | 15 MACHINE ??= "mtmitchell-dcscm"
20 # During a first build the system will download many different source code tarballs
26 # The default is a downloads directory under TOPDIR which is the build directory.
31 # Where to place shared-state files
37 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
42 # The default is a sstate-cache directory under TOPDIR.
44 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
47 # Where to place the build output
66 DISTRO ?= "openbmc-phosphor"
71 # DISTRO ?= "poky-bleeding"
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-jefferson/conf/templates/default/ |
| H A D | local.conf.sample | 20 # During a first build the system will download many different source code tarballs
26 # The default is a downloads directory under TOPDIR which is the build directory.
31 # Where to place shared-state files
37 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
42 # The default is a sstate-cache directory under TOPDIR.
44 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
47 # Where to place the build output
66 DISTRO ?= "openbmc-phosphor"
71 # DISTRO ?= "poky-bleeding"
80 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-jade/conf/templates/default/ |
| H A D | local.conf.sample | 20 # During a first build the system will download many different source code tarballs
26 # The default is a downloads directory under TOPDIR which is the build directory.
31 # Where to place shared-state files
37 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
42 # The default is a sstate-cache directory under TOPDIR.
44 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
47 # Where to place the build output
66 DISTRO ?= "openbmc-phosphor"
71 # DISTRO ?= "poky-bleeding"
80 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-hpe/meta-dl385-g11/conf/templates/default/ |
| H A D | local.conf.sample | 16 # You need to select a specific machine to target the build with. There are a selection
17 # of emulated machines available which can boot and run in the QEMU emulator:
25 #MACHINE ?= "qemux86-64"
30 #MACHINE ?= "beaglebone-yocto"
32 #MACHINE ?= "genericx86-64"
33 #MACHINE ?= "mpc8315e-rdb"
36 # This sets the default machine to be qemux86-64 if no other machine is selected:
37 MACHINE ??= "dl385-g11"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-palmetto/conf/templates/default/ |
| H A D | local.conf.sample | 17 # You need to select a specific machine to target the build with. There are a selection
18 # of emulated machines available which can boot and run in the QEMU emulator:
26 #MACHINE ?= "qemux86-64"
31 #MACHINE ?= "beaglebone-yocto"
33 #MACHINE ?= "genericx86-64"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
53 # Where to place shared-state files
59 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
64 # The default is a sstate-cache directory under TOPDIR.
[all …]
|
| /openbmc/openbmc/meta-amd/meta-daytonax/conf/templates/default/ |
| H A D | local.conf.sample | 17 # You need to select a specific machine to target the build with. There are a selection
18 # of emulated machines available which can boot and run in the QEMU emulator:
25 #MACHINE ?= "qemux86-64"
32 #MACHINE ?= "genericx86-64"
33 #MACHINE ?= "mpc8315e-rdb"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
53 # Where to place shared-state files
59 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
64 # The default is a sstate-cache directory under TOPDIR.
[all …]
|
| /openbmc/openbmc/meta-amd/meta-ethanolx/conf/templates/default/ |
| H A D | local.conf.sample | 17 # You need to select a specific machine to target the build with. There are a selection
18 # of emulated machines available which can boot and run in the QEMU emulator:
25 #MACHINE ?= "qemux86-64"
32 #MACHINE ?= "genericx86-64"
33 #MACHINE ?= "mpc8315e-rdb"
42 # During a first build the system will download many different source code tarballs
48 # The default is a downloads directory under TOPDIR which is the build directory.
53 # Where to place shared-state files
59 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
64 # The default is a sstate-cache directory under TOPDIR.
[all …]
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | orangepi.rst | 1 Orange Pi PC (``orangepi-pc``)
5 based embedded computer with mainline support in both U-Boot
6 and Linux. The board comes with a Quad Core Cortex-A7 @ 1.3GHz,
15 * SMP (Quad Core Cortex-A7)
20 * Timer device (re-used from Allwinner A10)
36 - Graphical output via HDMI, GPU and/or the Display Engine
37 - Audio output
38 - Hardware Watchdog
41 for a complete list of unimplemented I/O devices: ``./hw/arm/allwinner-h3.c``
46 The Orange Pi PC machine can start using the standard -kernel functionality
[all …]
|
| /openbmc/qemu/roms/ |
| H A D | Makefile | 2 vgabios_variants := stdvga cirrus vmware qxl isavga virtio bochs-display ramfb ati
3 vgabios_targets := $(subst -isavga,,$(patsubst %,vgabios-%.bin,$(vgabios_variants)))
7 pxe-rom-e1000 efi-rom-e1000 : VID := 8086
8 pxe-rom-e1000 efi-rom-e1000 : DID := 100e
9 pxe-rom-e1000e efi-rom-e1000e : VID := 8086
10 pxe-rom-e1000e efi-rom-e1000e : DID := 10d3
11 pxe-rom-eepro100 efi-rom-eepro100 : VID := 8086
12 pxe-rom-eepro100 efi-rom-eepro100 : DID := 1209
13 pxe-rom-ne2k_pci efi-rom-ne2k_pci : VID := 1050
14 pxe-rom-ne2k_pci efi-rom-ne2k_pci : DID := 0940
[all …]
|
| /openbmc/openbmc/meta-yadro/meta-vegman/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-bletchley/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-catalina/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-greatlakes/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-tiogapass/conf/templates/default/ |
| H A D | local.conf.sample | 22 # During a first build the system will download many different source code tarballs
28 # The default is a downloads directory under TOPDIR which is the build directory.
33 # Where to place shared-state files
39 # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
44 # The default is a sstate-cache directory under TOPDIR.
46 #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
49 # Where to place the build output
68 DISTRO ?= "openbmc-phosphor"
73 # DISTRO ?= "poky-bleeding"
82 # - 'package_deb' for debian style deb files
[all …]
|