Home
last modified time | relevance | path

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

12345678910>>...32

/OK3568_Linux_fs/yocto/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 …]
/OK3568_Linux_fs/kernel/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_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_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_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()
273 struct nand_ecc_props requirements = { in nand_onfi_detect() local
278 nanddev_set_ecc_requirements(base, &requirements); in nand_onfi_detect()
H A Dnand_jedec.c124 struct nand_ecc_props requirements = { in nand_jedec_detect() local
129 nanddev_set_ecc_requirements(base, &requirements); in nand_jedec_detect()
/OK3568_Linux_fs/buildroot/package/python-crossbar/
H A D0002-Remove-idna-requirement.patch12 requirements-min.txt | 1 -
15 diff --git a/requirements-min.txt b/requirements-min.txt
17 --- a/requirements-min.txt
18 +++ b/requirements-min.txt
/OK3568_Linux_fs/buildroot/package/docker-compose/
H A D0002-Bump-texttable-from-0.9.1-to-1.6.2.patch10 requirements.txt | 2 +-
14 diff --git a/requirements.txt b/requirements.txt
16 --- a/requirements.txt
17 +++ b/requirements.txt
H A D0003-support-PyYAML-up-to-5.1-version.patch12 requirements.txt | 2 +-
16 diff --git a/requirements.txt b/requirements.txt
18 --- a/requirements.txt
19 +++ b/requirements.txt
/OK3568_Linux_fs/yocto/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
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/include/c++/10.3.1/ext/
H A Dalgorithm115 // concept requirements
199 // concept requirements
221 // concept requirements
239 // concept requirements
263 // concept requirements
298 // concept requirements
354 // concept requirements
385 // concept requirements
409 // concept requirements
433 // concept requirements
[all …]
H A Diterator78 // concept requirements
92 // concept requirements
108 // concept requirements -- taken care of in __distance
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/include/c++/10.3.1/ext/
H A Dalgorithm115 // concept requirements
199 // concept requirements
221 // concept requirements
239 // concept requirements
263 // concept requirements
298 // concept requirements
354 // concept requirements
385 // concept requirements
409 // concept requirements
433 // concept requirements
[all …]
H A Diterator78 // concept requirements
92 // concept requirements
108 // concept requirements -- taken care of in __distance
/OK3568_Linux_fs/buildroot/package/vkmark/
H A D0002-kms-Drop-dependency-on-vkCreateDmaBufImageINTEL.patch86 + const VkMemoryRequirements* requirements,
91 + if (((1u << i) & requirements->memoryTypeBits) == 0)
182 + VkMemoryRequirements requirements;
183 + vkGetImageMemoryRequirements(vulkan->device(), image, &requirements);
184 + if (!requirements.memoryTypeBits) {
189 + &requirements,
198 + .allocationSize = requirements.size,
/OK3568_Linux_fs/yocto/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 …
/OK3568_Linux_fs/yocto/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
/OK3568_Linux_fs/yocto/poky/scripts/contrib/
H A Dpatchtest.sh82 pip install -r $PT/requirements.txt --quiet
83 pip install -r $PTOE/requirements.txt --quiet
/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/kernel/Documentation/power/regulator/
H A Ddesign.rst15 have different power requirements, and not all components with power
16 requirements are visible to software.
/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/kernel/drivers/gpu/drm/panfrost/
H A Dpanfrost_job.c118 if (job->requirements & PANFROST_JD_REQ_FS) in panfrost_job_get_slot()
123 if (job->requirements & PANFROST_JD_REQ_ONLY_COMPUTE) { in panfrost_job_get_slot()
124 if ((job->requirements & PANFROST_JD_REQ_CORE_GRP_MASK) && in panfrost_job_get_slot()
135 u32 requirements, in panfrost_job_write_affinity() argument
173 panfrost_job_write_affinity(pfdev, job->requirements, js); in panfrost_job_hw_submit()
/OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/intel/
H A Digbvf.rst23 For questions related to hardware requirements, refer to the documentation
24 supplied with your Intel adapter. All hardware requirements listed apply to use

12345678910>>...32