| /openbmc/qemu/docs/devel/ |
| H A D | codebase.rst | 5 This section presents the various parts of QEMU and how the codebase is
12 ----------
15 `MAINTAINERS <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`_
18 Some of the main QEMU subsystems are:
20 - `Accelerators<Accelerators>`
21 - Block devices and `disk images<disk images>` support
22 - `CI<ci>` and `Tests<testing>`
23 - `Devices<device-emulation>` & Board models
24 - `Documentation <documentation-root>`
25 - `GDB support<GDB usage>`
[all …]
|
| H A D | code-of-conduct.rst | 6 The QEMU community is made up of a mixture of professionals and
11 * Be welcoming. We are committed to making participation in this project
12 a harassment-free experience for everyone, regardless of level of
18 social and technical, happen all the time and the QEMU community is no
21 QEMU community should be respectful when dealing with other contributors as
22 well as with people outside the QEMU community and with users of QEMU.
43 This code of conduct applies to all spaces managed by the QEMU project.
45 events, and any other forums created by the project team which the
48 member of the project or its community.
50 By adopting this code of conduct, project maintainers commit themselves
[all …]
|
| H A D | maintainers.rst | 6 Maintainers are a critical part of the project's contributor ecosystem.
8 working in their spare time to employees who work on the project as
11 - reviewing patches and suggesting changes
12 - collecting patches and preparing pull requests
13 - tending to the long term health of their area
14 - participating in other project activities
18 to project's :ref:`code_of_conduct` and should also be exemplars of
22 --------------------
25 <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`__
34 .. list-table:: Meaning of support status in MAINTAINERS
[all …]
|
| H A D | code-provenance.rst | 1 .. _code-provenance:
9 The QEMU community **mandates** all contributors to certify provenance of
10 patch submissions they make to the project. To put it another way,
12 the project.
17 Signed-off-by: YOUR NAME <YOUR@EMAIL>
27 By making a contribution to this project, I certify that:
45 (d) I understand and agree that this project and the contribution
47 personal information I submit with it, including my sign-off) is
49 this project or the open source license(s) involved.
51 The name used with "Signed-off-by" does not need to be your legal name, nor
[all …]
|
| /openbmc/qemu/ |
| H A D | .gitmodules | 3 url = https://gitlab.com/qemu-project/seabios.git/
6 url = https://gitlab.com/qemu-project/SLOF.git
9 url = https://gitlab.com/qemu-project/ipxe.git
12 url = https://gitlab.com/qemu-project/openbios.git
13 [submodule "roms/qemu-palcode"]
14 path = roms/qemu-palcode
15 url = https://gitlab.com/qemu-project/qemu-palcode.git
16 [submodule "roms/u-boot"]
17 path = roms/u-boot
18 url = https://gitlab.com/qemu-project-mirrors/u-boot.git
[all …]
|
| H A D | .gitlab-ci.yml | 2 # This is the GitLab CI configuration file for the mainstream QEMU
3 # project: https://gitlab.com/qemu-project/qemu/-/pipelines
9 # To use a different set of jobs than the mainstream QEMU project,
12 # https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path
14 # ----------------------------------------------------------------------
16 # QEMU CI jobs are based on templates. Some templates provide
17 # user-configurable options, modifiable via configuration variables.
19 # See https://qemu-project.gitlab.io/qemu/devel/ci.html#custom-ci-cd-variables
24 - local: '/.gitlab-ci.d/qemu-project.yml'
|
| H A D | README.rst | 2 QEMU README
5 QEMU is a generic and open source machine & userspace emulator and
8 QEMU is capable of emulating a complete machine in software without any
10 it achieves very good performance. QEMU can also integrate with the Xen
12 hypervisor to manage the CPU. With hypervisor support, QEMU can achieve
13 near native performance for CPUs. When QEMU emulates CPUs directly it is
17 QEMU is also capable of providing userspace API virtualization for Linux
23 QEMU aims to fit into a variety of use cases. It can be invoked directly
28 open source applications such as oVirt, OpenStack and virt-manager.
30 QEMU as a whole is released under the GNU General Public License,
[all …]
|
| /openbmc/qemu/.github/workflows/ |
| H A D | lockdown.yml | 1 # Configuration for Repo Lockdown - https://github.com/dessant/repo-lockdown
10 pull-requests: write
14 runs-on: ubuntu-latest
16 - uses: dessant/repo-lockdown@v2
18 pr-comment: |
19 Thank you for your interest in the QEMU project.
21 This repository is a read-only mirror of the project's repostories hosted
22 on https://gitlab.com/qemu-project/qemu.git.
23 The project does not process merge requests filed on GitHub.
25 QEMU welcomes contributions of code (either fixing bugs or adding new
[all …]
|
| /openbmc/qemu/python/ |
| H A D | PACKAGE.rst | 1 QEMU Python Tooling
4 This package provides QEMU tooling used by the QEMU project to build,
5 configure, and test QEMU. It is not a fully-fledged SDK and it is subject
9 -----
11 The ``qemu.qmp`` subpackage provides a library for communicating with
12 QMP servers. The ``qemu.machine`` subpackage offers rudimentary
13 facilities for launching and managing QEMU processes. Refer to each
15 (``>>> help(qemu.qmp)``, ``>>> help(qemu.machine)``)
19 ------------
22 the QEMU source tree. Contributions are welcome and follow the `QEMU
[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
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
23 :ref:`dev-manual/start:setting up to use cross platforms (crops)`
25 in the Yocto Project Development Tasks Manual for more
28 - You may use version 2 of Windows Subsystem For Linux (WSL 2) to set
30 See the :ref:`dev-manual/start:setting up to use windows subsystem for
[all …]
|
| /openbmc/qemu/docs/ |
| H A D | conf.py | 1 # -*- coding: utf-8 -*-
3 # QEMU documentation build configuration file, created by
4 # sphinx-quickstart on Thu Jan 31 16:40:14 2019.
8 # for each of QEMU's manuals: in this case sphinx-build is run multiple
11 # the manuals into a single document: in this case sphinx-build is
12 # run once, on the top-level docs directory.
14 # QEMU's makefiles take option (1), which allows us to install
16 # to ship the 'devel' manual to end-users).
17 # Third-party sites such as readthedocs.org will take option (2).
34 # The per-manual conf.py will set qemu_docdir for a single-manual build;
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | qemu.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Using the Quick EMUlator (QEMU)
7 The Yocto Project uses an implementation of the Quick EMUlator (QEMU)
8 Open Source project as part of the Yocto Project development "tool set".
10 EMUlator (QEMU) and other QEMU information helpful for development
16 Within the context of the Yocto Project, QEMU is an emulator and
18 built using the Yocto Project as just another task on your build system.
19 QEMU is useful for running and testing images and applications on
20 supported Yocto Project architectures without having actual hardware.
21 Among other things, the Yocto Project uses QEMU to run automated Quality
[all …]
|
| 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
16 This section describes the Yocto Project support for generating and
20 GObject Introspection Repository (GIR) files go to ``-dev`` packages,
28 Generating this data in a cross-compilation environment is difficult
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 …]
|
| /openbmc/qemu/.gitlab-ci.d/custom-runners/ |
| H A D | ubuntu-22.04-s390x.yml | 1 # All ubuntu-22.04 jobs should run successfully in an environment
2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task
3 # "Install basic packages to build QEMU on Ubuntu 22.04"
5 ubuntu-22.04-s390x-all-linux:
10 - ubuntu_22.04
11 - s390x
13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
14 - if: "$S390X_RUNNER_AVAILABLE"
16 - mkdir build
17 - cd build
[all …]
|
| H A D | ubuntu-22.04-aarch64.yml | 1 # All ubuntu-22.04 jobs should run successfully in an environment
2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task
3 # "Install basic packages to build QEMU on Ubuntu 22.04"
5 ubuntu-22.04-aarch64-all-linux-static:
10 - ubuntu_22.04
11 - aarch64
13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'
14 - if: "$AARCH64_RUNNER_AVAILABLE"
16 - mkdir build
17 - cd build
[all …]
|
| /openbmc/qemu/pc-bios/ |
| H A D | README | 1 - SeaBIOS (bios.bin) is the successor of pc bios.
4 - The VGA BIOS and the Cirrus VGA BIOS come from the LGPL VGA bios
5 project (http://www.nongnu.org/vgabios/).
7 - OpenBIOS (http://www.openbios.org/) is a free (GPL v2) portable
9 1275-1994 (referred to as Open Firmware) compliant firmware.
11 Sparc32 (including QEMU,tcx.bin and QEMU,cgthree.bin) and Sparc64 are built
14 - SLOF (Slimline Open Firmware) is a free IEEE 1275 Open Firmware
16 https://gitlab.com/slof/slof, and the image currently in qemu is
17 built from git tag qemu-slof-20241106.
19 - VOF (Virtual Open Firmware) is a minimalistic firmware to work with
[all …]
|
| /openbmc/qemu/include/qemu/ |
| H A D | help-texts.h | 4 /* Copyright string for -version arguments, About dialogs, etc */
5 #define QEMU_COPYRIGHT "Copyright (c) 2003-2025 " \
6 "Fabrice Bellard and the QEMU Project developers"
8 /* Bug reporting information for --help arguments, About dialogs, etc */
10 "See <https://qemu.org/contribute/report-a-bug> for how to report bugs.\n" \
11 "More information on the QEMU project at <https://qemu.org>."
|
| /openbmc/qemu/docs/about/ |
| H A D | build-platforms.rst | 1 .. _Supported-build-platforms:
6 QEMU aims to support building and executing on multiple host OS
9 minimum required versions of 3rd party software QEMU depends on. The
11 the project when patches are submitted for review, and tested before and
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 :ref:`setup-build-env` page.
36 ----------------------------
[all …]
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | intro.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
10 Welcome to the Yocto Project Application Development and the Extensible
12 explains how to use both the Yocto Project extensible and standard
17 - *Cross-Development Toolchain*: This toolchain contains a compiler,
20 - *Libraries, Headers, and Symbols*: The libraries, headers, and
24 - *Environment Setup Script*: This ``*.sh`` file, once sourced, sets up the
25 cross-development environment by defining variables and preparing for
35 self-contained. The binaries are linked against their own copy of
42 Another feature of the SDKs is that only one set of cross-compiler
50 sysroot because those binaries are target-specific.
[all …]
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | qemu-project.yml | 1 # This file contains the set of jobs run by the QEMU project:
2 # https://gitlab.com/qemu-project/qemu/-/pipelines
9 - $RUNNER_TAG
12 - local: '/.gitlab-ci.d/base.yml'
13 - local: '/.gitlab-ci.d/stages.yml'
14 - local: '/.gitlab-ci.d/opensbi.yml'
15 - local: '/.gitlab-ci.d/containers.yml'
16 - local: '/.gitlab-ci.d/crossbuilds.yml'
17 - local: '/.gitlab-ci.d/buildtest.yml'
18 - local: '/.gitlab-ci.d/static_checks.yml'
[all …]
|
| H A D | opensbi.yml | 1 # All jobs needing docker-opensbi must use the same rules it uses.
5 - if: '$QEMU_CI != "1" && $QEMU_CI != "2" && $CI_PROJECT_NAMESPACE != "qemu-project"'
10 - if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project"'
12 - .gitlab-ci.d/opensbi.yml
13 - .gitlab-ci.d/opensbi/Dockerfile
14 - roms/opensbi/*
19 …- if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project" && $CI_COMMIT_REF_NAME =~ /^open…
24 …- if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project" && $CI_COMMIT_MESSAGE =~ /opensb…
28 - if: '$CI_PROJECT_NAMESPACE == $QEMU_CI_UPSTREAM && $CI_PIPELINE_SOURCE == "schedule"'
32 - changes:
[all …]
|
| /openbmc/qemu/tests/functional/ |
| H A D | test_ppc64_reverse_debug.py | 3 # SPDX-License-Identifier: GPL-2.0-or-later
13 # later. See the COPYING file in the top-level directory.
24 @skipFlakyTest("https://gitlab.com/qemu-project/qemu/-/issues/1992")
33 @skipFlakyTest("https://gitlab.com/qemu-project/qemu/-/issues/1992")
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | can.rst | 22 open-source/design/hardware solution. The core designer
23 of the project is Ondrej Ille, the financial support has been
26 The project has been initially started in frame of RTEMS GSoC 2013
31 to work on CAN hardware emulation on QEMU.
34 ----------------------------------------------------------
35 When QEMU with CAN PCI support is compiled then one of the next
38 (1) CAN bus Kvaser PCI CAN-S (single SJA1000 channel) board. QEMU startup options::
40 -object can-bus,id=canbus0
41 -device kvaser_pci,canbus=canbus0
43 Add "can-host-socketcan" object to connect device to host system CAN bus::
[all …]
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | release-process.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Yocto Project Releases and the Stable Release Process
7 The Yocto Project release process is predictable and consists of both
15 The Yocto Project delivers major releases (e.g. &DISTRO;) using a six
18 also shown. See the ":ref:`ref-manual/release-process:major release codenames`"
21 - 4.1 ("Langdale")
22 - 4.0 ("Kirkstone")
23 - 3.4 ("Honister")
30 The Yocto project delivers minor (point) releases on an unscheduled
35 - 4.1.3
[all …]
|
| H A D | resources.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 .. _resources-intro:
12 The Yocto Project team is happy for people to experiment with the Yocto
13 Project. There is a number of places where you can find help if you run into
15 and participating in the Yocto Project.
17 .. _resources-contributions:
22 The Yocto Project gladly accepts contributions. You can submit changes
23 to the project either by creating and sending pull requests, or by
26 code, see the :doc:`../contributor-guide/index`.
28 .. _resources-bugtracker:
[all …]
|