| /openbmc/openbmc/poky/scripts/lib/checklayer/cases/ |
| H A D | bsp.py | 19 self.assertTrue(self.tc.layer['conf']['machines'],
20 "Layer is BSP but doesn't defines machines.")
38 This test iterates over all machines. It would be nicer to instantiate
43 if not self.td['machines']:
44 self.skipTest('No machines set with --machines.')
46 for machine in self.td['machines']:
53 msg.insert(0, 'The following machines broke a world build:')
61 in exactly the same way. Otherwise it is not possible to use both machines
64 This criteria can only be tested by testing different machines in combination,
66 choice of machines:
[all …]
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | sstate-diff-machines.sh | 7 # Used to compare sstate checksums between MACHINES.
31 machines=
39 Welcome to utility to compare sstate checksums between different MACHINEs.
50 --machines=<machines>
51 …List of MACHINEs separated by space, will use the environment variable MACHINES if it is not speci…
59 Show the differences between MACHINEs. It assumes:
60 * First 2 MACHINEs in --machines parameter have the same TUNE_PKGARCH
62 * Next MACHINEs are ignored
79 --machines=*)
80 machines=`echo $1 | sed -e 's#^--machines="*\([^"]*\)"*#\1#'`
[all …]
|
| /openbmc/openbmc/meta-arm/ci/ |
| H A D | listmachines.py | 8 List all of the machines available under the listed sub-layers of meta-arm.
11 machines = set()
19 machines |= set(p.stem for p in (metaarm / layer / "conf" / "machine").glob("*.conf"))
20 return machines
24 machines = list_machines(sys.argv[1:]) variable
25 print(" ".join(sorted(machines)))
|
| H A D | check-machine-coverage | 16 machines = list_machines(layers) variable
22 missing = machines - kas
23 print(f"The following machines are missing: {', '.join(sorted(missing))}.")
25 covered = len(machines) - len(missing)
26 total = len(machines)
|
| /openbmc/google-misc/subprojects/ncsid/doc/ |
| H A D | ncsid_internals.md | 15 - **EC**. This is the code borrowed from EC. The three state machines are pretty
29 ## EC State Machines
31 NC-SId reuses the state machines from EC. They are treated like black boxes.
49 all state machines restart, which means that NC-SI in the NIC is also reset and
55 not a part of EC state machines' state:
57 - State Parameters. These structures are allocated outside of EC State Machines,
58 but their content is fully managed by EC State Machines.
79 This component coordinates the interaction between EC State Machines and is also
101 To allow some fairly sophisticated unit-tests, EC State Machines as well as
106 server, replying to NC-SI requests coming from NC-SI State Machines.
|
| /openbmc/openbmc/meta-raspberrypi/docs/ |
| H A D | layer-contents.md | 3 ## Supported Machines
18 Note: The raspberrypi3 machines include support for Raspberry Pi 3B+.
20 ## Multi-board Machines
22 This layer generally provides support for machines that are targetting a single
28 machines that are tagetting a wider support of Raspberry Pi boards.
56 bbappends to that recipe. All machines define
|
| /openbmc/qemu/tests/qtest/ |
| H A D | prom-env-test.c | 2 * Test Open-Firmware-based machines.
12 * This test is used to check that some Open Firmware based machines (i.e.
68 static void add_tests(const char *machines[]) in add_tests() argument
73 for (i = 0; machines[i] != NULL; i++) { in add_tests()
74 if (qtest_has_machine(machines[i])) { in add_tests()
75 name = g_strdup_printf("prom-env/%s", machines[i]); in add_tests()
76 qtest_add_data_func(name, machines[i], test_machine); in add_tests()
|
| H A D | libqtest.c | 1614 static void qtest_free_machine_list(struct MachInfo *machines) in qtest_free_machine_list() argument
1616 if (machines) { in qtest_free_machine_list()
1617 for (int i = 0; machines[i].name != NULL; i++) { in qtest_free_machine_list()
1618 g_free(machines[i].name); in qtest_free_machine_list()
1619 g_free(machines[i].alias); in qtest_free_machine_list()
1622 g_free(machines); in qtest_free_machine_list()
1632 static struct MachInfo *machines; in qtest_get_machines() local
1647 qtest_free_machine_list(machines); in qtest_get_machines()
1648 machines = NULL; in qtest_get_machines()
1651 if (machines) { in qtest_get_machines()
[all …]
|
| /openbmc/openbmc/meta-phosphor/scripts/ |
| H A D | generate-machine-list | 8 cat > meta-phosphor/docs/supported-machines.md << EOF
9 # Supported machines
23 ./setup machines >> meta-phosphor/docs/supported-machines.md
|
| /openbmc/openbmc/meta-arm/scripts/ |
| H A D | layer-overview.py | 6 Output includes sublayers, machines, recipes.
29 machines = sorted(p for p in layer.glob("conf/machine/*.conf"))
30 if machines:
31 print(" Machines")
32 for m in machines:
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/ |
| H A D | typeaheads.py | 63 """ Typeahead for all the machines available in the current project's
67 machines = prj.get_available_machines()
68 machines = machines.order_by("name")
70 primary_results = machines.filter(name__istartswith=search_term)
71 secondary_results = machines.filter(
73 tertiary_results = machines.filter(
|
| /openbmc/openbmc/poky/meta/lib/bblayers/ |
| H A D | machines.py | 19 """List the machines available in the currently configured layers."""
35 parser_show_machines = self.add_command(sp, "show-machines", self.do_show_machines)
37 …parser_show_machines.add_argument('-l', '--layer', help='Limit to machines in the specified layer')
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/orm/management/commands/ |
| H A D | lsupdates.py | 240 # update machines
243 total = len(index.machines)
244 for i, id in enumerate(index.machines):
246 name=index.machines[id].name,
248 pk=li_layer_branch_id_to_toaster_lv_id[index.machines[id].layerbranch_id]))
249 mo.up_date = index.machines[id].updated
250 mo.name = index.machines[id].name
251 mo.description = index.machines[id].description
253 self.mini_progress("machines", i, total)
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | stm32.rst | 9 The STM32F1 series is based on ARM Cortex-M3 core. The following machines are
14 The STM32F2 series is based on ARM Cortex-M3 core. The following machines are
21 The following machines are based on this ARM Cortex-M4F chip :
65 The STM32 machines can be started using the ``-kernel`` option to load a
|
| H A D | nuvoton.rst | 15 segment. The following machines are based on this chip :
20 Hyperscale applications. The following machines are based on this chip :
32 The following machines are based on this chip :
96 The Nuvoton machines can boot from an OpenBMC firmware image, or directly into
|
| H A D | aspeed.rst | 4 The QEMU Aspeed machines model BMCs of various OpenPOWER systems and
13 AST2400 SoC based machines :
20 AST2500 SoC based machines :
31 AST2600 SoC based machines :
90 The Aspeed machines can be started using the ``-kernel`` and ``-dtb`` options
170 The machine options specific to Aspeed machines to boot from an eMMC
175 Only the ``ast2600-evb`` and ``rainier-emmc`` machines have support to
232 Other machine options specific to Aspeed machines are :
235 machines use the ``UART5`` device for a boot console, which is
280 The QEMU Aspeed machines model BMCs of Aspeed evaluation boards.
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/ |
| H A D | README.md | 4 [Arm SystemReady][] validation on the supported machines.
11 This layer provides support for the following on supported machines:
83 To build the firmware for Arm SystemReady on the supported machines (take the
89 To run the Arm SystemReady ACS tests on the supported machines (take running
94 To run the Linux distributions installation on the supported machines (take
107 SystemReady IR implementation can be reused on other machines. Furthermore, the
112 To reuse the supported Arm SystemReady IR on other machines, you will need to:
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/multiconfig/ |
| H A D | multiconfig-image-packager_0.1.bb | 15 install -d ${D}/var/lib/machines/${MCNAME}
16 …_IMAGE}/${IMAGE_LINK_NAME_CORE_IMAGE_MINIMAL}.${MCIMGTYPE} ${D}/var/lib/machines/${MCNAME}/${MC_DE…
17 install ${MC_DEPLOY_DIR_IMAGE}/bzImage ${D}/var/lib/machines/${MCNAME}
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/ipmi/ |
| H A D | phosphor-ipmi-inventory-sel-native.bb | 1 SUMMARY = "Inventory to Sensor config for non-mrw machines"
17 # mapping, for non-mrw machines.
|
| /openbmc/qemu/docs/system/ |
| H A D | targets.rst | 6 QEMU is a generic emulator and it emulates many machines. Most of the
7 options are similar for all machines. Specific information about the
|
| H A D | target-arm.rst | 14 nearly fifty different machines. The reason we support so many is that
18 then built into machines which can vary still further even if they use
23 implement so many different machines.
58 real hardware and is designed for use in virtual machines. You'll
|
| /openbmc/qemu/monitor/ |
| H A D | qemu-config-qmp.c | 126 GSList *machines, *curr_mach; in query_all_machine_properties() local
131 machines = object_class_get_list(TYPE_MACHINE, false); in query_all_machine_properties()
132 assert(machines); in query_all_machine_properties()
135 for (curr_mach = machines; curr_mach; curr_mach = curr_mach->next) { in query_all_machine_properties()
161 g_slist_free(machines); in query_all_machine_properties()
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/connman/ |
| H A D | connman-conf.bb | 1 SUMMARY = "Connman config to ignore wired interface on qemu machines"
3 network interface inside qemu machines."
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | qgraph.rst | 12 therefore a generic sdhci test should test all machines and drivers that
21 The aim of qgraph is to create a graph of drivers, machines and tests such that
36 The graph is composed by nodes that represent machines, drivers, tests
63 - QNODE_DRIVER: driver names must be unique, and machines and nodes
70 An edge relation between two nodes (drivers or machines) ``X`` and ``Y`` can be:
84 and machines (note that only machines and "consumed" nodes are mapped
86 - The framework walks the graph starting from the available machines and
93 Depending on the QEMU binary used, only some drivers/machines will be
104 - ``in node`` : created from the node name. For example, machines will
218 (in this example we focus on the ``arm-raspi2b``) machines.
[all …]
|
| H A D | ci-runners.rst.inc | 10 The architecture of GitLab's CI service allows different machines to
20 Custom runners entail custom machines. To see a list of the machines
45 playbook will set up machines with the environment needed to perform
|