/openbmc/linux/Documentation/filesystems/ |
H A D | orangefs.rst | 253 a pointer to each buffer is added to its own PVFS_dev_map_desc structure 275 to each of the pages in the IO buffer through a call to get_user_pages. 408 union of structs, each of which is associated with a particular 523 if getattr_time has not timed out. Getattr_time is updated each time the
|
/openbmc/linux/Documentation/scsi/ |
H A D | scsi_fc_transport.rst | 50 mechanism, adding a fabric header to each frame allows the port to 52 obtain an N_Port_ID on each fabric it joins. Each fabric will have its 55 on each virtual fabric. 69 each will appear as a unique scsi_host with its own target and lun space.
|
/openbmc/linux/Documentation/accel/qaic/ |
H A D | aic100.rst | 83 multiple NSPs may be assigned to a single workload. Since each NSP can only run 93 channels, each consisting of a set of request/response FIFOs. Each active 254 The values in each register are indexes in the FIFO. To get the location of the 478 have multiple users, each with their own workload running. If the workload of
|
/openbmc/linux/Documentation/core-api/ |
H A D | kobject.rst | 14 all of which make reference to each other. In an attempt to make things 42 When you see a sysfs directory full of other directories, generally each 326 each other. There is no restriction that they be of the same ktype, but be 426 called, and the objects in the former circle release each other.
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A D | writing_musb_glue_layer.rst | 120 For the sake of readability each function will be split in logical 121 parts, each part being shown as if it was independent from the others. 431 ``arch/mips/jz4740/platform.c``. In the ``platform.c`` file each device of the 622 Looking at the configuration table above, we see that each endpoints is 626 hardware), and maxpacket defines the maximum size of each data packet
|
/openbmc/linux/LICENSES/dual/ |
H A D | MPL-1.1 | 24 1.1. "Contributor" means each entity that creates or contributes to 32 combination of the Original Code and Modifications, in each case 123 Subject to third party intellectual property claims, each Contributor 224 You must duplicate the notice in Exhibit A in each file of the Source 433 As between Initial Developer and the Contributors, each party is
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | CUA-OPL-1.0 | 9 1.1. "Contributor" means each entity that creates or contributes to 17 combination of the Original Code and Modifications, in each case 110 Subject to third party intellectual property claims, each Contributor 214 You must duplicate the notice in Exhibit A in each file of the Source 421 As between Initial Developer and the Contributors, each party is
|
H A D | MPL-1.1 | 9 means each entity that creates or contributes to the creation of Modifications. 13 …difications or the combination of the Original Code and Modifications, in each case including port… 50 Subject to third party intellectual property claims, each Contributor hereby grants You a world-wid… 86 You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible t… 148 As between Initial Developer and the Contributors, each party is responsible for claims and damages…
|
H A D | GFDL-1.3 | 163 copy along with each Opaque copy, or state in or with each Opaque copy 226 the substance and tone of each of the contributor acknowledgements 277 different contents, make the title of each such section unique by 296 of this License for verbatim copying of each of the documents in all
|
H A D | GFDL-1.3-no-invariants-or-later | 52 …include a machine-readable Transparent copy along with each Opaque copy, or state in or with each … 69 …of the section, and preserve in the section all the substance and tone of each of the contributor … 87 …ant Sections with the same name but different contents, make the title of each such section unique… 93 …rovided that you follow the rules of this License for verbatim copying of each of the documents in…
|
H A D | GFDL-1.3-no-invariants-only | 52 …include a machine-readable Transparent copy along with each Opaque copy, or state in or with each … 69 …of the section, and preserve in the section all the substance and tone of each of the contributor … 87 …ant Sections with the same name but different contents, make the title of each such section unique… 93 …rovided that you follow the rules of this License for verbatim copying of each of the documents in…
|
H A D | GFDL-1.3-invariants-or-later | 52 …include a machine-readable Transparent copy along with each Opaque copy, or state in or with each … 69 …of the section, and preserve in the section all the substance and tone of each of the contributor … 87 …ant Sections with the same name but different contents, make the title of each such section unique… 93 …rovided that you follow the rules of this License for verbatim copying of each of the documents in…
|
H A D | GFDL-1.3-only | 52 …include a machine-readable Transparent copy along with each Opaque copy, or state in or with each … 69 …of the section, and preserve in the section all the substance and tone of each of the contributor … 87 …ant Sections with the same name but different contents, make the title of each such section unique… 93 …rovided that you follow the rules of this License for verbatim copying of each of the documents in…
|
H A D | GFDL-1.3-invariants-only | 52 …include a machine-readable Transparent copy along with each Opaque copy, or state in or with each … 69 …of the section, and preserve in the section all the substance and tone of each of the contributor … 87 …ant Sections with the same name but different contents, make the title of each such section unique… 93 …rovided that you follow the rules of this License for verbatim copying of each of the documents in…
|
H A D | Interbase-1.0 | 8 1.1. ''Contributor'' means each entity that creates or contributes to the creation of Modifications. 12 …difications or the combination of the Original Code and Modifications, in each case including port… 56 Subject to third party intellectual property claims, each Contributor hereby grants You a world-wid… 96 You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible t… 171 As between Initial Developer and the Contributors, each party is responsible for claims and damages…
|
H A D | GFDL-1.3-or-later | 52 …include a machine-readable Transparent copy along with each Opaque copy, or state in or with each … 69 …of the section, and preserve in the section all the substance and tone of each of the contributor … 87 …ant Sections with the same name but different contents, make the title of each such section unique… 93 …rovided that you follow the rules of this License for verbatim copying of each of the documents in…
|
H A D | BitTorrent-1.0 | 81 that you receive from any Contributor. By application of the provisions in Section 4(a) below, each… 148 in each file of the Source Code of any copy you distribute of the Licensed Product. If you created … 254 11. Responsibility for Claims. As between Licensor and Contributors, each party is responsible fo… 289 …etical order, for the convenience of the reader. The Section of this License in which each defined 319 The Notice below must appear in each file of the Source Code of any copy you distribute of the Lice…
|
H A D | NOSL | 8 … 1.1. "Contributor" means each entity that creates or contributes to the creation of Modifications. 12 …difications or the combination of the Original Code and Modifications, in each case including port… 47 …Subject to third party intellectual property claims, each Contributor hereby grants You a world-wi… 70 …You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible … 130 As between Initial Developer and the Contributors, each party is responsible for claims and damages…
|
/openbmc/linux/Documentation/networking/ |
H A D | switchdev.rst | 86 struct net_device (using register_netdev()) for each enumerated physical switch 107 ndo_get_port_parent_id for each port netdev, returning the same physical ID for 108 each port of a switch. The ID must be unique between switches on the same 128 name for each port using port PHYS name. The udev rule would be:: 428 (proprietary metadata for each network port for instance).
|
/openbmc/openbmc/poky/documentation/ref-manual/ |
H A D | terms.rst | 238 for each type of system, to include the specific kernel modules 482 provide an :term:`SBOM` associated to each software image. 498 each compiled for a target instruction set (such as ``armv5``, 502 of the Yocto Project, each recipe has two sysroots: 518 One of the major benefits of the build system is that, since each
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | layers.rst | 8 Layers allow you to isolate different types of customizations from each 179 for each recipe that uses an include file. Or, if you are introducing 349 - *Acceptance Criteria:* Provide "Yes" or "No" answers for each of the 430 # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf 442 BitBake parses each ``conf/layer.conf`` file from the top down as 444 file. During the processing of each ``conf/layer.conf`` file, BitBake 699 cleaned up. The contents of each ``.bbappend`` end up in the
|
/openbmc/linux/Documentation/arch/sparc/oradax/ |
H A D | dax-hv-api.txt | 27 … of the submitted operations reported through a Completion Area linked to each CCB. Each CCB has a 365 0xD 2 byte elements where each element is the index value of a bit, 367 0xE 4 byte elements where each element is the index value of a bit, 373 … On platforms which support ADI, the ADI version number may be specified for each separate memory 382 …The ADI value is only guaranteed to be checked on the first 64 bytes of each data access. Mismatch… 600 …0xD, and 0xE). For the standard scan command using the bit vector output, for each input element t… 604 …output format contains one array entry for each input element that matched the scan criteria. Each… 725 …s, and outputs a bit vector or index array created by reading the tables bit value at each index in 835 …which input elements to include in the output. For each bit set at a given index N within the bit … 1120 as either a real or virtual addresses, with the type of each address indicated in flags. Virtual ad… [all …]
|
/openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
H A D | bitbake-user-manual-ref-variables.rst | 224 subsequent warnings are issued each time disk space or number of free 255 issue subsequent warnings each time the available disk space further 258 based on the interval occur each time a respective interval is 466 where each provides the same output. This scenario is usually 644 than querying the source control system each time. 756 the other ``BBFILE_*`` variables. Typically, each layer appends its 767 Assigns the priority for recipe files in each layer. 912 each separate configuration (multiconfig). You can use this variable 913 to cause BitBake to build multiple targets where each target has a 917 As an example, the following line specifies three multiconfigs, each [all …]
|
/openbmc/linux/Documentation/infiniband/ |
H A D | ipoib.rst | 15 When the IPoIB driver is loaded, it creates one interface for each
|
/openbmc/linux/Documentation/driver-api/media/ |
H A D | rc-core.rst | 37 *PULSE* and *SPACE* events, each with a given duration.
|