| /openbmc/linux/arch/microblaze/kernel/cpu/ |
| H A D | cpuinfo-pvr-full.c | 34 CI(ver_code, VERSION); in set_cpuinfo_pvr_full()
65 CI(pvr_user1, USER1); in set_cpuinfo_pvr_full()
66 CI(pvr_user2, USER2); in set_cpuinfo_pvr_full()
68 CI(mmu, USE_MMU); in set_cpuinfo_pvr_full()
70 CI(endian, ENDIAN); in set_cpuinfo_pvr_full()
72 CI(use_icache, USE_ICACHE); in set_cpuinfo_pvr_full()
93 CI(use_dopb, D_OPB); in set_cpuinfo_pvr_full()
94 CI(use_iopb, I_OPB); in set_cpuinfo_pvr_full()
95 CI(use_dlmb, D_LMB); in set_cpuinfo_pvr_full()
96 CI(use_ilmb, I_LMB); in set_cpuinfo_pvr_full()
[all …]
|
| /openbmc/qemu/.gitlab-ci.d/cirrus/ |
| H A D | README.rst | 1 Cirrus CI integration
4 GitLab CI shared runners only provide a docker environment running on Linux.
8 To work around this limitation, we take advantage of `Cirrus CI`_'s free
10 CI jobs from GitLab CI jobs so that Cirrus CI job output is integrated into
11 the main GitLab CI pipeline dashboard.
20 * enable the `Cirrus CI GitHub app`_ for your GitHub account;
25 * grab an API token from the `Cirrus CI settings`_ page;
29 Cirrus CI knows about your project by navigating to:
41 of it can impersonate you as far as Cirrus CI is concerned.
52 .. _Cirrus CI settings: https://cirrus-ci.com/settings/profile/
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | ca_high_level.rst | 3 The High level CI API
10 This document describes the high level CI API as in accordance to the
14 With the High Level CI approach any new card with almost any random
25 Why the need for another CI interface?
31 The CI interface is defined in the DVB API in ca.h as:
39 #define CA_CI 1 /* CI high level interface */
50 This CI interface follows the CI high level interface, which is not
89 APP: CI High level interface
90 APP: CA/CI Module Present
118 /* a message to/from a CI-CAM */
[all …]
|
| /openbmc/openbmc-build-scripts/jenkins/ |
| H A D | README.md | 8 | CI-MISC/ci-build-seed | jenkins/build-seed | |
9 | CI-MISC/ci-meta | jenkins/run-meta-ci | Deprecated |
10 | CI-MISC/ci-openbmc-build-scripts | jenkins/run-build-script-ci | |
11 | CI-MISC/ci-repository-ppc64le | run-unit-test-docker.sh | |
12 | CI-MISC/openbmc-node-cleaner | sstate-cache-management.sh | [1] |
13 | CI-MISC/openbmc-userid-validation | jenkins/userid-validation | |
14 | CI-MISC/run-ci-in-qemu | run-qemu-robot-test.sh | |
|
| /openbmc/qemu/docs/devel/ |
| H A D | ci-jobs.rst.inc | 3 Custom CI/CD variables
6 QEMU CI pipelines can be tuned by setting some CI environment variables.
8 Set variable globally in the user's CI namespace
11 Variables can be set globally in the user's CI namespace setting.
37 CI configurations. For example define an alias for triggering CI:
92 CI configuration file.
97 The job makes use of Cirrus CI infrastructure, requiring the
104 by default due to need to conserve limited CI resources. It is
105 available to be started manually by the contributor in the CI
113 CI pipeline.
[all …]
|
| H A D | ci.rst | 4 CI title
7 Most of QEMU's CI is run on GitLab's infrastructure although a number
8 of other CI services are used for specialised purposes. The most up to
10 `project wiki testing page <https://wiki.qemu.org/Testing/CI>`_.
|
| H A D | ci-runners.rst.inc | 4 Besides the jobs run under the various CI systems listed before, there
6 These use the same GitLab CI's service/framework already used for all
7 other GitLab based CI jobs, but rely on additional systems, not the
10 The architecture of GitLab's CI service allows different machines to
16 The GitLab CI jobs definition for the custom runners are located under::
21 currently deployed in the QEMU GitLab CI and their maintainers, please
74 * CI/CD, then
93 * CI/CD, then
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | ci.rst | 11 This document describes the usage of the high level CI API as
13 existing low level CI API.
17 For the Twinhan/Twinhan clones, the dst_ca module handles the CI
18 hardware handling. This module is loaded automatically if a CI
65 CI modules that are supported
68 The CI module support is largely dependent upon the firmware on the cards
69 Some cards do support almost all of the available CI modules. There is
70 nothing much that can be done in order to make additional CI modules
|
| H A D | dvb-usb-dvbsky-cardlist.rst | 31 * - TechnoTrend TT-connect CT2-4650 CI
33 * - TechnoTrend TT-connect CT2-4650 CI v1.1
35 * - TechnoTrend TT-connect S2-4650 CI
|
| H A D | cx23885-cardlist.rst | 86 - NetUP Dual DVB-S2 CI
138 - NetUP Dual DVB-T/C-CI RF
210 - Technotrend TT-budget CT2-4500 CI
|
| H A D | dvb-usb-pctv452e-cardlist.rst | 19 * - Technotrend TT Connect S2-3650-CI
|
| H A D | dvb-usb-az6007-cardlist.rst | 17 * - Technisat CableStar Combo HD CI
|
| /openbmc/qemu/ |
| H A D | .gitlab-ci.yml | 2 # This is the GitLab CI configuration file for the mainstream QEMU
10 # you need to set the location of your custom yml file at "custom CI/CD
11 # configuration path", on your GitLab CI namespace:
16 # QEMU CI jobs are based on templates. Some templates provide
|
| /openbmc/docs/designs/ |
| H A D | ci-authorization.md | 11 The OpenBMC project maintains a number of Jenkins CI jobs to ensure incoming
19 The project already has contributor authorization for CI. This proposal serves
27 team (or a general-developers sub-team), the automated CI processes are
30 project maintainer to trigger the automated CI processes.
46 An alternative authorization method for CI should:
49 authorized for CI.
86 Finally, any Jenkins CI jobs must be updated to test for membership of the
|
| /openbmc/docs/testing/ |
| H A D | local-ci-build.md | 1 # Local CI Build
3 These instructions pertain to running the upstream OpenBMC CI locally.
15 Each repository is built locally within the CI using the bootstrap.sh and
18 ## Download the CI Image
20 Start by making a place for your CI repositories to live, and clone the CI
33 clones and builds phosphor-hwmon directly. The upstream CI will try building
56 ## Run CI on local changed Repo
59 possible to run local CI as well by setting `NO_FORMAT_CODE=1` before running
72 ## Run CI for testing purposes only
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | cirrus.yml | 1 # Jobs that we delegate to Cirrus CI because they require an operating
5 # The Cirrus CI configuration is generated by replacing target-specific
7 # when the GitLab CI job is defined, others are taken from a shell
11 # special care, because we can't just override it at the GitLab CI job
19 # as there's often a 5-10 minute delay before Cirrus CI
94 # The following jobs run VM-based tests via KVM on a Linux-based Cirrus-CI job
|
| H A D | custom-runners.yml | 1 # The CI jobs defined here require GitLab runners installed and
3 # versions and architectures. This is in contrast to the other CI
|
| /openbmc/linux/drivers/media/pci/cx23885/ |
| H A D | Kconfig | 55 tristate "Altera FPGA based CI module"
59 An Altera FPGA CI module for NetUP Dual DVB-T/C RF CI card.
|
| /openbmc/bmcweb/ |
| H A D | CLIENTS.md | 22 Status: 100% passing. Integrated with CI to ensure no regressions.
28 Status: 100% of assertions passing. No CI integration.
33 Status: Passing for some machines with CI integration.
62 Status: Compatible. No CI integration.
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/ |
| H A D | CRP0.interface.yaml | 68 - name: CI
71 CI keyword.Processor Chip ID.
|
| /openbmc/webui-vue/docs/guide/coding-standards/ |
| H A D | readme.md | 34 CI tool runs after a push to Gerrit. There is a shell script named
36 script in your CI.
|
| /openbmc/openbmc-build-scripts/ |
| H A D | README.md | 3 Build script for CI jobs in Jenkins.
|
| /openbmc/qemu/tests/docker/dockerfiles/ |
| H A D | debian-hexagon-cross.docker | 5 # needs to be able to build QEMU itself in CI we include its
29 # Install QEMU build deps for use in CI
|
| /openbmc/linux/kernel/configs/ |
| H A D | debug.config | 1 # Help: Debugging for CI systems and finding regressions
3 # The config is based on running daily CI for enterprise Linux distros to
|
| /openbmc/linux/Documentation/translations/zh_CN/maintainer/ |
| H A D | maintainer-entry-profile.rst | 30 - 是否有任何机器人或CI基础设施监视列表，或子系统是否使用自动测试反馈以便把
|