| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | new-machine.rst | 3 Adding a New Machine
6 Adding a new machine to the Yocto Project is a straightforward process.
12 Although well within the capabilities of the Yocto Project, adding a
22 Adding the Machine Configuration File
27 provides details about the device you are adding.
55 Adding a Kernel for the Machine
76 of adding a suitable ``defconfig`` file. The file needs to be added into
79 the :term:`SRC_URI` and adding the machine to the expression in
88 Adding a Formfactor Configuration File
|
| /openbmc/linux/tools/testing/selftests/net/forwarding/ |
| H A D | tc_flower_l2_miss.sh | 88 # Before adding FDB entry.
92 check_err $? "Unknown unicast filter was not hit before adding FDB entry"
95 check_err $? "Known unicast filter was hit before adding FDB entry"
97 # Adding FDB entry.
103 check_err $? "Unknown unicast filter was hit after adding FDB entry"
106 check_err $? "Known unicast filter was not hit after adding FDB entry"
145 # Before adding MDB entry.
149 check_err $? "Unregistered multicast filter was not hit before adding MDB entry"
152 check_err $? "Registered multicast filter was hit before adding MDB entry"
154 # Adding MDB entry.
[all …]
|
| H A D | bridge_locked_port.sh | 105 check_fail $? "Ping worked after locking port, but before adding FDB entry"
110 check_err $? "Ping did not work after locking port and adding FDB entry"
135 check_fail $? "Ping through vlan worked after locking port, but before adding FDB entry"
140 check_err $? "Ping through vlan did not work after locking port and adding FDB entry"
164 check_fail $? "Ping6 worked after locking port, but before adding FDB entry"
168 check_err $? "Ping6 did not work after locking port and adding FDB entry"
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 082 | 73 # Adding the help option to a command without other -o options
77 # Adding the help option to the same -o option
83 # Adding the help option to a separate -o option
132 # Adding the help option to a command without other -o options
136 # Adding the help option to the same -o option
142 # Adding the help option to a separate -o option
165 # Adding the help option to a command without other -o options
191 # Adding the help option to a command without other -o options
195 # Adding the help option to the same -o option
201 # Adding the help option to a separate -o option
|
| H A D | 293.out | 9 == adding a password to slot 4 ==
10 == adding a password to slot 1 ==
11 == adding a password to slot 3 ==
12 == adding a password to slot 2 ==
33 == adding secret 0 ==
35 == adding secret 3 (last slot) ==
|
| H A D | 246 | 49 log('\n--- Adding bitmaps Small, Medium, Large, and Transient ---\n')
68 log('--- Adding new bitmap, growing image, and adding 2nd new bitmap ---')
85 log('--- Adding "NewB" bitmap, removing "New" bitmap ---')
95 log('--- Adding "NewC" bitmap, removing "NewTwo" bitmap ---')
|
| H A D | 246.out | 6 --- Adding bitmaps Small, Medium, Large, and Transient ---
88 --- Adding new bitmap, growing image, and adding 2nd new bitmap ---
191 --- Adding "NewB" bitmap, removing "New" bitmap ---
200 --- Adding "NewC" bitmap, removing "NewTwo" bitmap ---
|
| H A D | 202.out | 2 Adding IOThread...
4 Adding blockdevs...
|
| H A D | 293 | 77 echo "== adding a password to slot 4 =="
79 echo "== adding a password to slot 1 =="
81 echo "== adding a password to slot 3 =="
84 echo "== adding a password to slot 2 =="
118 echo "== adding secret 0 =="
122 echo "== adding secret 3 (last slot) =="
|
| /openbmc/linux/tools/testing/selftests/tc-testing/creating-plugins/ |
| H A D | AddingPlugins.txt | 1 tdc - Adding plugins for tdc
5 ADDING PLUGINS
14 - adding commands to be run before and/or after the test suite
15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing-standard.rst | 9 Adding Individual Packages to the Standard SDK
17 variables control the set of packages adding to the SDK.
25 Adding API Documentation to the Standard SDK
29 provided by recipes with the standard SDK by adding "api-documentation"
|
| /openbmc/linux/drivers/net/ethernet/mellanox/mlxsw/ |
| H A D | spectrum_switchdev.c | 1640 static enum mlxsw_reg_sfd_op mlxsw_sp_sfd_op(bool adding) in mlxsw_sp_sfd_op() argument
1642 return adding ? MLXSW_REG_SFD_OP_WRITE_EDIT : in mlxsw_sp_sfd_op()
1648 const char *mac, u16 fid, __be32 addr, bool adding) in mlxsw_sp_port_fdb_tun_uc_op4() argument
1660 mlxsw_reg_sfd_pack(sfd_pl, mlxsw_sp_sfd_op(adding), 0); in mlxsw_sp_port_fdb_tun_uc_op4()
1679 u32 kvdl_index, bool adding) in mlxsw_sp_port_fdb_tun_uc_op6_sfd_write() argument
1689 mlxsw_reg_sfd_pack(sfd_pl, mlxsw_sp_sfd_op(adding), 0); in mlxsw_sp_port_fdb_tun_uc_op6_sfd_write()
1749 u16 fid, const struct in6_addr *addr, bool adding) in mlxsw_sp_port_fdb_tun_uc_op6() argument
1751 if (adding) in mlxsw_sp_port_fdb_tun_uc_op6()
1763 bool adding, bool dynamic) in mlxsw_sp_port_fdb_tunnel_uc_op() argument
1768 addr->addr4, adding); in mlxsw_sp_port_fdb_tunnel_uc_op()
[all …]
|
| /openbmc/openbmc/poky/meta/classes-recipe/ |
| H A D | gtk-icon-cache.bbclass | 68 bb.note("adding hicolor-icon-theme dependency to %s" % pkg)
73 bb.note("adding gdk-pixbuf dependency to %s" % pkg)
77 bb.note("adding %s dependency to %s" % (d.getVar('GTKPN'), pkg))
81 bb.note("adding gtk-icon-cache postinst and postrm scripts to %s" % pkg)
|
| /openbmc/linux/net/batman-adv/ |
| H A D | main.h | 312 * * when adding nothing - it is neither a predecessor nor a successor
313 * * before adding more than 127 to the starting value - it is a predecessor,
314 * * when adding 128 - it is neither a predecessor nor a successor,
315 * * after adding more than 127 to the starting value - it is a successor
338 * * when adding nothing - it is neither a predecessor nor a successor
339 * * before adding more than 127 to the starting value - it is a predecessor,
340 * * when adding 128 - it is neither a predecessor nor a successor,
341 * * after adding more than 127 to the starting value - it is a successor
|
| /openbmc/openpower-proc-control/extensions/phal/ |
| H A D | phal_error.cpp | 323 // Adding collected phal logs into PEL additional data in processNonFunctionalBootProc()
362 // Adding hardware procedures return code details in processClockInfoErrorHelper()
368 // Adding hardware procedures required ffdc data for debug in processClockInfoErrorHelper()
390 // Adding CDG (Only deconfigure) targets details in processClockInfoErrorHelper()
405 // Adding collected phal logs into PEL additional data in processClockInfoErrorHelper()
495 * Not adding callouts from FFDC as the hardware errors in the poweroff path
517 // Adding hardware procedures return code details in processPoweroffError()
534 // Adding collected phal logs into PEL additional data in processPoweroffError()
578 // Adding hardware procedures return code details in processBootErrorHelper()
585 // Adding hardware procedures required ffdc data for debug in processBootErrorHelper()
[all …]
|
| /openbmc/openbmc/meta-security/meta-integrity/ |
| H A D | README.md | 54 1. Adding the integrity layer to your build
59 1. Adding the integrity layer to your build
66 yocto build tree, you can add it to the build system by adding the
88 Adding the layer only enables IMA (see below regarding EVM) during
140 supports adding tha CA's public key to the kernel's system keyring by
219 issues. Enable it by adding a kernel configuration fragment and
230 Adding auditd is not strictly necessary but helps to capture a
|
| /openbmc/openbmc/meta-google/ |
| H A D | README | 26 I. Adding the filesystems layer to your build
31 I. Adding the meta-google layer to your build
38 yocto build tree, you can add it to the build system by adding the
|
| /openbmc/linux/Documentation/driver-api/fpga/ |
| H A D | intro.rst | 19 * Generally, when adding code, think of the future. Plan for reuse.
26 If you are adding a new FPGA or a new method of programming an FPGA,
46 If you are adding a new interface to the FPGA framework, add it on top
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | memory-hotplug.rst | 89 When adding/removing memory that uses memory block devices (i.e. ordinary RAM),
99 device_hotplug_lock when adding memory and user space tries to online that
114 When adding/removing/onlining/offlining memory or adding/removing
|
| /openbmc/linux/Documentation/arch/sh/ |
| H A D | new-machine.rst | 4 Adding a new board to LinuxSH
89 2. Adding a New Board
92 The first thing to determine is whether the board you are adding will be
97 board in arch/sh/boards/ and adding rules to hook your board in with the
114 explain this, we use some examples for adding an imaginary board. For
167 Adding a new machine is relatively trivial (using vapor as an example):
233 This is done by adding an entry to the end of the arch/sh/tools/mach-types
|
| /openbmc/u-boot/include/ |
| H A D | pch.h | 72 * This is a catch-all operation intended to avoid adding lots of
75 * use this method instead of adding new methods.
129 * This is a catch-all operation intended to avoid adding lots of
132 * use this method instead of adding new methods.
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | fapi_data_process.cpp | 260 // Adding hardware procedures return code details in processClockInfoErrorHelper()
264 // Adding hardware procedures required ffdc data for debug in processClockInfoErrorHelper()
285 // Adding CDG (Only deconfigure) targets details in processClockInfoErrorHelper()
313 // Adding hardware procedures return code details in convertFAPItoPELformat()
317 // Adding hardware procedures required ffdc data for debug in convertFAPItoPELformat()
328 // Adding hardware callout details in convertFAPItoPELformat()
378 // Adding CDG (callout, deconfigure and guard) targets details in convertFAPItoPELformat()
443 // Adding procedure callout in convertFAPItoPELformat()
|
| /openbmc/linux/tools/testing/selftests/drivers/net/dsa/ |
| H A D | bridge_locked_port.sh | 105 check_fail $? "Ping worked after locking port, but before adding FDB entry"
110 check_err $? "Ping did not work after locking port and adding FDB entry"
135 check_fail $? "Ping through vlan worked after locking port, but before adding FDB entry"
140 check_err $? "Ping through vlan did not work after locking port and adding FDB entry"
164 check_fail $? "Ping6 worked after locking port, but before adding FDB entry"
168 check_err $? "Ping6 did not work after locking port and adding FDB entry"
|
| /openbmc/webui-vue/docs/customization/ |
| H A D | theme.md | 47 `/node_modules/bootstrap/scss/variables.scss` helper file. Adding a variable
147 Adding, removing, or updating the color variables and map is how the application
178 the colors except gray. The Bootstrap documentation indicates that adding color
203 ## Adding a logo
205 The updated page header can include a small logo. The guidelines for adding a
|
| /openbmc/linux/drivers/nvme/host/ |
| H A D | fabrics.h | 72 * on adding a NVMe controller.
82 * subsystem which is adding a controller.
84 * subsystem which is adding a controller.
141 * when adding a new NVMe controller.
143 * when adding a new NVMe controller.
|