Home
last modified time | relevance | path

Searched full:described (Results 1 – 25 of 1079) sorted by relevance

12345678910>>...44

/openbmc/u-boot/doc/device-tree-bindings/net/
H A Dethernet.txt16 - phy-connection-type: the same as "phy-mode" property but described in ePAPR;
18 device; this property is described in ePAPR and so preferred;
25 They are described in the phy.txt file in this same directory.
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A Dredfish-error.v1_0_2.json10 …"longDescription": "The Redfish Specification-described type shall contain an error payload from a…
15 …"longDescription": "This property, as described by the Redfish Specification, shall contain proper…
26 …"longDescription": "The Redfish Specification-described type shall contain properties that describ…
H A DMessage.v1_3_0.json9 …"This type shall contain a message that the Redfish service returns, as described in the Redfish S…
56 …erties contained in this object shall conform to the Redfish Specification-described requirements."
59 "description": "A set of properties described by the message.",
63 …ain an array of RFC6901-defined JSON pointers indicating the properties described by the message, …
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A Dredfish-error.v1_0_2.json10 …"longDescription": "The Redfish Specification-described type shall contain an error payload from a…
15 …"longDescription": "This property, as described by the Redfish Specification, shall contain proper…
26 …"longDescription": "The Redfish Specification-described type shall contain properties that describ…
H A DMessage.v1_3_0.json9 …"This type shall contain a message that the Redfish service returns, as described in the Redfish S…
56 …erties contained in this object shall conform to the Redfish Specification-described requirements."
59 "description": "A set of properties described by the message.",
63 …ain an array of RFC6901-defined JSON pointers indicating the properties described by the message, …
H A DExternalAccountProvider.v1_8_1.json131 …erties contained in this object shall conform to the Redfish Specification-described requirements."
283 …rties that this object contains shall conform to the Redfish Specification-described requirements."
480 …erties contained in this object shall conform to the Redfish Specification-described requirements."
493 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
512 …erties contained in this object shall conform to the Redfish Specification-described requirements."
591 …rties contained in this object shall conform to the Redfish Specification-described requirements.",
692 …erties contained in this object shall conform to the Redfish Specification-described requirements."
731 …"ASCII": "This value shall indicate the ASCII Login flow as described under section 5.4.2 of RFC89…
732 …"CHAP": "This value shall indicate the CHAP Login flow as described under section 5.4.2 of RFC8907…
733 …"MSCHAPv1": "This value shall indicate the MS-CHAP v1 Login flow as described under section 5.4.2 …
[all …]
H A DSimpleStorage.v1_3_2.json86 …mber. The resource values shall conform with the Redfish Specification-described requirements. T…
93 …erties contained in this object shall conform to the Redfish Specification-described requirements."
109 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
135 …erties contained in this object shall conform to the Redfish Specification-described requirements."
241 …rties that this object contains shall conform to the Redfish Specification-described requirements."
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/libsombok3/
H A Dlibsombok3_2.4.0.bb2 DESCRIPTION = "Sombok library package performs Line Breaking Algorithm described in \
6 Cluster segmentation described in Annex #29 (UAX #29)."
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DOPL-1.020 … 1.8. "License" means this document and the corresponding addendum described in section 6.4 below.
28 …1.10. "Original Code" means Source Code of computer software code which is described in the Source…
52 …er, You may include an additional document offering the additional rights described in Section 3.5.
60 …you obtain such knowledge after You make Your Modification available as described in Section 3.2, …
64 …e Modification(s), You may add your name as a Contributor to the notice described in Exhibit A. If…
72 …e code they affect. Such description must be included in the LEGAL file described in Section 3.4 a…
84 …described in section 6.4, (which you may only do in order to apply it to code which is not already…
124 …y left blank. The contents of this section are found in the corresponding addendum described above.
132 Text for this Exhibit A is found in the corresponding addendum, described in section 6.4 above, tex…
136 Text for this Exhibit B is found in the corresponding addendum, described in section 6.4 above, tex…
H A DErlPL-1.146 which is described in the Source Code notice required by Exhibit A as
116 the additional rights described in Section 3.5.
150 make Your Modification available as described in Section 3.2, You
168 Contributor to the notice described in Exhibit A. If it is not
217 file described in Section 3.4 and must be included with all
H A DSugarCRM-153 described in the Source Code notice required by Exhibit A as Original Code, and
139 offering the additional rights described in Section 3.5.
170 available as described in Section 3.2, Contributor shall promptly modify the
192 to the notice described in Exhibit A. You must also duplicate this License in
235 affect. Such description must be included in the LEGAL file described in
265 Original Code or Contributor in the notice described in Exhibit A shall not of
376 Initial Developer in the file described in Exhibit A.
404 These additional terms described in this SugarCRM Public License –
H A DSugarCRM-1.1.334 1.10. ``Original Code`` means Source Code of computer software code which is described in the Sourc…
63 …er, You may include an additional document offering the additional rights described in Section 3.5.
73 …utor obtains such knowledge after the Modification is made available as described in Section 3.2, …
80 …re Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. Yo…
89 …e code they affect. Such description must be included in the LEGAL file described in Section 3.4 a…
101 …me of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A sha…
131 …lternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A.
154 These additional terms described in this SugarCRM Public License – Additional Terms shall app…
H A DNPL-1.017 …1.10. ``Original Code'' means Source Code of computer software code which is described in the Sour…
33 …er, You may include an additional document offering the additional rights described in Section 3.5.
38 …you obtain such knowledge after You make Your Modification available as described in Section 3.2, …
41 …e Modification(s), You may add your name as a Contributor to the notice described in Exhibit A. If…
46 …e code they affect. Such description must be included in the LEGAL file described in Section 3.4 a…
55 …me of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A sha…
84 …I. Effect. These additional terms described in this Netscape Public License -- Amendments shall a…
/openbmc/service-config-manager/
H A DREADME.md4 described by the [service management D-Bus interfaces][].
18 Implementation details are described in the [D-Bus interface README].
/openbmc/u-boot/doc/device-tree-bindings/pinctrl/
H A Drockchip,pinctrl.txt37 Use rockchip,grf and rockchip,pmu described above instead.
50 cells should use the standard two-cell scheme described in
56 rockchip,pmu described above instead
63 to use, as described in pinctrl-bindings.txt in this directory.
/openbmc/u-boot/drivers/misc/
H A Dihs_fpga.h36 * @member: Name of member (described by ihs_fpga_regs) to set
45 * @member: Name of member (described by ihs_fpga_regs) to get
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/
H A DTriggerManager.interface.yaml44 Contains array of numeric thresholds that are described in
49 Contains array of discrete thresholds that are described in
/openbmc/u-boot/board/ti/ks2_evm/
H A DREADME137 1. Start CCS and run U-Boot as described above.
141 through CCS as described in step 2 of "Load and Run U-Boot on K2HK/K2E/K2L
143 4. Free Run the target as described earlier (step 4) to get U-Boot prompt
158 1. Start CCS and run U-Boot as described above.
162 through CCS as described in step 2 of "Load and Run U-Boot on K2HK EVM
164 4. Free Run the target as described earlier (step 4) to get U-Boot prompt
/openbmc/openbmc/poky/documentation/
H A Dstandards.md16 conventions described below still apply.
89 Wikipedia, or on their own project pages if they are not described on
104 This assumes that `VARIABLE` is described either
109 If it is not described yet, the variable should be added to the
/openbmc/qemu/docs/specs/
H A Dppc-spapr-hotplug.rst33 for hot plugged resources described under :ref:`guest-host-interface`.
35 The array properties are described below. Each entry/element in an array
328 The format for these EPOW-signalled events is described below under
331 also described below under :ref:`hot-plug-unplug-event-structure`, and so are
339 ``ibm,architecture-vec-5`` option vector structure (as described by [LoPAR]_,
344 guest's device tree using the standard format described in [LoPAR]_,
450 described here.
487 ``ibm,associativity-lookup-arrays`` property described earlier. This is used
507 ``ibm,associativity-lookup-arrays`` property described earlier. This
/openbmc/docs/designs/
H A Dvirtual-media.md83 Asynchronous responses will be described later on in appropriate sections.
117 described by [RFC6455](HTTPS://tools.ietf.org/html/rfc6455). Since WSS upgrade,
123 being defined in configuration file described in next chapter.
182 and described in details in next chapter.
238 Members in collection will be defined based on configuration file described in
297 | InsertMedia | N/A | action as described by DMTF spec | Action can return Task obj…
300 | ConnectedVia | "Applet" | as described by DMTF spec | applies only for connected…
302 | TransferProtocolType | "OEM" | as described by DMTF spec | …
359 representation of configuration file described above
H A Dentity-manager.md3 Design is described in the
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DRedfishError_v1.xml30 …<Annotation Term="OData.LongDescription" String="The Redfish Specification-described type shall co…
33 …<Annotation Term="OData.LongDescription" String="This property, as described by the Redfish Specif…
41 …<Annotation Term="OData.LongDescription" String="The Redfish Specification-described type shall co…
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DRedfishError_v1.xml30 …<Annotation Term="OData.LongDescription" String="The Redfish Specification-described type shall co…
33 …<Annotation Term="OData.LongDescription" String="This property, as described by the Redfish Specif…
41 …<Annotation Term="OData.LongDescription" String="The Redfish Specification-described type shall co…
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/VirtualMedia/
H A DREADME.md3 All exposed objects, their paths and interfaces are described in

12345678910>>...44