Home
last modified time | relevance | path

Searched refs:requirements (Results 1 – 25 of 631) sorted by relevance

12345678910>>...26

/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/mycroft/files/
H A D0005-pip-requirements-Don-t-install-requirements-with-pip.patch4 Subject: [PATCH 5/7] pip requirements: Don't install requirements with pip
10 requirements.txt | 36 ------------------------------------
11 test-requirements.txt | 7 -------
13 delete mode 100644 requirements.txt
14 delete mode 100644 test-requirements.txt
25 -if ! pip install -r requirements.txt ; then
26 - echo 'Warning: Failed to install all requirements. Continue? y/N'
33 -if ! pip install -r test-requirements.txt ; then
34 - echo "Warning test requirements wasn't installed, Note: normal operation should still work fin…
44 -md5sum requirements.txt test-requirements.txt dev_setup.sh > .installed
[all …]
/openbmc/linux/drivers/mtd/nand/raw/
H A Dnand_samsung.c14 struct nand_ecc_props requirements = {}; in samsung_nand_decode_id() local
76 requirements.step_size = 512; in samsung_nand_decode_id()
77 requirements.strength = 1 << extid; in samsung_nand_decode_id()
79 requirements.step_size = 1024; in samsung_nand_decode_id()
82 requirements.strength = 24; in samsung_nand_decode_id()
85 requirements.strength = 40; in samsung_nand_decode_id()
88 requirements.strength = 60; in samsung_nand_decode_id()
92 requirements.step_size = 0; in samsung_nand_decode_id()
102 requirements.step_size = 512; in samsung_nand_decode_id()
103 requirements.strength = 1; in samsung_nand_decode_id()
[all …]
H A Dnand_esmt.c14 struct nand_ecc_props requirements = {}; in esmt_nand_decode_id() local
20 requirements.step_size = 512; in esmt_nand_decode_id()
23 requirements.strength = 4; in esmt_nand_decode_id()
26 requirements.strength = 2; in esmt_nand_decode_id()
29 requirements.strength = 1; in esmt_nand_decode_id()
33 requirements.step_size = 0; in esmt_nand_decode_id()
38 nanddev_set_ecc_requirements(base, &requirements); in esmt_nand_decode_id()
H A Dnand_hynix.c499 struct nand_ecc_props requirements = {}; in hynix_nand_extract_ecc_requirements() local
504 requirements.step_size = 1024; in hynix_nand_extract_ecc_requirements()
508 requirements.step_size = 0; in hynix_nand_extract_ecc_requirements()
509 requirements.strength = 0; in hynix_nand_extract_ecc_requirements()
512 requirements.strength = 4; in hynix_nand_extract_ecc_requirements()
515 requirements.strength = 24; in hynix_nand_extract_ecc_requirements()
518 requirements.strength = 32; in hynix_nand_extract_ecc_requirements()
521 requirements.strength = 40; in hynix_nand_extract_ecc_requirements()
524 requirements.strength = 50; in hynix_nand_extract_ecc_requirements()
527 requirements.strength = 60; in hynix_nand_extract_ecc_requirements()
[all …]
H A Dnand_toshiba.c149 struct nand_ecc_props requirements = {}; in toshiba_nand_decode_id() local
180 requirements.step_size = 512; in toshiba_nand_decode_id()
183 requirements.strength = 1; in toshiba_nand_decode_id()
186 requirements.strength = 4; in toshiba_nand_decode_id()
189 requirements.strength = 8; in toshiba_nand_decode_id()
193 requirements.step_size = 0; in toshiba_nand_decode_id()
198 nanddev_set_ecc_requirements(base, &requirements); in toshiba_nand_decode_id()
H A Dnand_micron.c416 const struct nand_ecc_props *requirements = in micron_supports_on_die_ecc() local
430 if (requirements->strength != 4 && requirements->strength != 8) in micron_supports_on_die_ecc()
471 if (requirements->strength != 4 && requirements->strength != 8) in micron_supports_on_die_ecc()
480 const struct nand_ecc_props *requirements = in micron_nand_init() local
531 if (requirements->strength == 4) { in micron_nand_init()
541 if (requirements->strength == 4) in micron_nand_init()
548 chip->ecc.bytes = requirements->strength * 2; in micron_nand_init()
550 chip->ecc.strength = requirements->strength; in micron_nand_init()
H A Dnand_onfi.c38 struct nand_ecc_props requirements; in nand_flash_detect_ext_param_page() local
99 requirements.strength = ecc->ecc_bits; in nand_flash_detect_ext_param_page()
100 requirements.step_size = 1 << ecc->codeword_size; in nand_flash_detect_ext_param_page()
101 nanddev_set_ecc_requirements(base, &requirements); in nand_flash_detect_ext_param_page()
272 struct nand_ecc_props requirements = { in nand_onfi_detect() local
277 nanddev_set_ecc_requirements(base, &requirements); in nand_onfi_detect()
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-lief/
H A D0001-build-requirements.txt-Allow-newer-versions.patch4 Subject: [PATCH] build-requirements.txt: Allow newer versions
12 api/python/build-requirements.txt | 14 +++++++-------
15 diff --git a/api/python/build-requirements.txt b/api/python/build-requirements.txt
17 --- a/api/python/build-requirements.txt
18 +++ b/api/python/build-requirements.txt
/openbmc/openbmc/poky/documentation/toaster-manual/
H A Dstart.rst27 requirements file named ``toaster-requirements.txt`` defines the Python
28 dependencies. The requirements file is located in the ``bitbake``
31 ``poky/bitbake/toaster-requirements.txt``). The dependencies appear in a
40 $ pip3 install --user -r bitbake/toaster-requirements.txt
/openbmc/phosphor-dbus-interfaces/
H A DREADME.md7 through the documented set of the common [requirements and expectations][].
33 [requirements and expectations]: requirements.md
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-hatch-requirements-txt_0.4.1.bb1 SUMMARY = "Hatchling plugin to read project dependencies from requirements.txt"
2 HOMEPAGE = "https://github.com/repo-helper/hatch-requirements-txt"
/openbmc/openbmc/poky/documentation/migration-guides/
H A Drelease-notes-4.0.17.rst66 - manuals: add minimum RAM requirements
68 - manuals: update disk space requirements
85 - ref-manual: system-requirements: recommend buildtools for not supported distros
86 - ref-manual: system-requirements: add info on buildtools-make-tarball
88 - ref-manual: system-requirements: fix AlmaLinux variable name
89 - ref-manual: system-requirements: modify anchor
90 - ref-manual: system-requirements: remove outdated note
91 - ref-manual: system-requirements: simplify supported distro requirements
92 - ref-manual: system-requirements: update packages to build docs
/openbmc/openbmc/poky/bitbake/lib/toaster/
H A Dtox.ini20 -r {toxinidir}/../../toaster-requirements.txt
21 -r {toxinidir}/tests/toaster-tests-requirements.txt
/openbmc/pldm/tools/visualize-pdr/
H A DREADME.md34 - The `requirements.txt` file should list all Python libraries that the tool
38 sudo pip3 install -r requirements.txt
40 pip3 install -r requirements.txt --user
/openbmc/qemu/tests/vm/
H A Dhaiku.x86_6456 requirements = [ variable in HaikuVM
112 self.ssh_root("pkgman install -y %s" % " ".join(self.requirements))
/openbmc/openbmc-tools/bi2cp/
H A DREADME.md7 dependencies are listed in `requirements.txt`:
10 pip3 install --user --requirement requirements.txt
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-kernel/wireguard/
H A Dwireguard-module_1.0.20220627.bb12 # configuration options. For exact kernel requirements visit:
13 # https://www.wireguard.io/install/#kernel-requirements
/openbmc/openbmc/poky/scripts/contrib/
H A Dpatchtest.sh82 pip install -r $PT/requirements.txt --quiet
83 pip install -r $PTOE/requirements.txt --quiet
/openbmc/qemu/docs/system/
H A Dsecurity.rst7 This chapter explains the security requirements that QEMU is designed to meet
14 requirements than others. The community has agreed on the overall security
15 requirements that users may depend on. These requirements define what is
43 the non-virtualization use case should meet the same security requirements as
46 requirements in mind.
56 requirements are met.
91 requirements. For example, guest A only has access to its own disk image file
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-iio-dma-buffer9 This property reports the alignment requirements in bytes.
13 The alignment requirements in number of sample sets will depend
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DSISSL-1.251 …requirements set out by the Standards body in effect one hundred twenty (120) days before You ship…
57 …ay distribute Original Code in Executable and Source form only if the requirements of Sections 3.1…
59 …rger Work as a single product. In such a case, You must make sure the requirements of this License…
107 1.0 Requirements for project Standards. The requirements for project Standards are version-dependen…
109 2.0 Additional requirements. The additional requirements pursuant to Section 3.1 are defined as:
111 …2.1 Naming Conventions. If any of your Modifications do not meet the requirements of the Standard,…
113 …2.2 Compliance Claims. If any of your Modifications do not meet the requirements of the Standards …
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/
H A DREADME.msl.md12 requirements on how the setting is used; implementations are free to react to
21 namespace. Again, there are no requirements on what an implementation does when
33 requirements, allowing a user to toggle the setting back and forth.
/openbmc/docs/
H A Dhw-vendor-repos-policy.md13 OpenBMC Github project is made. It starts with the requirements and then some
14 information on how those requirements were created.
26 following requirements to be eligible for a repository under OpenBMC:
30 3. It has no external dependencies which would fail the requirements defined
55 requirements:
57 1. It should meet all of the quality-based requirements for hosting a repository
120 The goal of this document is to clearly state the requirements and expectations
/openbmc/linux/Documentation/power/regulator/
H A Ddesign.rst15 have different power requirements, and not all components with power
16 requirements are visible to software.
/openbmc/linux/Documentation/kbuild/
H A DKconfig.recursion-issue-0212 # annotate those requirements, ie, some drivers use "depends on" while others
19 # core requirements are not carefully synced, as drivers evolve features
20 # they select or depend on end up becoming shared requirements which cannot be

12345678910>>...26