Home
last modified time | relevance | path

Searched +full:directory +full:- +full:based (Results 1 – 25 of 1150) sorted by relevance

12345678910>>...46

/openbmc/linux/Documentation/admin-guide/mm/damon/
H A Dusage.rst1 .. SPDX-License-Identifier: GPL-2.0
9 - *DAMON user space tool.*
11 system administrators who want a just-working human-friendly interface.
12 Using this, users can use the DAMON’s major features in a human-friendly way.
16 - *sysfs interface.*
23 - *debugfs interface. (DEPRECATED!)*
28 linux-mm@kvack.org.
29 - *Kernel Space Programming Interface.*
42 creates multiple directories and files under its sysfs directory,
44 from the files under the directory.
[all …]
/openbmc/openbmc/poky/documentation/sdk-manual/
H A Dworking-projects.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 You can use the SDK toolchain directly with Makefile and Autotools-based
10 Autotools-Based Projects
13 Once you have a suitable :ref:`sdk-manual/intro:the cross-development toolchain`
15 Autotools-based <GNU_Build_System>` workflow, which is outside of the
20 .. image:: figures/sdk-autotools-flow.png
24 Follow these steps to create a simple Autotools-based "Hello World"
34 #. *Create a Working Directory and Populate It:* Create a clean
35 directory for your project and then make that directory your working
41 After setting up the directory, populate it with files needed for the flow.
[all …]
H A Dusing.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
13 For a side-by-side comparison of main features supported for a
15 ":ref:`sdk-manual/intro:introduction`" section.
17 You can use a standard SDK to work on Makefile and Autotools-based
19 ":ref:`sdk-manual/working-projects:using the sdk toolchain directly`" chapter
25 The Standard SDK provides a cross-development toolchain and libraries
34 usage. You can see the directory structure in the
35 ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
44 You can download a tarball installer, which includes the pre-built
46 appropriate :yocto_dl:`toolchain </releases/yocto/yocto-&DISTRO;/toolchain/>` directory within
[all …]
H A Dappendix-obtain.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
11 ":ref:`sdk-manual/extensible:Setting up the Extensible SDK environment directly in a Yocto build`"
14 machine, or a well-functioning sstate cache infrastructure is required:
21 Locating Pre-Built SDK Installers
22 ---------------------------------
24 You can use existing, pre-built toolchains by locating and running an
26 method, you select and download an architecture-specific SDK installer
27 and then run the script to hand-install the toolchain.
29 Follow these steps to locate and hand-install the toolchain:
31 #. *Go to the Installers Directory:* Go to
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/opencv/opencv/
H A D0008-Do-not-embed-build-directory-in-binaries.patch3 Subject: Do not embed build directory in binaries
7 https://salsa.debian.org/science-team/opencv/-/raw/master/debian/patches/0008-Do-not-embed-build-di…
8 Upstream-Status: Backport
9 Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com>
10 ---
11 modules/core/CMakeLists.txt | 10 ------
12 modules/core/include/opencv2/core/private.hpp | 4 +--
13 modules/core/include/opencv2/core/utility.hpp | 4 +--
14 modules/core/src/utils/datafile.cpp | 48 +--------------------------
15 4 files changed, 5 insertions(+), 61 deletions(-)
[all …]
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/
H A DREADME.md1 # phosphor-regulators Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Example](#example)
8 - [Name](#name)
9 - [Contents](#contents)
10 - [Validation](#validation)
11 - [Installation](#installation)
12 - [Loading and Reloading](#loading-and-reloading)
13 - [Testing](#testing)
[all …]
/openbmc/u-boot/doc/device-tree-bindings/net/
H A Daltera_tse.txt1 * Altera Triple-Speed Ethernet MAC driver (TSE)
4 - compatible: Should be "altr,tse-1.0" for legacy SGDMA based TSE, and should
5 be "altr,tse-msgdma-1.0" for the preferred MSGDMA based TSE.
6 - reg: Address and length of the register set for the device. It contains
7 the information of registers in the same order as described by reg-names
8 - reg-names: Should contain the reg names
16 - interrupts: Should contain the TSE interrupts and it's mode.
17 - interrupt-names: Should contain the interrupt names
20 - rx-fifo-depth: MAC receive FIFO buffer depth in bytes
21 - tx-fifo-depth: MAC transmit FIFO buffer depth in bytes
[all …]
/openbmc/openbmc/poky/bitbake/lib/bb/fetch2/
H A Dsftp.py10 supports key based authentication, not password. This class, unlike
11 the SSH fetcher, does not support fetching a directory tree from the
14 http://tools.ietf.org/html/draft-ietf-secsh-scp-sftp-ssh-uri-04
15 https://www.iana.org/assignments/uri-schemes/prov/sftp
16 https://tools.ietf.org/html/draft-ietf-secsh-filexfer-13
20 ~ (tilde) to specify a path relative to your home directory.
22 user's home directory is not supported.) Note that the tilde must
29 A path relative to your home directory.
42 # Based in part on bb.fetch2.wget:
45 # SPDX-License-Identifier: GPL-2.0-only
[all …]
/openbmc/qemu/docs/devel/testing/
H A Dacpi-bits.rst11 acpica bios interpreter (a freely available C based library written by Intel,
13 operating system getting involved in between. Bios-bits has python integration
15 python instead of bash-ish (grub's native scripting language).
32 bios-bits very attractive for testing bioses. More details on the inspiration
41 author's FOSDEM presentation <FOSDEM_>`__ on this bios-bits based test framework.
45 .. _gitlab: https://gitlab.com/qemu-project/biosbits-bits
46 …rg/2024/schedule/event/fosdem-2024-2262-exercising-qemu-generated-acpi-smbios-tables-using-biosbit…
52 Under the directory ``tests/functional/``, ``test_acpi_bits.py`` is a QEMU
61 ├── acpi-bits
62 │ ├── bits-config
[all …]
/openbmc/openbmc/poky/bitbake/lib/toaster/orm/fixtures/
H A DREADME1 # Fixtures directory
6 In this directory we have the fixtures which are loaded the first time you start Toaster.
9 - settings.xml This Contains Toaster wide settings, such as the default values for
12 - poky.xml This is the default release data for supported poky based setup
14 - oe-core.xml This is the default release data for supported oe-core based setups
18 - custom.xml
21 "custom.xml" in this directory. If present it will be loaded into the database.
30 https://docs.djangoproject.com/en/3.2/ref/django-admin/#django-admin-loaddata
/openbmc/phosphor-debug-collector/tools/dreport.d/
H A Ddreport14 -n, —-name <name> Name to be used for the archive.
16 -d, —-dir <directory> Archive directory to copy the compressed report.
17 Default output directory is /tmp
18 -i, —-id <id> Dump identifier to associate with the archive.
21 -t, —-type <type> Data collection type. Valid types are
24 -p, —-path <path> Optional contents to be included in the archive.
25 Valid paths are absolute file path or d-bus path
26 based on type parameter.
27 -Absolute file path for "core" type.
28 -elog d-bus object for "elog" type.
[all …]
/openbmc/linux/drivers/fsi/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
11 FSI - the FRU Support Interface - is a simple bus for low-level
12 access to POWER-based hardware.
17 bool "Create '/dev/fsi' directory for char devices"
21 located under a common /dev/fsi/ directory. Set to N unless your
29 symlinks in /dev/fsi/by-path when this option is enabled.
32 tristate "GPIO-based FSI master"
47 tristate "FSI master based on Aspeed ColdFire coprocessor"
77 This option enables an FSI based SCOM device driver.
83 This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
[all …]
/openbmc/openbmc/poky/meta-poky/conf/templates/default/
H A Dlocal.conf.sample.extended13 # Default to setting automatically based on cpu count
19 #PARALLEL_MAKE ?= "-j 4"
21 # Default to setting automatically based on cpu count
22 #PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
24 # For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
34 # If you want to get an image based on directfb without x11 alter
40 # packages at build time using qemu-native. Disabling it (by setting it to 0)
45 # If GLIBC_SPLIT_LC_PACKAGES is set to a non-zero value, convert
46 # glibc-binary-localedata-XX-YY to be a meta package depending on
47 # glibc-binary-localedata-XX-YY-lc-address and so on. This enables
[all …]
/openbmc/linux/Documentation/admin-guide/
H A DREADME.rst11 --------------
14 Linus Torvalds with assistance from a loosely-knit team of hackers across
17 It has all the features you would expect in a modern fully-fledged Unix,
19 loading, shared copy-on-write executables, proper memory management,
22 It is distributed under the GNU General Public License v2 - see the
26 -----------------------------
28 Although originally developed first for 32-bit x86-based PCs (386 or higher),
31 IBM S/390, MIPS, HP PA-RISC, Intel IA-64, DEC VAX, AMD x86-64 Xtensa, and
34 Linux is easily portable to most general-purpose 32- or 64-bit architectures
40 userspace application - this is called UserMode Linux (UML).
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-devices-soc5 The /sys/devices/ directory contains a sub-directory for each
6 System-on-Chip (SoC) device on a running platform. Information
10 The directory created for each SoC will also house information
19 Read-only attribute common to all SoCs. Contains the SoC machine
26 Read-only attribute common to all SoCs. Contains SoC family name
29 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
57 Read-only attribute supported by most SoCs. Contains the SoC's
64 Read-only attribute supported by most SoCs. In the case of
65 ST-Ericsson's chips this contains the SoC serial number.
67 On many of ARM based silicon with SMCCC v1.2+ compliant firmware
[all …]
H A Dsysfs-kernel-mm-damon6 please refer to Documentation/admin-guide/mm/damon/index.rst.
19 named '0' to 'N-1' under the kdamonds/ directory.
26 based on the current status. Writing 'commit' to this file
31 contents of 'tried_regions' directory of every scheme directory
35 removes contents of the 'tried_regions' directory.
48 'N-1' under the contexts/ directory.
110 named '0' to 'N-1' under the contexts/ directory.
124 context named '0' to 'N-1' under the regions/ directory. In
126 automatically sets the target memory region based on the target
145 directories for controlling each DAMON-based operation scheme
[all …]
/openbmc/u-boot/doc/imx/common/
H A Dmxs.txt1 Booting U-Boot on a MXS processor
4 This document describes the MXS U-Boot port. This document mostly covers topics
8 -----------
14 into the unix command prompt in U-Boot source code root directory.
16 The (=>) introduces a snipped of code that should by typed into U-Boot command
20 --------
23 2) Compiling U-Boot for a MXS based board
24 3) Installation of U-Boot for a MXS based board to SD card
25 4) Installation of U-Boot into NAND flash on a MX28 based board
26 5) Installation of U-Boot into SPI NOR flash on a MX28 based board
[all …]
/openbmc/linux/tools/testing/ktest/examples/
H A DREADME1 This directory contains example configs to use ktest for various tasks.
6 The configs are based off of real working configs but have been modified
10 crosstests.conf - this config shows an example of testing a git repo against
16 test.conf - A generic example of a config. This is based on an actual config
19 kvm.conf - A example of a config that is used to test a virtual guest running
22 snowball.conf - An example config that was used to demo ktest.pl against
25 include/ - The include directory holds default configs that can be
/openbmc/phosphor-power/tools/power-utils/
H A Dupdater.hpp8 * http://www.apache.org/licenses/LICENSE-2.0
47 * @param[in] bus - The sdbusplus DBus bus connection
48 * @param[in] psuInventoryPath - The inventory path of the PSU
49 * @param[in] imageDir - The directory containing the PSU image
69 * @param psuInventoryPath - The PSU inventory path
70 * @param devPath - The PSU device path
71 * @param imageDir - The update image directory
81 * @param doBind - indicate if it's going to bind or unbind the driver
87 * @param present - The present state to set
99 * @return 0 if success, otherwise non-zero
[all …]
/openbmc/openbmc/poky/documentation/overview-manual/
H A Ddevelopment-environment.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
38 Linus Torvalds in 1991. Conversely, a good example of a non-open source
54 system not intended to run the software --- the development host.
60 development host. When you have a Mac or Windows-based system, you can
62 `CROPS <https://github.com/crops/poky-container>`__, which leverages
65 environment that is similar to what you see when using a Linux-based
68 ":ref:`dev-manual/start:setting up to use cross platforms (crops)`"
79 ":ref:`dev-manual/start:setting up a native linux host`"
85 - *Command Lines, BitBake, and Shells:* Traditional development in the
88 BitBake, in a command-line environment from a shell on your
[all …]
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dqemu.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
34 - `QEMU Website <https://wiki.qemu.org/Main_Page>`__\ *:* The official
37 - `Documentation <https://wiki.qemu.org/Manual>`__\ *:* The QEMU user
49 (SDK). See ":ref:`sdk-manual/intro:the qemu emulator`" section in the
56 - If you cloned the ``poky`` repository or you downloaded and
58 environment script (i.e. :ref:`structure-core-script`)::
61 $ source oe-init-build-env
63 - If you installed a cross-toolchain, you can run the script that
65 the initialization script from the default ``poky_sdk`` directory::
67 . poky_sdk/environment-setup-core2-64-poky-linux
[all …]
/openbmc/linux/fs/adfs/
H A Ddir_f.c1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright (C) 1997-1999 Russell King
7 * E and F format directory handling
48 int _off = idx - (_buf << blocksize_bits);\
49 *(u8 *)(bh[_buf]->b_data + _off); \
54 int _off = idx - (_buf << blocksize_bits);\
55 *(__le32 *)(bh[_buf]->b_data + _off); \
60 int _off = _idx - (_buf << blocksize_bits);\
61 (void *)(_bh[_buf]->b_data + _off); \
72 struct buffer_head * const *bh = dir->bh; in adfs_dir_checkbyte()
[all …]
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dfs.rst11 ------------------------------------------------------------------------------
16 The files in this directory can be used to tune and monitor
31 aio-nr & aio-max-nr
32 -------------------
34 ``aio-nr`` shows the current system-wide number of asynchronous io
35 requests. ``aio-max-nr`` allows you to change the maximum value
36 ``aio-nr`` can grow to. If ``aio-nr`` reaches ``aio-nr-max`` then
38 ``aio-max-nr`` does not result in the
39 pre-allocation or re-sizing of any kernel data structures.
42 dentry-state
[all …]
/openbmc/openbmc-test-automation/docs/
H A Dopenbmc_test_tools.md8 $ ipmitool -V
16 [README](https://github.com/open-power/HTX)
21 [README](https://github.com/openbmc/phosphor-logging/blob/master/README.md#remote-logging-via-rsysl…
25 Pre-requisite: A Power Linux system is required.
27 - Obtain the SEL (System Error Log) parser tools:
29 - Go to https://openpower.xyz/job/openpower/job/openpower-op-build/
30 - Click the link for the BMC system of interest (e.g. witherspoon)
31 - Click the "host_fw_debug.tar" link in order to download the tar file.
32 - On your Power Linux system, untar the file with the following command:
35 $ tar -xvf host_fw_debug.tar
[all …]
/openbmc/linux/Documentation/filesystems/
H A Dautofs.rst2 autofs - how it works
8 The goal of autofs is to provide on-demand mounting and race free
17 media with a media-changing robot.
23 filesystem can even be programmatic rather than database-backed,
24 allowing wildcards for example, and can vary based on the user who
31 There also needs to be a user-space program which looks up names
35 required with any user-space program. Subsequent text refers to this
52 directory should be a mount trap is based on a master map. This master
58 mount is considered to be *indirect*), then the root directory is
59 always a regular directory, otherwise it is a mount trap when it is
[all …]

12345678910>>...46