| /openbmc/entity-manager/configurations/ |
| H A D | VENDORS.md | 11 when multiple companies are involved in the chain between design and end-user.
29 3. When one company primarily oversees the design but other companies
|
| /openbmc/linux/Documentation/process/ |
| H A D | contribution-maturity-model.rst | 14 the conclusions from that discussion included that companies which are a
65 authored by engineers from other companies) as part of their job
|
| H A D | 1.Intro.rst | 62 (and companies) wishing to participate in its development. Hardware
78 involve over 1000 developers working for more than 100 different companies
120 Some companies and developers occasionally wonder why they should bother
|
| H A D | 3.Early-stage.rst | 211 disclose its plans early in the development process. Companies with
214 problems later. For companies without that sort of in-house expertise, the
|
| H A D | kernel-enforcement-statement.rst | 41 software. We want companies and individuals to use, modify and distribute
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NGPL | 9 The license agreements of most software companies keep you at the mercy of those companies. By cont…
|
| H A D | SMAIL_GPL | 32 The license agreements of most software companies keep you at the
33 mercy of those companies. By contrast, our general public license is
|
| H A D | GPL-1.0-only | 14 The license agreements of most software companies try to keep users
15 at the mercy of those companies. By contrast, our General Public
|
| H A D | GPL-1.0-or-later | 13 The license agreements of most software companies try to keep users at the
14 mercy of those companies. By contrast, our General Public License is intended
|
| H A D | TORQUE-1.1 | 20 … SHALL ADAPTIVE COMPUTING ENTERPRISES, INC. CORPORATION, ITS AFFILIATED COMPANIES, OR THE U.S. GOV…
|
| H A D | OpenPBS-2.3 | 66 IN NO EVENT SHALL VERIDIAN CORPORATION, ITS AFFILIATED COMPANIES, OR THE
|
| H A D | DOC | 9 …ssist in its use, correction, modification, or enhancement. A number of companies around the world…
|
| H A D | BSD-Protection | 13 In addition, one can imagine that companies which operate by producing and selling (possibly closed…
|
| /openbmc/openbmc/meta-yadro/ |
| H A D | README.md | 7 of leading technology companies.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | btrfs.rst | 9 Jointly developed by several companies, licensed under the GPL and open for
|
| /openbmc/u-boot/doc/ |
| H A D | README.semihosting | 21 companies can purchase licenses for and contain much more functionality.
|
| /openbmc/linux/Documentation/devicetree/bindings/i2c/ |
| H A D | st,nomadik-i2c.yaml | 12 DB8500 after the merge of these two companies wireless divisions.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/zabbix/ |
| H A D | zabbix_6.2.7.bb | 16 organisations with a few servers and for large companies with a \
|
| /openbmc/linux/LICENSES/deprecated/ |
| H A D | GPL-1.0 | 23 The license agreements of most software companies try to keep users
24 at the mercy of those companies. By contrast, our General Public
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/custom-licenses/ |
| H A D | STM-SLA0044-Rev5 | 3 …TMICROELECTRONICS INTERNATIONAL N.V, SWISS BRANCH AND/OR ITS AFFILIATED COMPANIES (STMICROELECTRON…
|
| /openbmc/qemu/docs/system/ |
| H A D | target-riscv.rst | 14 many different companies with different devices, and these SoCs are
|
| H A D | target-arm.rst | 17 many different companies with different devices, and these SoCs are
|
| /openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
| H A D | UFL | 29 "Copyright Holder(s)" refers to all individuals and companies who have a
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/opensaf/ |
| H A D | opensaf_5.22.01.bb | 5 established by leading Communications and Enterprise Computing Companies to \
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | bttv-devel.rst | 59 These pins are also used by some companies to drive remote control
|