| /openbmc/openbmc/poky/meta/recipes-devtools/expect/expect/ |
| H A D | 0001-Replace-tclsh-with-tclsh8-in-the-scripts-used-in-the.patch | 63 # The next line is executed by /bin/sh, but not tcl \
76 # The next line is executed by /bin/sh, but not tcl \
89 # The next line is executed by /bin/sh, but not tcl \
102 # The next line is executed by /bin/sh, but not tcl \
115 # The next line is executed by /bin/sh, but not tcl \
128 # The next line is executed by /bin/sh, but not tcl \
141 # The next line is executed by /bin/sh, but not tcl \
154 # The next line is executed by /bin/sh, but not tcl \
167 # The next line is executed by /bin/sh, but not tcl \
180 # The next line is executed by /bin/sh, but not tcl \
[all …]
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | environmental_message_registry.hpp | 177 …"Indicates that a flow rate reading is no longer below the lower critical threshold but is still o…
178 …"Flow rate '%1' reading of %2 L/min is now above the %3 lower critical threshold but remains outsi…
191 …"Indicates that a flow rate reading is no longer below the lower fatal threshold but is still outs…
192 …"Flow rate '%1' reading of %2 L/min is now above the %3 lower fatal threshold but remains outside …
289 …"Indicates that a flow rate reading is no longer above the upper critical threshold but is still o…
290 …"Flow rate '%1' reading of %2 L/min is now below the %3 upper critical threshold but remains outsi…
303 …"Indicates that a flow rate reading is no longer above the upper fatal threshold but is still outs…
304 …"Flow rate '%1' reading of %2 L/min is now below the %3 upper fatal threshold but remains outside …
343 …"Indicates that a flow rate reading no longer exceeds an internal critical level but still exceeds…
356 …"Indicates that a flow rate reading is no longer exceeds an internal fatal level but is still exce…
[all …]
|
| H A D | power_message_registry.hpp | 105 …"Indicates that a current reading is no longer below the lower critical threshold but is still out…
106 …"Current '%1' reading of %2 amperes is now above the %3 lower critical threshold but remains outsi…
119 …"Indicates that a current reading is no longer below the lower fatal threshold but is still outsid…
120 …"Current '%1' reading of %2 amperes is now above the %3 lower fatal threshold but remains outside …
217 …"Indicates that a current reading is no longer above the upper critical threshold but is still out…
218 …"Current '%1' reading of %2 amperes is now below the %3 upper critical threshold but remains outsi…
231 …"Indicates that a current reading is no longer above the upper fatal threshold but is still outsid…
232 …"Current '%1' reading of %2 amperes is now below the %3 upper fatal threshold but remains outside …
258 …"Indicates that a current reading no longer exceeds an internal critical level but still exceeds a…
297 …"Indicates that a frequency reading is no longer below the lower critical threshold but is still o…
[all …]
|
| H A D | sensor_event_message_registry.hpp | 57 …"Indicates that a sensor reading is no longer below the lower critical threshold but is still outs…
58 …"Sensor '%1' reading of %2 (%3) is now above the %4 lower critical threshold but remains outside o…
72 …"Indicates that a sensor reading is no longer below the lower fatal threshold but is still outside…
73 …"Sensor '%1' reading of %2 (%3) is now above the %4 lower fatal threshold but remains outside of n…
177 …"Indicates that a sensor reading is no longer above the upper critical threshold but is still outs…
178 …"Sensor '%1' reading of %2 (%3) is now below the %4 upper critical threshold but remains outside o…
192 …"Indicates that a sensor reading is no longer above the upper fatal threshold but is still outside…
193 …"Sensor '%1' reading of %2 (%3) is now below the %4 upper fatal threshold but remains outside of n…
221 …"Indicates that a sensor reading no longer exceeds an internal critical level but still exceeds an…
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/browser/ |
| H A D | test_project_config_page.py | 130 msg = 'downloads directory path starts with invalid character but ' \
139 msg = 'downloads directory path characters invalid but treated as valid'
142 # downloads dir path starts with ${...} but has a space
147 msg = 'downloads directory path characters invalid but treated as valid'
156 'downloads directory path valid but treated as invalid')
164 'downloads directory path valid but treated as invalid')
185 msg = 'sstate directory path starts with invalid character but ' \
194 msg = 'sstate directory path characters invalid but treated as valid'
197 # path starts with ${...} but has a space
202 msg = 'sstate directory path characters invalid but treated as valid'
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Net-SNMP | 21 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
31 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
51 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
61 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
71 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
85 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
97 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
107 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
|
| H A D | ParaTypeFFL-1.3 | 16 - You may bundle the fonts with commercial software, but you may not
22 placed in a separate text file or inserted into the font file, but it
30 This license has no limits on time and territory, but it becomes null
35 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
|
| H A D | Sleepycat | 26 OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
30 CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
53 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
57 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
80 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
84 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
| H A D | Spencer-99 | 7 …en credit for this package in the documentation of software which uses it, but that is not a requi…
9 …BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE…
|
| H A D | TAPR-OHL-1.0 | 36 physical things, but does not cover software, firmware, or code loaded
47 * You may distribute unmodified documentation, but you must include the
94 * You may include files in proprietary formats, but you must also
118 including but not limited to computer files in open or proprietary
144 from suit granted in Section 2), but the rights of others who have
211 but if reasonably possible, you must also include open format,
223 (including, but not limited to, copyright notices on circuit boards).
235 general provisions as the present version, but differ in detail to
241 TAPR owns the copyright to the OHL, but grants permission to any person
247 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
[all …]
|
| H A D | IJG | 7 1. We don't promise that this software works. (But if you find any bugs, please let us know!)
29 …Park, CA. ansi2knr.c is NOT covered by the above copyright and conditions, but instead by the usua…
31 …but is freely distributable. The same holds for its supporting scripts (config.guess, config.sub, …
35 … not use the LZW algorithm; the resulting GIF files are larger than usual, but are readable by all…
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/commands/ |
| H A D | test_loaddata.py | 26 "Loaded poky fixture but don't have a meta-poky for all releases"
35 "Loaded oe-core fixture but still have no openemebedded-core"
43 "Loaded settings but have no DEFAULT_RELEASE")
48 "Loaded settings but have no DEFCONF (default project "
|
| H A D | test_lsupdates.py | 30 "lsupdates ran but we still have no more layers!")
32 "lsupdates ran but we still have no more Recipes!")
34 "lsupdates ran but we still have no more Machines!")
|
| /openbmc/openbmc/poky/bitbake/lib/toaster/tests/functional/ |
| H A D | test_project_config.py | 133 msg = 'downloads directory path starts with invalid character but ' \
142 msg = 'downloads directory path characters invalid but treated as valid'
145 # downloads dir path starts with ${...} but has a space
150 msg = 'downloads directory path characters invalid but treated as valid'
159 'downloads directory path valid but treated as invalid')
167 'downloads directory path valid but treated as invalid')
190 msg = 'sstate directory path starts with invalid character but ' \
199 msg = 'sstate directory path characters invalid but treated as valid'
202 # path starts with ${...} but has a space
207 msg = 'sstate directory path characters invalid but treated as valid'
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.console | 53 fputc (like putc but redirected to a file)
54 fputs (like puts but redirected to a file)
55 fprintf (like printf but redirected to a file)
56 ftstc (like tstc but redirected to a file)
57 fgetc (like getc but redirected to a file)
68 But REMEMBER that that will work only if you have not overwritten any
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 126 | 15 # but WITHOUT ANY WARRANTY; without even the implied warranty of
52 # But if you want to be really sure, you can do this
69 # format of its backing file as such (but neither it nor qcow
96 # -- but behavior for that case is a bit strange. Protocol-prefixed paths are
98 # the path of the overlay. But since "image:base.$IMGFMT" is actually a
99 # relative path, it will always be evaluated relative to qemu's CWD (but not
|
| /openbmc/qemu/tcg/tci/ |
| H A D | tcg-target.h | 17 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
27 * real target machine but which generates virtual machine code for an
28 * interpreter. Interpreted pseudo code is slow, but it works on any host.
35 * Here the TCG target is a virtual machine, but this virtual machine must
|
| /openbmc/docs/designs/ |
| H A D | bmc-reset-with-host-up.md | 46 but do nothing. That is commonly done within a systemd service file via the
56 when the chassis power is on, but the host is unreachable. This design needs to
67 - Support custom behavior when chassis power is on but the BMC is unable to
91 firmware and talking PLDM but the BMC recovery paths will differ based on
125 to execute the following logic in situations where chassis power is on but the
141 If the chassis power is on but the BMC is unable to communicate with the host
149 but it will also show the host state as `Running`.
182 - Reboot the BMC while the host is booting, but before it's in a state where it
186 - Reboot the BMC when the host is up and running but disable the IPMI/PLDM stack
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | severity.hpp | 28 * - critical PEL but non critical LogSeverity
29 * - info PEL but non info LogSeverity
30 * - non info PEL but info LogSeverity
|
| /openbmc/openbmc/meta-raspberrypi/recipes-graphics/userland/files/ |
| H A D | 0001-mmal-Do-not-use-Werror.patch | 6 Clang warns about unused-but-set variables
7 interface/mmal/vc/mmal_vc_api.c:395:18: error: variable 'status' set but not used [-We
8 rror,-Wunused-but-set-variable]
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 12 There are two things that are different, but they have very similar
34 device feature exposure. But that is not relevant for this section.
47 Exactly the same case than the previous one, but for 5.1.
54 we have the same QEMU version in both sides (qemu-5.2) but we are using
55 the latest machine type for that version (pc-5.2) but one of an older
61 were configured on 5.1, but this should be easy in the sense that
90 compatibility problems. But the reason that we create qemu-5.2 is to
117 version. But if we want a different value for a previous version, we
139 to qemu-5.2, we only sent information for one queue, but destination
185 migration B -> C is case 3, so we don't care. But actually we
[all …]
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp.md | 8 BMC. This is primarily IPMI-based, but also includes a few hardware-specific
27 attempted, but not in a cross-implementation manner so far. This does not
75 - Be usable over simple hardware implementations, but have a facility for higher
87 This is in use by a few platforms, but should be avoided for new designs.
93 Design details for both approaches are covered in their relevant documents, but
101 Continue using IPMI, but start making more use of OEM extensions to suit the
|
| /openbmc/qemu/docs/system/ |
| H A D | bootindex.rst | 7 but you can also do this more flexibly, by setting a ``bootindex``
15 ``bootindex`` property set will be considered for booting, but they
60 can natively boot from, but if firmware relies on an option ROM for
65 the option ROM will have a boot method for each of them, but it is not
75 but not both parameters at the same time. Mixing them will result in
|
| /openbmc/openbmc/poky/bitbake/lib/bb/fetch2/ |
| H A D | README | 3 documented in the context of how OE uses it but the API calls are generic.
6 This is not enforced or tested but is required so that we can:
29 environment but only in the do_fetch tasks).
32 git recipe might be ok but you can't expect to checkout a git tree.
|
| /openbmc/openbmc/poky/ |
| H A D | MAINTAINERS.md | 9 workflow works well for single or small numbers of maintainers but we have
15 both to recognise their contributions but also empower them to help lead and
20 This file is maintained in OE-Core but may refer to components that are separate
63 * meta-gplv2 (ideally new strategy but active maintainer welcome)
|