| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Artistic-1.0 | 5 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
10 "Standard Version" refers to such a Package if it has not been modified, or has been modified in ac…
15 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
17 … Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
21 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
25 …non-standard executables so the names do not conflict with standard executables, which must also b…
31 …e a Standard Version of the executables and library files, together with instructions (in the manu…
33 b) accompany the distribution with the machine-readable source of the Package with your modificatio…
35 …non-standard executables with their corresponding Standard Version executables, giving the non-sta…
|
| H A D | NBPL-1.0 | 9 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
15 …"Standard Version" refers to such a Package if it has not been modified, or has been modified in a…
25 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
27 … Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
31 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
35 …non-standard executables so the names do not conflict with standard executables, which must also b…
41 …e a Standard Version of the executables and library files, together with instructions (in the manu…
43 …b) accompany the distribution with the machine-readable source of the Package with your modificati…
45 …non-standard executables with their corresponding Standard Version executables, giving the non-sta…
|
| H A D | Artistic-1.0-cl8 | 5 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
11 …"Standard Version" refers to such a Package if it has not been modified, or has been modified in a…
21 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
23 … Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
27 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
29 …non-standard executables so the names do not conflict with standard executables, which must also b…
34 …e a Standard Version of the executables and library files, together with instructions (in the manu…
35 …b) accompany the distribution with the machine-readable source of the Package with your modificati…
36 …non-standard executables with their corresponding Standard Version executables, giving the non-sta…
|
| H A D | OLDAP-1.1 | 10 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
16 …"Standard Version" refers to such a Package if it has not been modified, or has been modified in a…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 … Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
32 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
36 …non-standard executables so the names do not conflict with standard executables, which must also b…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
44 …b) accompany the distribution with the machine-readable source of the Package with your modificati…
46 …non-standard executables with their corresponding Standard Version executables, giving the non-sta…
|
| H A D | OLDAP-1.2 | 10 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
16 …"Standard Version" refers to such a Package if it has not been modified, or has been modified in a…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 … Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
32 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
36 …non-standard executables so the names do not conflict with standard executables, which must also b…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
44 …b) accompany the distribution with the machine-readable source of the Package with your modificati…
46 …non-standard executables with their corresponding Standard Version executables, giving the non-sta…
|
| H A D | OLDAP-1.3 | 4 Copyright 1998-1999, The OpenLDAP Foundation. All Rights Reserved.
10 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
16 …"Standard Version" refers to such a Package if it has not been modified, or has been modified in a…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 … Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
32 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
36 …non-standard executables so the names do not conflict with standard executables, which must also b…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
44 …b) accompany the distribution with the machine-readable source of the Package with your modificati…
46 …non-standard executables with their corresponding Standard Version executables, giving the non-sta…
|
| H A D | OLDAP-1.4 | 4 Copyright 1998-1999, The OpenLDAP Foundation. All Rights Reserved.
10 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
16 …"Standard Version" refers to such a Package if it has not been modified, or has been modified in a…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 … Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
32 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
36 …non-standard executables so the names do not conflict with standard executables, which must also b…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
44 …b) accompany the distribution with the machine-readable source of the Package with your modificati…
46 …non-standard executables with their corresponding Standard Version executables, giving the non-sta…
|
| H A D | OGTSL | 10 distribute the Package in a more-or-less customary fashion, plus
14 standards-based products.
22 multi-platform application software.
24 For suppliers: In-depth testing increases customer satisfaction and
46 "Standard Version" refers to such a Package if it has not been
63 the Standard Version of this Package without restriction, provided
70 the Standard Version.
77 rename any non-standard executables and testcases so the
78 names do not conflict with standard executables and
80 separate manual page for each non-standard executable and
[all …]
|
| H A D | ClArtistic | 10 the Package in a more-or-less customary fashion, plus the right to make
19 "Standard Version" refers to such a Package if it has not been
38 Standard Version of this Package without restriction, provided that you
44 considered the Standard Version.
55 Copyright Holder to include your modifications in the Standard Version
60 c) rename any non-standard executables so the names do not conflict
61 with standard executables, which must also be provided, and provide
62 a separate manual page for each non-standard executable that clearly
63 documents how it differs from the Standard Version.
75 a) distribute a Standard Version of the executables and library files,
[all …]
|
| H A D | Artistic-1.0-Perl | 5 …users of the package the right to use and distribute the Package in a more-or-less customary fashi…
11 …"Standard Version" refers to such a Package if it has not been modified, or has been modified in a…
21 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
23 …Copyright Holder. A Package modified in such a way shall still be considered the Standard Version.
27 …r by allowing the Copyright Holder to include your modifications in the Standard Version of the Pa…
29 …non-standard executables so the names do not conflict with standard executables, which must also b…
34 …e a Standard Version of the executables and library files, together with instructions (in the manu…
35 …b) accompany the distribution with the machine-readable source of the Package with your modificati…
36 …non-standard executables non-standard names, and clearly document the differences in manual pages …
39 … be construed as a mere form of aggregation, provided that the complete Standard Version of the in…
[all …]
|
| H A D | Artistic-2.0 | 4 Copyright (c) 2000-2006, The Perl Foundation.
37 those files. A given Package may consist of either the Standard
48 "Standard Version" refers to the Package if it has not been
57 the Standard Version of the Package, in its current version or as
70 (1) You are permitted to use the Standard Version and create and use
75 Permissions for Redistribution of the Standard Version
78 Standard Version of this Package in any medium without restriction,
86 Package will still be considered the Standard Version, and as such
95 from the Standard Version, including, but not limited to, documenting
96 any non-standard features, executables, or modules, and provided that
[all …]
|
| H A D | Ruby | 21 c) rename any non-standard executables so the names do not conflict
22 with standard executables, which must also be provided.
33 b) accompany the distribution with the machine-readable source of
36 c) give non-standard executables non-standard names, with
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_sol.robot | 20 @{setinprogress} set-complete set-in-progress commit-write
30 ${msg}= Run Keyword Run External IPMI Standard Command
45 ${msg}= Run Keyword Run External IPMI Standard Command
55 ${msg}= Run Keyword And Expect Error * Run External IPMI Standard Command
67 Set SOL Setting privilege-level ${item}
78 ${msg}= Run Keyword And Expect Error * Run External IPMI Standard Command
79 ... sol set privilege-level ${value}
90 ${msg}= Run Keyword And Expect Error * Run External IPMI Standard Command
91 ... sol set retry-count ${value}
102 ${msg}= Run Keyword And Expect Error * Run External IPMI Standard Command
[all …]
|
| /openbmc/linux/arch/riscv/ |
| H A D | Kconfig.errata | 20 non-standard handling on non-coherent operations on Andes cores.
35 bool "Apply SiFive errata CIP-453"
39 This will apply the SiFive CIP-453 errata to add sign extension
46 bool "Apply SiFive errata CIP-1200"
50 This will apply the SiFive CIP-1200 errata to repalce all
57 bool "T-HEAD errata"
60 All T-HEAD errata Kconfig depend on this Kconfig. Disabling
61 this Kconfig will disable all T-HEAD errata. Please say "Y"
62 here if your platform uses T-HEAD CPU cores.
67 bool "Apply T-Head memory type errata"
[all …]
|
| /openbmc/linux/Documentation/riscv/ |
| H A D | uabi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 RISC-V Linux User ABI
7 ------------------------------------
14 #. Single-letter extensions come first, in canonical order.
17 #. All multi-letter extensions will be separated from other extensions by an
20 #. Additional standard extensions (starting with 'Z') will be sorted after
21 single-letter extensions and before any higher-privileged extensions.
23 #. For additional standard extensions, the first letter following the 'Z'
29 #. Standard supervisor-level extensions (starting with 'S') will be listed
30 after standard unprivileged extensions. If multiple supervisor-level
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | pmbus-core.rst | 8 [from pmbus.org] The Power Management Bus (PMBus) is an open standard
9 power-management protocol with a fully defined command language that facilitates
11 protocol is implemented over the industry-standard SMBus serial interface and
12 enables programming, control, and real-time monitoring of compliant power
13 conversion products. This flexible and highly versatile standard allows for
17 semiconductor companies, this open power system standard is maintained and
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
22 commands, and manufacturers can add as many non-standard commands as they like.
23 Also, different PMBUs devices act differently if non-supported commands are
43 PMBus device capabilities auto-detection
[all …]
|
| H A D | submitting-patches.rst | 10 ----------
14 - Documentation/process/submit-checklist.rst
15 - Documentation/process/submitting-patches.rst
16 - Documentation/process/coding-style.rst
18 * Please run your patch through 'checkpatch --strict'. There should be no
22 * Please use the standard multi-line comment style. Do not mix C and C++
34 hardware. In such cases, you should test-build the code on at least one
35 architecture. If run-time testing was not achieved, it should be written
43 -------------------------------------------
58 --------------
[all …]
|
| /openbmc/linux/drivers/net/dsa/ |
| H A D | vitesse-vsc73xx-core.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Vitesse VSC7385 SparX-G5 5+1-port Integrated Gigabit Ethernet Switch
4 * Vitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet Switch
5 * Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Switch
6 * Vitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet Switch
8 * These switches have a built-in 8051 CPU and can download and execute a
10 * handling the switch in a memory-mapped manner by connecting to that external
31 #include "vitesse-vsc73xx.h"
33 #define VSC73XX_BLOCK_MAC 0x1 /* Subblocks 0-4, 6 (CPU port) */
37 #define VSC73XX_BLOCK_CAPTURE 0x4 /* Subblocks 0-4, 6, 7 */
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | wait_bit.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
6 * Linux wait-bit related types and methods:
55 * wait_on_bit - wait for a bit to be cleared
60 * There is a standard hashed waitqueue table for generic use. This
66 * Returned value will be zero if the bit was cleared, or non-zero
82 * wait_on_bit_io - wait for a bit to be cleared
87 * Use the standard hashed waitqueue table to wait for a bit
91 * Returned value will be zero if the bit was cleared, or non-zero
107 * wait_on_bit_timeout - wait for a bit to be cleared or a timeout elapses
113 * Use the standard hashed waitqueue table to wait for a bit
[all …]
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | advanced.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 Working with Advanced Metadata (``yocto-kernel-cache``)
19 :ref:`overview-manual/development-environment:yocto project source repositories`
20 is the ``yocto-kernel-cache`` Git repository. You can find this repository
24 Kernel development tools ("kern-tools") are also available in the Yocto Project
26 ``yocto-kernel-tools`` Git repository. The recipe that builds these
27 tools is ``meta/recipes-kernel/kern-tools/kern-tools-native_git.bb`` in
35 Metadata, which is located in the ``yocto-kernel-cache`` Git repository.
37 definitions in linux-yocto recipes for corresponding BSPs. A BSP
39 hardware-specific features. The BSP can be influenced from within the
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-support/rasdaemon/ |
| H A D | rasdaemon_0.8.0.bb | 3 LICENSE = "GPL-2.0-only"
15 RDEPENDS:${BPN} = "perl perl-module-file-basename perl-module-file-find perl-module-file-spec perl-…
16 perl-module-posix perl-module-file-glob libdbi-perl libdbd-sqlite-perl"
18 inherit autotools pkgconfig update-rc.d systemd
21 PACKAGECONFIG[sqlite3] = "--enable-sqlite3,--disable-sqlite3,sqlite3"
22 PACKAGECONFIG[mce] = "--enable-mce,--disable-mce"
23 PACKAGECONFIG[aer] = "--enable-aer,--disable-aer"
24 PACKAGECONFIG[extlog] = "--enable-extlog,--disable-extlog"
25 PACKAGECONFIG[devlink] = "--enable-devlink,--disable-devlink"
26 PACKAGECONFIG[diskerror] = "--enable-diskerror,--disable-diskerror"
[all …]
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | css.rst | 5 functionless) channel paths, and channel devices (virtio-ccw, 3270, and
6 devices passed via vfio-ccw). It supports multiple subchannel sets (MSS) and
7 multiple channel subsystems extended (MCSS-E).
14 enable MCSS-E. Note that devices with a different cssid will not be visible
15 if the guest OS does not enable MCSS-E (which is true for all supported guest
18 Supported values for the subchannel set id (``<ssid>``) range from ``0-3``.
24 The device number can range from ``0-0xffff``.
36 --------
38 * a virtio-net device, cssid/ssid/devno automatically assigned::
40 -device virtio-net-ccw
[all …]
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | howto.rst | 1 .. include:: ../disclaimer-ita.rst
14 sviluppo kernel Linux. Il documento non tratterà alcun aspetto
23 ------------
36 L'assembly (di qualsiasi architettura) non è richiesto, a meno che non
38 Sebbene essi non siano un buon sostituto ad un solido studio del
39 linguaggio C o ad anni di esperienza, i seguenti libri sono, se non
42 - "The C Programming Language" di Kernighan e Ritchie [Prentice Hall]
43 - "Practical C Programming" di Steve Oualline [O'Reilly]
44 - "C: A Reference Manual" di Harbison and Steele [Prentice Hall]
47 Sebbene si attenga allo standard ISO C11, esso utilizza una serie di
[all …]
|
| /openbmc/u-boot/scripts/dtc/libfdt/ |
| H A D | libfdt.h | 4 * libfdt - Flat Device Tree manipulation
23 * MA 02110-1301 USA
75 * offset which is out-of-bounds, or which points to an
84 * length, or the phandle value was either 0 or -1, which are
88 * tree created by the sequential-write functions, which is
97 * device tree at all - it is missing the flattened device
102 * read-write functions, this may mean that fdt_open_into() is
109 /* FDT_ERR_BADLAYOUT: For read-write functions, the given
110 * device tree has it's sub-blocks in an order that the
113 * into a form suitable for the read-write operations. */
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | colorspaces.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
40 standard that defines spectral weighting functions that model the
41 perception of color. Specifically that standard defines functions that
97 the non-linear component value, which is a closer match to the
98 non-linear performance of both the eye and displays. Linear component
99 values are denoted RGB, non-linear are denoted as R'G'B'. In general
102 provide linear RGB colors or to use the built-in openGL support to apply
106 non-linear R'G'B' to non-linear Y'CbCr. This function is determined by
107 the so-called luma coefficients. There may be multiple possible Y'CbCr
148 colorspace standard only defines some, and you have to rely on other
[all …]
|