Home
last modified time | relevance | path

Searched full:standard (Results 1 – 25 of 4282) sorted by relevance

12345678910>>...172

/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Dstandard.rst17 V4L2 defines one bit for each analog video standard currently in use
21 standard, although presenting the user a menu of supported standards is
29 standards also contain sets of one or more standard bits.
32 signals. The first enumerated standard is a set of B and G/PAL, switched
38 To query and select the standard used by the current video input or
41 *received* standard can be sensed with the
47 :ref:`v4l2_std_id <v4l2-std-id>` type (a standard set), *not* an
48 index into the standard enumeration. Drivers must implement all video
49 standard ioctls when the device has one or more video inputs or outputs.
56 video standard, or
[all …]
H A Dvidioc-querystd.rst13 VIDIOC_QUERYSTD - VIDIOC_SUBDEV_QUERYSTD - Sense the video standard received by the current input
38 The hardware may be able to detect the current video standard
50 Drivers shall *not* switch the video standard
51 automatically if a new video standard is detected. Instead, drivers
54 :ref:`VIDIOC_QUERYSTD`. The reason is that a new video standard can mean
58 standard is valid they will have to stop streaming, set the new
59 standard, allocate new buffers and start streaming again.
69 Standard video timings are not supported for this input or output.
/openbmc/linux/Documentation/devicetree/bindings/riscv/
H A Dextensions.yaml15 RISC-V has a large number of extensions, some of which are "standard"
21 Once a standard extension has been ratified, no changes in behaviour can be
23 The properties for standard extensions therefore map to their originally
80 The standard M extension for integer multiplication and division, as
86 The standard A extension for atomic instructions, as ratified in the
91 The standard F extension for single-precision floating point, as
97 The standard D extension for double-precision floating-point, as
103 The standard Q extension for quad-precision floating-point, as
109 The standard C extension for compressed instructions, as ratified in
114 The standard V extension for vector operations, as ratified
[all …]
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DArtistic-1.010 "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 …standard executables so the names do not conflict with standard executables, which must also be pr…
31 …e a Standard Version of the executables and library files, together with instructions (in the manu…
35 …standard executables with their corresponding Standard Version executables, giving the non-standar…
H A DNBPL-1.015 …"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 …standard executables so the names do not conflict with standard executables, which must also be pr…
41 …e a Standard Version of the executables and library files, together with instructions (in the manu…
45 …standard executables with their corresponding Standard Version executables, giving the non-standar…
H A DArtistic-1.0-cl811 …"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 …standard executables so the names do not conflict with standard executables, which must also be pr…
34 …e a Standard Version of the executables and library files, together with instructions (in the manu…
36 …standard executables with their corresponding Standard Version executables, giving the non-standar…
H A DOLDAP-1.116 …"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 …standard executables so the names do not conflict with standard executables, which must also be pr…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
46 …standard executables with their corresponding Standard Version executables, giving the non-standar…
H A DOLDAP-1.216 …"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 …standard executables so the names do not conflict with standard executables, which must also be pr…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
46 …standard executables with their corresponding Standard Version executables, giving the non-standar…
H A DClArtistic19 "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,
77 to get the Standard Version.
[all …]
H A DArtistic-2.037 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
100 of the Standard Version, under the Original License, so that the
[all …]
H A DOLDAP-1.316 …"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 …standard executables so the names do not conflict with standard executables, which must also be pr…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
46 …standard executables with their corresponding Standard Version executables, giving the non-standar…
H A DArtistic-1.0-Perl11 …"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 …standard executables so the names do not conflict with standard executables, which must also be pr…
34 …e a Standard Version of the executables and library files, together with instructions (in the manu…
36 …standard executables non-standard names, and clearly document the differences in manual pages (or …
39 … be construed as a mere form of aggregation, provided that the complete Standard Version of the in…
41 …and 4, provided that you do not represent such an executable image as a Standard Version of this P…
H A DOLDAP-1.416 …"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 …standard executables so the names do not conflict with standard executables, which must also be pr…
42 …e a Standard Version of the executables and library files, together with instructions (in the manu…
46 …standard executables with their corresponding Standard Version executables, giving the non-standar…
H A DOGTSL46 "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
82 Standard Version.
87 accompany any non-standard executables and testcases with
88 their corresponding Standard Version executables and
89 testcases, giving the non-standard executables and
[all …]
H A DIEC-Code-Components-EULA9 - The software license extends to modifications permitted under the relevant IEC standard.
13 relevant IEC standard may be referenced when claiming compliance with the relevant IEC
14 standard.
16 the IEC standard from which it is taken. Such attribution (e.g., “This code was derived from IEC
17 [insert standard reference number:publication year] within modifications permitted in the
18 relevant IEC standard. Please reproduce this note if possible.”), may be placed in the code itself
23 BEGINS> and <CODE ENDS>, or otherwise clearly labeled in this standard as a Code
/openbmc/openbmc-test-automation/ipmi/
H A Dtest_ipmi_disable.robot16 ... AND Run Inband IPMI Standard Command lan set ${CHANNEL_NUMBER} access on
19 Run Inband IPMI Standard Command lan set ${CHANNEL_NUMBER} access off
21 ... Run External IPMI Standard Command lan print ${CHANNEL_NUMBER}
24 Run Inband IPMI Standard Command lan set ${CHANNEL_NUMBER} access on
36 ... AND Run Inband IPMI Standard Command lan set ${CHANNEL_NUMBER} access on
40 ... Run External IPMI Standard Command lan set ${CHANNEL_NUMBER} access off
43 ... Run External IPMI Standard Command lan print ${CHANNEL_NUMBER}
46 Run Inband IPMI Standard Command lan set ${CHANNEL_NUMBER} access on
58 ... AND Run Inband IPMI Standard Command lan set ${CHANNEL_NUMBER} access on
61 Run Inband IPMI Standard Command lan set ${CHANNEL_NUMBER} access off
[all …]
/openbmc/openbmc/poky/meta/recipes-kernel/linux/
H A Dlinux-yocto_6.6.bb1 KBRANCH ?= "v6.6/standard/base"
10 KBRANCH:qemuarm ?= "v6.6/standard/arm-versatile-926ejs"
11 KBRANCH:qemuarm64 ?= "v6.6/standard/qemuarm64"
12 KBRANCH:qemumips ?= "v6.6/standard/mti-malta32"
13 KBRANCH:qemuppc ?= "v6.6/standard/qemuppc"
14 KBRANCH:qemuriscv64 ?= "v6.6/standard/base"
15 KBRANCH:qemuriscv32 ?= "v6.6/standard/base"
16 KBRANCH:qemux86 ?= "v6.6/standard/base"
17 KBRANCH:qemux86-64 ?= "v6.6/standard/base"
18 KBRANCH:qemuloongarch64 ?= "v6.6/standard/base"
[all …]
H A Dlinux-yocto_6.12.bb1 KBRANCH ?= "v6.12/standard/base"
10 KBRANCH:qemuarm ?= "v6.12/standard/arm-versatile-926ejs"
11 KBRANCH:qemuarm64 ?= "v6.12/standard/base"
12 KBRANCH:qemumips ?= "v6.12/standard/mti-malta32"
13 KBRANCH:qemuppc ?= "v6.12/standard/qemuppc"
14 KBRANCH:qemuriscv64 ?= "v6.12/standard/base"
15 KBRANCH:qemuriscv32 ?= "v6.12/standard/base"
16 KBRANCH:qemux86 ?= "v6.12/standard/base"
17 KBRANCH:qemux86.104 ?= "v6.12/standard/base"
18 KBRANCH:qemuloongarch64 ?= "v6.12/standard/base"
[all …]
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dadvanced.rst72 KBRANCH:beaglebone-yocto = "standard/beaglebone"
83 you do not specify a :term:`LINUX_KERNEL_TYPE`, it defaults to "standard".
87 configuration. The linux-yocto recipes define "standard", "tiny", and
365 LINUX_KERNEL_TYPE ??= "standard"
381 Three kernel types ("standard", "tiny", and "preempt-rt") are supported
384 - "standard": Includes the generic Linux kernel policy of the Yocto
391 This kernel type inherits from the "standard" kernel type.
395 from the "standard" configuration. Although the "tiny" kernel type
400 ``standard.scc``). Here is a partial listing for the ``standard.scc``
401 file, which is found in the ``ktypes/standard`` directory of the
[all …]
/openbmc/linux/Documentation/riscv/
H A Duabi.rst20 #. Additional standard extensions (starting with 'Z') will be sorted after
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
33 #. Standard machine-level extensions (starting with 'Zxm') will be listed
34 after any lower-privileged, standard extensions. If multiple machine-level
37 #. Non-standard extensions (starting with 'X') will be listed after all standard
38 extensions. If multiple non-standard extensions are listed, they will be
/openbmc/qemu/scripts/
H A Dupdate-linux-headers.sh21 # - include/standard-headers/ for files that are used for guest
76 # Let users of include/standard-headers/linux/ headers pick the
80 arch_cmd='s/<asm\/\([^>]*\)>/"standard-headers\/asm-'$arch'\/\1"/'
89 -e 's/"\(input-event-codes\.h\)"/"standard-headers\/linux\/\1"/' \
90 -e 's/<linux\/\([^>]*\)>/"standard-headers\/linux\/\1"/' \
152 rm -rf "$output/include/standard-headers/asm-$arch"
153 mkdir -p "$output/include/standard-headers/asm-$arch"
155 cp_portable "$hdrdir/include/asm/virtio-ccw.h" "$output/include/standard-headers/asm-s390/"
173 cp_portable "$hdrdir/include/asm/kvm_para.h" "$output/include/standard-headers/asm-$arch"
175 #include "standard-headers/asm-$arch/kvm_para.h"
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/libopus/
H A Dlibopus_1.5.2.bb41 #| {standard input}: Assembler messages:
42 #| {standard input}:389: Error: selected processor does not support Thumb mode `smull r5,r7,r1,r4'
43 #| {standard input}:418: Error: selected processor does not support Thumb mode `smull r5,r6,r4,r1'
44 #| {standard input}:448: Error: selected processor does not support Thumb mode `smull r4,r5,r1,r0'
45 #| {standard input}:474: Error: selected processor does not support Thumb mode `smull r0,r4,r8,r1'
46 #| {standard input}:510: Error: selected processor does not support Thumb mode `smull fp,r0,r10,r1'
47 #| {standard input}:553: Error: selected processor does not support Thumb mode `smull fp,r1,r10,r3'
48 #| {standard input}:741: Error: selected processor does not support Thumb mode `smull r3,r0,r6,r10'
49 #| {standard input}:761: Error: selected processor does not support Thumb mode `smull fp,r2,r3,r9'
50 #| {standard input}:773: Error: selected processor does not support Thumb mode `smull fp,r3,r5,r8'
/openbmc/openbmc/poky/documentation/sdk-manual/
H A Dappendix-customizing-standard.rst4 Customizing the Standard SDK
7 This appendix presents customizations you can apply to the standard SDK.
9 Adding Individual Packages to the Standard SDK
12 When you build a standard SDK using the ``bitbake -c populate_sdk``, a
25 Adding API Documentation to the Standard SDK
29 provided by recipes with the standard SDK by adding "api-documentation"
34 documentation and then include it in the standard SDK.
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/cim-schema/files/
H A DLICENSE10 // Implementation of certain elements of this standard or proposed
11 // standard may be subject to third party patent rights, including
13 // no representations to users of the standard as to the existence
21 // reliance on the standard or incorporation thereof in its product,
23 // any party implementing such standard, whether such implementation
26 // a standard is withdrawn or modified after publication, and shall be
28 // standard from any and all claims of infringement by a patent owner
/openbmc/openbmc/meta-openembedded/meta-networking/licenses/
H A DDMTF10 // Implementation of certain elements of this standard or proposed
11 // standard may be subject to third party patent rights, including
13 // no representations to users of the standard as to the existence
21 // reliance on the standard or incorporation thereof in its product,
23 // any party implementing such standard, whether such implementation
26 // a standard is withdrawn or modified after publication, and shall be
28 // standard from any and all claims of infringement by a patent owner

12345678910>>...172