Home
last modified time | relevance | path

Searched refs:configurations (Results 1 – 25 of 511) sorted by relevance

12345678910>>...21

/OK3568_Linux_fs/yocto/poky/scripts/lib/resulttool/
H A Dmanualexecution.py60 configurations = {}
61 configurations['LAYERS'] = layers
62 configurations['STARTTIME'] = datetime.datetime.now().strftime('%Y%m%d%H%M%S')
63 configurations['TEST_TYPE'] = 'manual'
64 configurations['TEST_MODULE'] = test_module
66 extra_config = set(store_map['manual']) - set(configurations)
84 configurations[config] = value_conf
85 return configurations
127 configurations = self._get_config(config_options, test_module)
128 result_id = 'manual_%s_%s' % (test_module, configurations['STARTTIME'])
[all …]
/OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-daemons/proftpd/files/
H A Dclose-RequireValidShell-check.patch10 sample-configurations/basic.conf | 1 +
13 diff --git a/sample-configurations/basic.conf b/sample-configurations/basic.conf
15 --- a/sample-configurations/basic.conf
16 +++ b/sample-configurations/basic.conf
H A Dbasic.conf.patch10 --- proftpd-1.3.3c.orig/sample-configurations/basic.conf
11 +++ proftpd-1.3.3c/sample-configurations/basic.conf
/OK3568_Linux_fs/kernel/Documentation/usb/
H A Dgadget_configfs.rst18 A gadget is seen by its host as a set of configurations, each of which contains
24 Creating a gadget means deciding what configurations there will be
93 2. Creating the configurations
96 Each gadget will consist of a number of configurations, their corresponding
145 4. Associating the functions with their configurations
149 configurations specified and a number of functions available. What remains
151 function can be used in multiple configurations). This is achieved with
168 configurations and functions.
226 Remove functions from configurations::
239 Remove strings directories in configurations:
[all …]
/OK3568_Linux_fs/kernel/Documentation/xtensa/
H A Dbooting.rst11 - For configurations without MMU, with region protection or with MPU the
13 - For configurations with region translarion MMU or with MMUv3 and CONFIG_MMU=n
16 - For configurations with MMUv2 the address must be a virtual address in the
18 - For configurations with MMUv3 and CONFIG_MMU=y the address may be either a
/OK3568_Linux_fs/buildroot/docs/manual/
H A Dadding-board-support.txt7 Buildroot contains basic configurations for several publicly available
17 target platform. You can of course use more complicated configurations
19 integrate basic board configurations. This is because package
39 kernel and bootloader configurations. If they are incorrect for your
47 and configurations in these directories, and reference them from the main
/OK3568_Linux_fs/u-boot/scripts/
H A Dfit-resign.sh70 …LEN=`./tools/fit_info -f ${ITB} -n /configurations/conf/signature -p value | sed -n "/LEN:/p" | aw…
71 …OFF=`./tools/fit_info -f ${ITB} -n /configurations/conf/signature -p value | sed -n "/OFF:/p" | aw…
72 …END=`./tools/fit_info -f ${ITB} -n /configurations/conf/signature -p value | sed -n "/END:/p" | aw…
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/net/
H A Dsnps,dwc-qos-ethernet.txt10 configurations.
29 In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
30 path. In other configurations, other clocks (such as tx_125, rmii) may
34 In some configurations (e.g. GMII/RGMII), this clock is derived from the
35 PHY's RX clock output. In other configurations, other clocks (such as
47 The master bus interface clock. Only required in configurations that use a
59 Note: Support for additional IP configurations may require adding the
67 This will allow easy support for configurations that support multiple PHY
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/net/
H A Dsnps,dwc-qos-ethernet.txt7 configurations.
26 In some configurations (e.g. GMII/RGMII), this clock also drives the PHY TX
27 path. In other configurations, other clocks (such as tx_125, rmii) may
31 In some configurations (e.g. GMII/RGMII), this clock is derived from the
32 PHY's RX clock output. In other configurations, other clocks (such as
44 The master bus interface clock. Only required in configurations that use a
56 Note: Support for additional IP configurations may require adding the
64 This will allow easy support for configurations that support multiple PHY
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-bus-iio-magnetometer-hmc58436 Current configuration and available configurations
10 normal Normal measurement configurations (default)
/OK3568_Linux_fs/kernel/Documentation/arm/pxa/
H A Dmfp.rst16 out of the GPIO controller. In addition to pin-mux configurations, the MFP
95 NOTE: PXA300 and PXA310 are almost identical in pin configurations (with
99 2. prepare an array for the initial pin configurations, e.g.::
123 a) once the pin configurations are passed to pxa{2xx,3xx}_mfp_config(),
127 b) when there is only one possible pin configurations for a component,
195 configurations, these definitions are processor and platform independent, and
211 configurations
215 for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations
264 Examples of pin configurations are::
/OK3568_Linux_fs/external/xserver/hw/xquartz/GL/
H A Dcapabilities.c456 cap->configurations = NULL; in initCapabilities()
513 conf = cap->configurations; in freeGlCapabilities()
521 cap->configurations = NULL; in freeGlCapabilities()
563 conf->next = cap->configurations; in getGlCapabilities()
564 cap->configurations = conf; in getGlCapabilities()
H A DvisualConfigs.c95 assert(NULL != caps.configurations); in __glXAquaCreateVisualConfigs()
99 for(conf = caps.configurations; conf; conf = conf->next) { in __glXAquaCreateVisualConfigs()
124 for(conf = caps.configurations; conf; conf = conf->next) { in __glXAquaCreateVisualConfigs()
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.srio-pcie-boot-corenet62 Then, it will finish necessary configurations for slave's boot from
73 necessary configurations.
85 1. Slave's RCW with SRIO or PCIE boot configurations, and all cores in holdoff
86 configurations.
106 UCode, ENV stored in master's NorFlash, and any other configurations
/OK3568_Linux_fs/buildroot/system/
H A Ddevice_table.txt5 # in both static device configurations (where /dev/ is static) and in
6 # dynamic configurations (where devtmpfs, mdev or udev are used).
/OK3568_Linux_fs/u-boot/doc/uImage.FIT/
H A Dsource_file_format.txt87 To identify FIT sub-nodes representing images, hashes, configurations (which
109 o configurations
135 - configurations : Contains a set of available configuration nodes and
203 6) '/configurations' node
206 The 'configurations' node is optional. If present, it allows to create a
207 convenient, labeled boot configurations, which combine together kernel images
210 The 'configurations' node has has the following structure:
212 o configurations
H A Dkernel.its30 configurations {
79 configurations {
/OK3568_Linux_fs/buildroot/board/atmel/
H A Dreadme.txt5 This guide covers the following configurations:
29 These configurations will use AT91Bootstrap, u-boot and a linux kernel from
32 The configurations labeled as 'dev' provide a development rootfs with tools to
46 provided to boot from an SD card. Those configurations are labeled as
50 For the other configurations listed above, the Buildroot configuration
/OK3568_Linux_fs/u-boot/arch/arm/mach-rockchip/rk3399/
H A DKconfig27 * on-module eMMC (up to 256GB configurations available)
28 * on-module DDR3 (1GB, 2GB and 4GB configurations available)
/OK3568_Linux_fs/kernel/drivers/usb/typec/altmodes/
H A Ddisplayport.c355 static const char * const configurations[] = { variable
371 con = sysfs_match_string(configurations, buf); in configuration_store()
423 for (i = 1; i < ARRAY_SIZE(configurations); i++) { in configuration_show()
425 len += sprintf(buf + len, "[%s] ", configurations[i]); in configuration_show()
428 len += sprintf(buf + len, "%s ", configurations[i]); in configuration_show()
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/pinctrl/
H A Dnvidia,tegra124-dpaux-padctl.txt17 Child nodes contain the pinmux configurations following the conventions
20 Since only three configurations are possible, only three child nodes are
H A Dfsl,mxs-pinctrl.txt27 configurations, and it's called group node in the binding document. The other
39 there to adjust configurations for some pins in the group.
52 since config node is only meant to set up pin configurations.
118 to function as a 8-bit mmc device, with 8mA, 3.3V and pull-up configurations
/OK3568_Linux_fs/yocto/poky/documentation/kernel-dev/
H A Dmaint-appx.rst17 list all necessary patches, configurations, branches, tags, and feature
24 images based on their configurations and features.
67 To see the features and configurations for a particular Yocto Linux
131 all the branches, tags, patches and configurations that need to be
154 combination of all supported boards and configurations.
186 has configurations and features grouped under the
188 configurations for the BeagleBone Board assuming a
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dpstore-blk.rst20 divides all configurations into two parts, configurations for user and
21 configurations for driver.
33 All of these configurations support both Kconfig and module parameters, but
40 The detail of each configurations may be of interest to you.
154 Only a block device driver cares about these configurations. A block device
/OK3568_Linux_fs/buildroot/board/armadeus/
H A Dreadme.txt21 configurations.
55 Building U-Boot is currently not supported in these configurations.

12345678910>>...21