| /openbmc/openbmc/meta-openembedded/meta-oe/classes/ |
| H A D | socorro-syms.bbclass | 151 # won't be accessible by Socorro.
|
| /openbmc/openbmc-tools/openbmctool/ |
| H A D | README.md | 195 otherwise BMC would not be accessible.
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | scsi-changer.rst | 37 import/export the same as above, but is accessible from outside,
|
| /openbmc/linux/Documentation/riscv/ |
| H A D | boot.rst | 148 devicetree. This ensures that the devicetree remains accessible by both virtual
|
| /openbmc/linux/arch/arm/boot/dts/marvell/ |
| H A D | armada-385-clearfog-gtr.dtsi | 226 * The PCIe units are accessible through
|
| /openbmc/linux/arch/um/ |
| H A D | Kconfig | 222 After enabling this option, two modes are accessible at runtime
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | debugging-via-ohci1394.rst | 125 On the debug host, make sure that /dev/fw* is accessible,
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | interlaken-lac.txt | 33 latter, and includes certain registers that should not be accessible to
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | armada-388-clearfog.dts | 130 * The two PCIe units are accessible through
|
| H A D | rk3188.dtsi | 243 * not accessible through pinctrl. Also they should've
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 164 parameters that are accessible at /sys/module/acpi/parameters/:
|
| /openbmc/linux/Documentation/driver-api/surface_aggregator/clients/ |
| H A D | cdev.rst | 17 The provided interface is accessible through the ``/dev/surface/aggregator``
|
| /openbmc/qemu/docs/system/riscv/ |
| H A D | virt.rst | 221 tree and should be accessible from the guest software.
|
| /openbmc/qemu/docs/system/ |
| H A D | introduction.rst | 185 user-mode networking isn't directly accessible from the outside world
|
| H A D | security.rst | 172 QEMU and as such should only be made accessible to a trusted management
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | perf-script-perl.txt | 191 common, but need to be made accessible to user scripts nonetheless.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | unicode.rst | 178 The ConScript Unicode Registry is accessible at:
|
| H A D | initrd.rst | 48 be accessible.
112 accessible if the following device has been created::
|
| /openbmc/linux/arch/arm/boot/dts/ti/omap/ |
| H A D | omap3-n950-n9.dtsi | 344 /* RNG not directly accessible on N950/N9. */
|
| /openbmc/u-boot/scripts/ |
| H A D | spelling.txt | 24 accessable||accessible
37 acessable||accessible
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | PDDL-1.0 | 16 …erms because they have nothing left to license. Doing so creates truly accessible data to build ri…
36 …on of Data arranged in a systematic or methodical way and individually accessible by electronic or…
|
| /openbmc/linux/Documentation/crypto/ |
| H A D | userspace-if.rst | 31 The kernel crypto API is accessible from user space. Currently, the
32 following ciphers are accessible:
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | README.txt | 304 private data (accessible through dev_get_priv(dev) once the driver has
312 The U_BOOT_DRIVER macro creates a data structure accessible from C,
662 is allocated for the device and zeroed. It will be accessible as
671 zeroed. It will be accessible as dev->platdata.
734 all of the above structures are accessible. The device appears in the
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | vt1211.rst | 187 thermal thresholds are accessible via pwm[1-2]_auto_point[1-4]_temp. Note
|
| /openbmc/linux/Documentation/sound/cards/ |
| H A D | hdspm.rst | 115 Note: Within the windows-driver the latency is accessible of a
|