| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | CERN-OHL-1.2 | 11 …Documentation” means schematic diagrams, designs, circuit or circuit board layouts, mechanical dra…
12 …Documentation Location” means a location where the Licensor has placed Documentation, and which he…
13 …er an entire, or any part of a, device built using the Documentation or the modified Documentation.
15 …hat creates or modifies Documentation and subsequently communicates to the public and/ or distribu…
20 …ng, modification, communication to the public and distribution of the Documentation, and the manuf…
22 …mable devices which may be used in conjunction with the Documentation, the modified Documentation …
24 3. Copying, modification, communication to the public and distribution of the Documentation
25 …Documentation Location, and all notices that refer to this Licence and to the disclaimer of warran…
26 …copy, communicate to the public and distribute verbatim copies of the Documentation, in any medium…
27 …Documentation or any portion thereof provided that upon modification of the Documentation, the Lic…
[all …]
|
| H A D | CERN-OHL-1.1 | 11 …Documentation” means schematic diagrams, designs, circuit or circuit board layouts, mechanical dra…
12 …er an entire, or any part of a, device built using the Documentation or the modified Documentation.
14 …hat creates or modifies Documentation and subsequently communicates to the public and/ or distribu…
18 …ng, modification, communication to the public and distribution of the Documentation, and the manuf…
20 …mable devices which may be used in conjunction with the Documentation, the modified Documentation …
22 3. Copying, modification, communication to the public and distribution of the Documentation
23 …uded in the Documentation. He shall include a copy thereof in every copy of the documentation or, …
24 …copy, communicate to the public and distribute verbatim copies of the Documentation, in any medium…
25 …may modify the Documentation or any portion thereof. The Licensee may communicate to the public an…
27 b. cause the modified Documentation to carry prominent notices stating that the Licensee has modifi…
[all …]
|
| H A D | TAPR-OHL-1.0 | 11 "documentation" and things created from it are called "products."
22 copy, modify, and distribute documentation, and to make, use and
23 distribute products based on that documentation.
26 copyright protects documentation from unauthorized copying, modification,
28 or use a product based on that documentation. For better or worse, patents
43 * You may modify the documentation and make products based upon it.
47 * You may distribute unmodified documentation, but you must include the
51 include the documentation on which the product is based, or make it
55 * You may distribute modified documentation or products based on it, if
60 * Attempt to send the modified documentation by email to any of the
[all …]
|
| H A D | OML | 1 …documentation (the "Documentation") are copyrighted by Open Market, Inc ("Open Market"). The follo…
3 …Documentation for any purpose, provided that existing copyright notices are retained in all copies…
5 …DOCUMENTATION, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTI…
|
| /openbmc/linux/Documentation/doc-guide/ |
| H A D | contributing.rst | 3 How to help improve kernel documentation
6 Documentation is an important part of any software-development project.
7 Good documentation helps to bring new developers in and helps established
8 developers work more effectively. Without top-quality documentation, a lot
12 Unfortunately, the kernel's documentation currently falls far short of what
16 Kernel documentation improvements can be made by developers at a variety of
19 documentation maintainer's list of tasks that most urgently need to be
22 The documentation TODO list
26 documentation to where it should be. This list contains a number of
28 improve the documentation, please do not hold back!
[all …]
|
| H A D | sphinx.rst | 4 Using Sphinx for kernel documentation
7 The Linux kernel uses `Sphinx`_ to generate pretty documentation from
8 `reStructuredText`_ files under ``Documentation``. To build the documentation in
10 documentation is placed in ``Documentation/output``.
16 documentation comments, or kernel-doc comments, from source files. Usually these
21 Finally, there are thousands of plain text documentation files scattered around
22 ``Documentation``. Some of these will likely be converted to reStructuredText
30 The ReST markups currently used by the Documentation/ files are meant to be
38 on your machine would cause the documentation build to break.
55 (sphinx_2.4.4) $ pip install -r Documentation/sphinx/requirements.txt
[all …]
|
| H A D | maintainer-profile.rst | 3 Documentation subsystem maintainer entry profile
6 The documentation "subsystem" is the central coordinating point for the
7 kernel's documentation and associated infrastructure. It covers the
8 hierarchy under Documentation/ (with the exception of
9 Documentation/devicetree), various utilities under scripts/ and, at least
14 of portions of Documentation/, and many more freely apply changes there
15 when it is convenient. Beyond that, much of the kernel's documentation is
19 The mailing list for documentation is linux-doc@vger.kernel.org. Patches
25 When making documentation changes, you should actually build the
26 documentation and ensure that no new errors or warnings have been
[all …]
|
| /openbmc/openbmc-test-automation/redfish/managers/ |
| H A D | test_bmc_network_conf.robot | 2 Documentation Network interface configuration and verification keyword
59 [Documentation] Get IP Address And Verify.
67 [Documentation] Get Netmask And Verify.
75 [Documentation] Get gateway and verify it's existence on the BMC.
83 [Documentation] Get MAC address and verify it's existence on the BMC.
94 [Documentation] Verify all configured IP and netmask on BMC.
103 [Documentation] Get hostname via Redfish and verify.
111 [Documentation] Configure hostname via Redfish and verify.
126 [Documentation] Configure invalid hostname via Redfish and verify.
134 [Documentation] Configure empty hostname and verify if localHost is assigned.
[all …]
|
| H A D | test_certificate.robot | 2 Documentation Test certificate in OpenBMC. keyword
26 [Documentation] Verify server certificate replace.
38 [Documentation] Verify client certificate replace.
50 [Documentation] Verify CA certificate replace.
60 [Documentation] Verify client certificate install.
72 [Documentation] Verify CA certificate install.
82 [Documentation] Verify maximum CA certificate install.
101 [Documentation] Verify error while uploading same CA certificate two times.
120 [Documentation] Verify server certificate via openssl command.
139 [Documentation] Verify CSR generation for server certificate.
[all …]
|
| /openbmc/openbmc-test-automation/openpower/ |
| H A D | test_bmc_devicetree.robot | 2 Documentation This suite is for Verifying BMC device tree. keyword
17 [Documentation] Verify if the BMC Model is populated in the device tree.
26 [Documentation] Verify if the BMC compatible property is populated.
35 [Documentation] Verify if the BMC CPU name property is populated.
44 [Documentation] Verify if the BMC CPU compatible property is populated.
53 [Documentation] Verify if the BMC Memory name property is populated.
62 [Documentation] Verify if the BMC Memory Device Type property is
72 [Documentation] Verify if the BMC FSI name property is populated.
81 [Documentation] Verify if the BMC FSI compatible property is populated.
90 [Documentation] Verify if the BMC GPIO-FSI name property is populated.
[all …]
|
| /openbmc/openbmc-test-automation/gui/gui_test/overview_menu/ |
| H A D | test_overview_menu.robot | 3 Documentation Test OpenBMC GUI "Overview" menu. keyword
40 [Documentation] Verify existence of all sections in Overview page.
54 [Documentation] Verify values under network information section.
68 [Documentation] Verify values under server information section in overview page.
89 [Documentation] Verify BMC information section in overview page.
97 …[Documentation] Verify navigation to network setting page after clicking the button in overview p…
105 [Documentation] Verify event under critical event logs section in case of any event.
119 [Documentation] Verify event under warning event logs section in case of any event.
137 [Documentation] Verify view more event log button in overview page.
147 [Documentation] Click host console button and verify page navigation to host console page.
[all …]
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | README | 1 documentation
4 This is the directory that contains the Yocto Project documentation. The Yocto
6 instances of the "documentation" directory. You should understand each of
9 poky/documentation - The directory within the poky Git repository containing
11 poky Git repository, the documentation directory
18 yocto-docs/documentation - The Git repository for the Yocto Project manuals.
21 Yocto Project documentation, you should set up
58 This file defines variables used for documentation production. The variables
64 This file specifies some rules to follow when contributing to the documentation.
75 The Yocto Project documentation was migrated from the original DocBook
[all …]
|
| /openbmc/openbmc/poky/bitbake/doc/ |
| H A D | README | 1 Documentation
4 This is the directory that contains the BitBake documentation.
16 go to https://www.openembedded.org/wiki/Documentation.
21 The BitBake documentation was migrated from the original DocBook
22 format to Sphinx based documentation for the Yocto Project 3.2
26 for developers willing to contribute to the BitBake documentation can
27 be found in the Yocto Project Documentation README file:
29 https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/tree/documentation/README
31 How to build the Yocto Project documentation
36 documentation with Python3.
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/dev-tools/ |
| H A D | testing-overview.rst | 5 :Original: Documentation/dev-tools/testing-overview.rst
31 （Documentation/dev-tools/testing-overview.rst）辅助阅读。
34 KUnit（Documentation/dev-tools/kunit/index.rst）是用于“白箱”测
48 Documentation/dev-tools/kunit/style.rst
50 kselftest（Documentation/dev-tools/kselftest.rst），相对来说，大量用
73 Documentation/translations/zh_CN/dev-tools/gcov.rst 是GCC的覆盖率测试
78 Documentation/dev-tools/kcov.rst 是能够构建在内核之中，用于在每个任务
92 Documentation/dev-tools/kmemleak.rst
94 Documentation/dev-tools/kasan.rst
96 Documentation/dev-tools/ubsan.rst
[all …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | docs.rst | 3 QEMU Documentation
6 QEMU's documentation is written in reStructuredText format and
7 built using the Sphinx documentation generator. We generate both
8 the HTML manual and the manpages from the some documentation sources.
13 The documentation for QEMU command line options and Human Monitor Protocol
20 to be included in the HTML or manpage documentation
24 put into the documentation. A few special directives are recognised;
29 nor the documentation output.
32 are put into the documentation verbatim, and discarded from the C output.
34 referenced from elsewhere in the rST documentation. The label will take
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | state_manager.robot | 17 [Documentation] Initiate host power on.
35 [Documentation] Initiate host power off.
56 [Documentation] Wait for power off state.
64 [Documentation] Do a hard power off.
82 [Documentation] Initiate host reboot via REST.
99 [Documentation] Check if host state is "Running".
109 [Documentation] Return the state of the host as a string.
125 [Documentation] Check OS status.
144 [Documentation] Check if host state is "Off".
155 [Documentation] Checks if host rebooted.
[all …]
|
| H A D | utils.robot | 3 Documentation Utilities for Robot keywords that use REST. keyword
48 [Documentation] Verify ping and rest authentication.
66 [Documentation] Verify ping, SSH and redfish authentication.
81 [Documentation] Wait for Host to be online. Checks every X seconds
100 [Documentation] Removes all the active session objects
105 [Documentation] Inject host watchdog timeout error via REST.
132 [Documentation] Login to OS Host and return the Login response code.
149 [Documentation] Initiate an auto reboot.
162 [Documentation] Initiate an OS reboot.
181 [Documentation] Initiate an OS reboot.
[all …]
|
| /openbmc/openbmc-test-automation/redfish/account_service/ |
| H A D | test_ldap_configuration.robot | 2 Documentation Test Redfish LDAP user configuration. keyword
27 [Documentation] Verify that LDAP configuration created.
39 [Documentation] Verify that LDAP is disabled and that LDAP user cannot
59 [Documentation] Verify that LDAP Login with ServiceEnabled.
73 [Documentation] Verify that LDAP Login with right AuthenticationType.
85 [Documentation] Verify that invalid AuthenticationType is not updated.
95 [Documentation] Verify LDAP Login with right LDAP URL.
102 [Documentation] Verify that LDAP Login fails with invalid LDAP URL.
110 [Documentation] Verify that LDAP configuration is available.
119 [Documentation] Verify that LDAP user able to login into BMC.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/licenses/ |
| H A D | OML | 2 "Software") and its documentation (the "Documentation") are
4 apply to all files associated with the Software and Documentation
8 this Software and the Documentation for any purpose, provided that
12 authorized uses. Modifications to this Software and Documentation may
15 Documentation have new licensing terms, the new terms must be clearly
19 SOFTWARE OR THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION ANY
23 DOCUMENTATION, INCLUDING, WITHOUT LIMITATION, ANY INDIRECT, SPECIAL OR
26 SUCH DAMAGES. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS".
28 OTHERWISE ARISING OUT OF THIS SOFTWARE OR THE DOCUMENTATION.
|
| /openbmc/openbmc-test-automation/openpower/ext_interfaces/ |
| H A D | test_vmi.robot | 3 Documentation VMI static/dynamic IP config tests. keyword
44 [Documentation] Verify all VMI ethernet interfaces.
51 [Documentation] Verify existing VMI network interface details.
67 [Documentation] Delete existing static VMI IP address.
77 [Documentation] Verify user cannot delete readonly property IPv4Addresses.
87 [Documentation] Assign static IPv4 address to VMI.
100 [Documentation] Add multiple IP addresses on VMI interface and verify.
114 [Documentation] Modify IP addresses on VMI interface and verify.
125 [Documentation] Switch between IP origins on VMI and verify details.
133 [Documentation] Verif
[all...] |
| /openbmc/openbmc-test-automation/gui/test/server_control/ |
| H A D | test_obmc_gui_server_power_operations.robot | 3 Documentation Test OpenBMC GUI "Server power operation" sub-menu of keyword
24 [Documentation] Verify system state at power off.
32 [Documentation] Verify BMC IP in server power operation page.
40 [Documentation] Verify that shutdown button is not present at power Off.
48 [Documentation] Verify that reboot button is not present at power Off.
56 [Documentation] Verify presence of "Power On" button at power off.
64 [Documentation] Verify system state at power on.
72 [Documentation] Verify that shutdown button is present at power on.
80 [Documentation] Verify that reboot button is present at power on.
88 [Documentation] Verify existence of all sections in host os boot settings.
[all …]
|
| /openbmc/openbmc-test-automation/gui/test/gui_header/ |
| H A D | test_obmc_gui_server_health.robot | 3 Documentation Test Open BMC GUI server health under GUI Header. keyword
28 [Documentation] Check that "Event Log" text appears by clicking server
37 [Documentation] Check that the "event log" filters appears by clicking
49 [Documentation] Check that the "drop down" button of user timezone appears
62 [Documentation] Check that the "event search element is available with
73 [Documentation] Check that the "filter by date" elements are available and
83 [Documentation] Check that the "filter by event status" element appears.
96 [Documentation] Check that "event action bar" element appears.
106 [Documentation] Check that "event check box" element appears and on click
121 [Documentation] Check that "number of events" element appears and value is
[all …]
|
| /openbmc/linux/ |
| H A D | MAINTAINERS | 29 or a URI. See Documentation/maintainer/maintainer-entry-profile.rst
74 F: Documentation/networking/device_drivers/ethernet/3com/vortex.rst
101 F: Documentation/networking/6lowpan.rst
119 F: Documentation/driver-api/80211/cfg80211.rst
120 F: Documentation/networking/regulatory.rst
161 F: Documentation/filesystems/9p.rst
188 F: Documentation/scsi/aacraid.rst
193 F: Documentation/devicetree/bindings/power/supply/*ab8500*
285 F: Documentation/ABI/testing/configfs-acpi
286 F: Documentation/AB
[all...] |
| /openbmc/linux/Documentation/translations/zh_CN/process/ |
| H A D | submit-checklist.rst | 3 :Original: Documentation/process/submit-checklist.rst
16 这些都是在 Documentation/translations/zh_CN/process/submitting-patches.rst
39 5) 按 Documentation/translations/zh_CN/process/coding-style.rst 所述检查您的
45 它们符合 ``Documentation/kbuild/kconfig-language.rst`` 菜单属性：默认值中
54 （参见 Documentation/translations/zh_CN/dev-tools/sparse.rst ）
78 15) 所有新的 ``/proc`` 条目都记录在 ``Documentation/``
81 Documentation/admin-guide/kernel-parameters.rst 中。
85 18) 所有新的用户空间接口都记录在 ``Documentation/ABI/`` 中。有关详细信息，
86 请参阅 ``Documentation/ABI/README`` 。更改用户空间接口的补丁应该抄送
89 19) 已通过至少注入slab和page分配失败进行检查。请参阅 ``Documentation/fault-injection/`` 。
[all …]
|
| /openbmc/openbmc-test-automation/gui/test/server_overview/ |
| H A D | test_obmc_gui_server_overview.robot | 2 Documentation This test suite will validate the "OpenBMC ASMI Menu -> keyword
26 [Documentation] Verify console page on clicking serial over lan console button
34 [Documentation] Verify display of title text from "Server Overview"
43 [Documentation] Verify existence of text "Server information".
51 [Documentation] Verify existence of text "BMC information".
59 [Documentation] Verify existence of text "Power Consumption".
67 [Documentation] Verify the text display.
75 [Documentation] Will open the "High Priority Events".
85 [Documentation] Will open the serial over the lan command prompt window.
97 [Documentation] Get BMC hostname, version, IP, and MAC address via GUI and verify using REST
[all …]
|