| /openbmc/qemu/include/exec/ |
| H A D | target_long.h | 14 * Usually this should only be included via cpu-defs.h however for
16 * object we can include directly. However the build-system must
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | disk-space.rst | 22 final disk usage of 22 Gbytes instead of &MIN_DISK_SPACE; Gbytes. However,
31 disk space. However, only the most recent ones are likely to be reused.
47 exploring a set of build configurations. However, this command
|
| /openbmc/u-boot/include/configs/ |
| H A D | integrator-common.h | 37 * However it may be needed if Integrator/CP switch S2-1
47 * However, the default U-Boot code also performs the initialization.
57 * However, the default U-Boot code performs the relocation check,
|
| /openbmc/docs/designs/management-console/ |
| H A D | Authorities_List_Management.md | 16 1. It only allows replacing a single Authority object in dbus; however, Google's
20 certs; however, Google's trust bundle file contains multiple PEM encoded
91 existing codes. However, trust bundle isn't in BMCWeb, neither in Redfish
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Net-SNMP | 21 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
31 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
51 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
61 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
71 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
85 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
97 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
107 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
|
| H A D | bzip2-1.0.5 | 17 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
18 … of my knowledge, bzip2 and libbzip2 do not use any patented algorithms. However, I do not have th…
|
| H A D | Sleepycat | 32 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
59 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
86 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
| H A D | DOC | 3 …ell as copy and distribute modified versions of this software. You must, however, include this cop…
5 …stribute any of your source code that is built using DOC software. Note, however, that you may not…
9 … companies around the world provide commercial support for DOC software, however. DOC software is …
|
| H A D | BSD-3-Clause-LBNL | 9 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
12 …ctionality or performance of the source code ("Enhancements") to anyone; however, if you choose to…
|
| H A D | Catharon | 23 o We don't promise that this software works. However, we are
101 our work, you must acknowledge us. However, no fee need be paid
116 accept it. However, as the Catharon Packages are copyrighted
|
| H A D | FTL | 15 …o We don't promise that this software works. However, we will be interested in any kind of bug rep…
53 …just the unmodified files. If you use our work, you must acknowledge us. However, no fee need be p…
61 As you have not signed this license, you are not required to accept it. However, as the FreeType Pr…
|
| H A D | EUDatagrid | 20 …ures,functionality or performance of this software that you may develop. However, if you publish o…
28 …ODS OR SERVICES, LOSS OF USE, DATA OR PROFITS, OR BUSINESS INTERRUPTION, HOWEVER CAUSED AND ON ANY…
|
| H A D | gtkbook | 4 this code for any purpose, however, if this code is republished or
|
| H A D | SSH-OpenSSH | 11 * However, I am not implying to give any licenses to any patents or
18 [However, none of that term is relevant at this point in time. All of
|
| /openbmc/u-boot/drivers/usb/dwc3/ |
| H A D | io.h | 31 * However, the offsets are given starting from xHCI address space. in dwc3_readl()
45 * However, the offsets are given starting from xHCI address space. in dwc3_writel()
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-general.rst | 37 that everything works for the new release. However, this is not the
44 them much more manageable. However, sometimes it is not practical to
53 releases. However, if the append file is specific to a
|
| H A D | migration-3.0.rst | 20 settings to continue working. However, it is advisable to explicitly set
30 layer if needed. However, presently LSB support has been removed from
171 continue to work, however it may be removed in a future release.
241 starting with ``#!/bin/bash`` but has no dependency on bash. However,
280 required. However, if for some reason the software being built by one
|
| /openbmc/qemu/docs/devel/ |
| H A D | lockcnt.rst | 15 by stashing away its ``next`` pointer. However, ``ioh->fd_write`` could
31 If however this loop must also be reentrant, i.e. it is possible that
138 However, critical sections are easy to forget since you have to do
157 However, these are usually not a problem if any of the following
170 frequent and can happen on a fast path; however: 1) it is almost never
|
| /openbmc/qemu/docs/system/ |
| H A D | vm-templating.rst | 18 new VMs are able to read template VM memory; however, any modifications
59 configure VM RAM to be based on a template VM RAM file; however, the VM
93 These technologies rely on shared memory, however, the template VMs
|
| /openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/ |
| H A D | systemd-pager.sh | 1 # Systemd expect a color capable pager, however the less provided
|
| /openbmc/openbmc/poky/meta/recipes-sato/pulseaudio-sato/pulseaudio-client-conf-sato/ |
| H A D | 50-sato.conf | 2 # in Sato. The graphical session in Sato runs under root, however, and
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | Mode.interface.yaml | 6 however not all implementations may respect having this property set
|
| /openbmc/u-boot/doc/device-tree-bindings/remoteproc/ |
| H A D | remoteproc.txt | 6 drivers. However the following generic properties will be supported
|
| /openbmc/qemu/linux-user/openrisc/ |
| H A D | target_syscall.h | 7 * However, elfload.c wants this name.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
| H A D | ACE-TAO-CIAO | 16 must, however, include this copyright statement along with any code
23 that is built using DOC software. Note, however, that you may not
59 world provide commercial support for DOC software, however. DOC
|