Home
last modified time | relevance | path

Searched full:requirements (Results 1 – 25 of 1867) sorted by relevance

12345678910>>...75

/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
73 /* Extract ECC requirements from 5th id byte*/ in samsung_nand_decode_id()
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()
[all …]
H A Dnand_esmt.c14 struct nand_ecc_props requirements = {}; in esmt_nand_decode_id() local
18 /* Extract ECC requirements from 5th id byte. */ in esmt_nand_decode_id()
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
173 * Extract ECC requirements from 6th id byte. in toshiba_nand_decode_id()
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_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()
294 pr_warn("Could not retrieve ONFI ECC requirements\n"); in nand_onfi_detect()
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()
/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.rst12 Setting Up the Basic System Requirements
27 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/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DResource.v1_21_0.json251 …rties contained in this object shall conform to the Redfish Specification-described requirements.",
500 …de for this resource. The value shall conform to the RFC5139-defined requirements of the PC field…
629 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the ADDCODE fie…
639 …"longDescription": "The value shall conform to the requirements of the LOC field as defined in RFC…
649 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the BLD field. …
659 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the A3 field. …
669 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the PCN field. …
679 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the Country fie…
689 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the A2 field. …
699 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the A4 field. …
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DResource.v1_21_0.json251 …rties contained in this object shall conform to the Redfish Specification-described requirements.",
500 …de for this resource. The value shall conform to the RFC5139-defined requirements of the PC field…
629 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the ADDCODE fie…
639 …"longDescription": "The value shall conform to the requirements of the LOC field as defined in RFC…
649 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the BLD field. …
659 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the A3 field. …
669 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the PCN field. …
679 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the Country fie…
689 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the A2 field. …
699 …"longDescription": "The value shall conform to the RFC5139-defined requirements of the A4 field. …
[all …]
/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 …
H A DAPL-1.0117 For greater certainty, the above-noted requirements apply to any Licensed Work or portion thereof d…
127 3.5. NO DISTRIBUTION REQUIREMENTS FOR INTERNALLY USED MODIFICATIONS.
137 …Distributor or Recipient (as the case may be) must make sure that the requirements of this License…
141 …requirements of Part 1 of the Supplement File, that such Subsequent Contributor made in the creati…
143 …requirements or add to or change earlier requirements (in each case, the "EARLIER DESCRIPTION REQU…
145 …Requirements may choose, with respect to each such Earlier Licensed Copy, to comply with the Earli…
147 …each Recipient of any Licensed Work to the extent Part 1 sets out the requirements for documenting…
149 …requirements for documenting changes and contributions made by Subsequent Contributor is set out i…
159 …mation is set out in Part 2 of the Supplement File, then there are no requirements for Recipients …
163 … only be used to specify the nature of the description or attribution requirements, as the case ma…
/openbmc/qemu/docs/system/
H A Dsecurity.rst7 This chapter explains the security requirements that QEMU is designed to meet
10 Security Requirements
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/qemu/
H A D.patchew.yml122 requirements: docker
129 requirements: docker,x86_64
136 requirements: ''
144 requirements: docker,x86_64
151 requirements: ppcle
180 requirements: ppcbe
209 requirements: qemu-x86,x86_64,git
227 requirements: docker,x86_64
234 requirements: s390x
261 requirements:
/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.
16 ## Requirements section in Hardware Vendor Repository Policy
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/pldm/tools/visualize-pdr/
H A DREADME.md13 ## Requirements section in Overview
34 - 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/phosphor-dbus-interfaces/
H A DREADME.md7 through the documented set of the common [requirements and expectations][].
33 [requirements and expectations]: requirements.md
/openbmc/linux/Documentation/gpu/
H A Ddrm-uapi.rst49 Open-Source Userspace Requirements
52 The DRM subsystem has stricter requirements than most other kernel subsystems on
54 explains what exactly those requirements are, and why they exist.
89 leads to a few additional requirements:
105 requirements by doing a quick fork.
107 - The kernel patch can only be merged after all the above requirements are met,
112 These are fairly steep requirements, but have grown out from years of shared
218 The goal raises at least the following requirements for the kernel and
221 Requirements for KMS UAPI
240 Requirements for Render and Cross-Device UAPI
[all …]
/openbmc/linux/include/linux/
H A Dzconf.h11 /* The memory requirements for deflate are (in bytes):
15 the default memory requirements from 256K to 128K, compile with
19 The memory requirements for inflate are (in bytes) 1 << windowBits
/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/designs/
H A Ddesign-template.md25 may learn of new requirements during the design review process that could
64 keep it short. Elaborate on the details below in the Background and Requirements
75 specific requirements details, or ideas to solve problems here.
77 ## Requirements section in Example design - this is the design title
H A Dredfish-pcie.md25 ## Requirements section in Redfish PCIe Resources
27 This feature is intended to meet the Redfish requirements for the PCIe resources
52 changes and any BIOS timing requirements, so it can check for hardware changes,
/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/meta-raspberrypi/
H A D.readthedocs.yaml11 - requirements: docs/requirements.txt

12345678910>>...75