| /openbmc/linux/tools/testing/selftests/openat2/ |
| D | openat2_test.c | |
| D | resolve_test.c | |
| D | helpers.c | |
| D | helpers.h | |
| /openbmc/linux/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-ksm | |
| D | sysfs-kernel-slab | |
| /openbmc/openbmc/poky/meta/lib/oeqa/core/tests/cases/ |
| H A D | depends.py | 13 self.assertTrue(True, msg='How is this possible?')
17 self.assertTrue(True, msg='How is this possible?')
21 self.assertTrue(True, msg='How is this possible?')
25 self.assertTrue(True, msg='How is this possible?')
29 self.assertTrue(True, msg='How is this possible?')
33 self.assertTrue(True, msg='How is this possible?')
37 self.assertTrue(True, msg='How is this possible?')
41 self.assertTrue(True, msg='How is this possible?')
|
| H A D | oetag.py | 13 self.assertTrue(True, msg='How is this possible?')
17 self.assertTrue(True, msg='How is this possible?')
21 self.assertTrue(True, msg='How is this possible?')
24 self.assertTrue(True, msg='How is this possible?')
30 self.assertTrue(True, msg='How is this possible?')
34 self.assertTrue(True, msg='How is this possible?')
37 self.assertTrue(True, msg='How is this possible?')
|
| H A D | timeout.py | 17 self.assertTrue(True, msg='How is this possible?')
22 self.assertTrue(True, msg='How is this possible?')
31 self.assertTrue(False, msg='How is this possible?')
|
| /openbmc/docs/development/ |
| H A D | README.md | 9 Start here. This shows how to setup an OpenBMC development environment using
10 its bitbake build process and how to start the software emulator, QEMU.
14 This shows how to use the yocto tool, devtool, to extract an OpenBMC source
19 This shows how to modify the phosphor-webui web application and test your
24 This shows how to setup your environment to utilize Gerrit for submitting
|
| /openbmc/openbmc/poky/documentation/ |
| H A D | what-i-wish-id-known.rst | 19 understanding of how the build process works, you'll find yourself trying to
26 because of how git works. If you download the tarball instead, you will need
83 #. **Understand the basic concepts of how the build system works: the workflow:**
85 pinpoint where trouble is occurring and how the build is breaking. The
101 .. image:: figures/yp-how-it-works-new-diagram.png
104 #. **Know that you can generate a dependency graph and learn how to do it:**
110 dependency graphs and how to generate them in the
114 #. **Here's how you decode "magic" folder names in tmp/work:**
130 :doc:`brief-yoctoprojectqs/index` show how to create an image
137 Shell` for information on how to build and run a specific task using
[all …]
|
| /openbmc/openbmc/poky/documentation/kernel-dev/ |
| H A D | faq.rst | 12 How do I use my own Linux kernel ``.config`` file?
19 How do I create configuration fragments?
26 How do I use my own Linux kernel sources?
33 How do I install/not-install the kernel image on the root filesystem?
43 Yocto Project Development Tasks Manual for information on how to use an
46 How do I install a specific kernel module?
67 How do I change the Linux kernel command line?
|
| /openbmc/linux/security/smack/ |
| D | Kconfig | |
| /openbmc/u-boot/doc/ |
| H A D | README.sata | 8 1.0 How to read the SATA hard disk's information?
17 1.1 How to raw write the kernel, file system, dtb to a SATA hard disk?
34 1.2 How to raw read the kernel, file system, dtb from a SATA hard disk?
48 1.3 How to load an image from an ext2 file system in U-Boot?
|
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team.md | 21 the problem, its severity, and how to protect your systems that were built on
31 [How to privately report a security vulnerability](./how-to-report-a-security-vulnerability.md)
32 web page explains how OpenBMC community members can report a security
|
| /openbmc/qemu/qapi/ |
| H A D | compat.json | 54 # @deprecated-input: how to handle deprecated input (default 'accept')
56 # @deprecated-output: how to handle deprecated output (default
59 # @unstable-input: how to handle unstable input (default 'accept')
62 # @unstable-output: how to handle unstable output (default 'accept')
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 3 ## How to report a security vulnerability
5 This describes how you can report an OpenBMC security vulnerability privately to
21 - how to reproduce the problem
36 - Coordinate announcement details with you, such as timing or how you want to be
|
| /openbmc/linux/include/linux/ |
| D | map_benchmark.h | |
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | intro.rst | 20 example, procedures that show you how to set up a build host and work
23 - Procedures that show you how to submit changes to the Yocto Project.
35 instructions on how to install an SDK, which is used to develop
43 example, exhaustive information on how to use the Git version
|
| /openbmc/bmcweb/ |
| H A D | OWNERS | 5 # - Have a solid understanding of the bmcweb core code, and how it's used.
19 # how it interacts with OpenBMC, and how the bmcweb implementation compares to
20 # other Redfish instances and how changes effect compatibility with other
56 # how they differ from "normal" client-based use cases, as well as an
|
| /openbmc/linux/Documentation/driver-api/virtio/ |
| D | virtio.rst | |
| /openbmc/docs/designs/ |
| H A D | design-template.md | 14 requires you to explore how each might be implemented.
83 implementation. Roughly estimate relevant details. How big is the data? What are
84 the transaction rates? Bandwidth? How will the feature be configured, and what
117 How will this be tested? How will this feature impact CI testing?
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | resources.rst | 24 submitting patches through email. For information on how to do both as
25 well as information on how to identify the maintainer for each area of
45 For a general procedure and guidelines on how to use Bugzilla to submit a bug
137 - :doc:`/dev-manual/index`: This manual is a "how-to" guide
152 how to work with Linux Yocto kernels as well as provides a bit of
170 introduces and describes how to set up and use Toaster. Toaster is an
193 Information on how to get set up and use the Yocto Project
|
| /openbmc/linux/Documentation/bpf/ |
| D | map_array.rst | |
| /openbmc/qemu/docs/system/ |
| H A D | introduction.rst | 143 - Backends are how QEMU deals with the guest's data, for example
144 how a block device is stored, how network devices see the
145 network or how a serial device is directed to the outside world.
147 - How the system is displayed, how it is managed and controlled or
150 - How the system boots, via firmware or direct kernel boot.
|