Home
last modified time | relevance | path

Searched full:manage (Results 1 – 25 of 1260) sorted by relevance

12345678910>>...51

/OK3568_Linux_fs/yocto/poky/bitbake/bin/
H A Dtoaster17 Usage 2: source toaster manage [createsuperuser|lsupdates|migrate|makemigrations|checksettings|coll…
32 # ../bitbake/lib/toaster/manage.py createsuperuser --username=<ME>
33 $MANAGE migrate --noinput || retval=1
41 $MANAGE checksettings --traceback || retval=1
86 $MANAGE runserver --noreload "$ADDR_PORT" \
154 MANAGE="python3 $BBBASEDIR/lib/toaster/manage.py"
212 manage )
221 if [ "manage" == "$CMD" ] ; then
275 $MANAGE checksocket "$ADDR_PORT" || return 1
301 $MANAGE runbuilds \
[all …]
/OK3568_Linux_fs/kernel/drivers/crypto/ccp/
H A Dsp-dev.c83 /* Need a common routine to manage all interrupts */ in sp_request_ccp_irq()
96 /* Each sub-device can manage it's own interrupt */ in sp_request_ccp_irq()
111 /* Need a common routine to manage all interrupts */ in sp_request_psp_irq()
124 /* Each sub-device can manage it's own interrupt */ in sp_request_psp_irq()
136 /* Using common routine to manage all interrupts */ in sp_free_ccp_irq()
147 /* Each sub-device can manage it's own interrupt */ in sp_free_ccp_irq()
155 /* Using common routine to manage all interrupts */ in sp_free_psp_irq()
166 /* Each sub-device can manage it's own interrupt */ in sp_free_psp_irq()
/OK3568_Linux_fs/yocto/poky/documentation/toaster-manual/
H A Dreference.rst11 some useful ``manage.py`` commands that are Toaster-specific.
12 Information on ``manage.py`` commands is available across the Web and
133 $ bitbake/lib/toaster/manage.py lsupdates
511 stop Toaster, command-line commands are available through the ``manage.py``
512 management script. You can find general documentation on ``manage.py``
515 site. However, several ``manage.py`` commands have been created that are
519 ``bitbake/lib/manage.py``. This section documents those commands.
523 - When using ``manage.py`` commands given a default configuration,
526 ``manage.py`` commands from the Build Directory allows Toaster to
531 can use ``manage.py`` commands from a directory other than the
[all …]
/OK3568_Linux_fs/kernel/drivers/scsi/cxlflash/
H A Dlunmgt.c219 * @manage: Manage ioctl data structure.
228 struct dk_cxlflash_manage_lun *manage) in cxlflash_manage_lun() argument
234 u64 flags = manage->hdr.flags; in cxlflash_manage_lun()
238 lli = find_and_create_lun(sdev, manage->wwid); in cxlflash_manage_lun()
240 __func__, get_unaligned_be64(&manage->wwid[0]), in cxlflash_manage_lun()
241 get_unaligned_be64(&manage->wwid[8]), manage->hdr.flags, lli); in cxlflash_manage_lun()
/OK3568_Linux_fs/kernel/Documentation/core-api/irq/
H A Dirq-domain.rst33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
163 controller to manage IRQ allocations and it requires an irq_desc to be
210 CPU Vector irq_domain (root irq_domain to manage CPU vectors)
213 Interrupt Remapping irq_domain (manage irq_remapping entries)
216 IOAPIC irq_domain (manage IOAPIC delivery entries/pins)
258 3) Optionally implement an irq_chip to manage the interrupt controller
/OK3568_Linux_fs/app/forlinx/quectelCM/
H A Dudhcpc_script.c76 …* The main aim of this function is offload ip management to script, CM has not interest in manage
92 // manage IPv4??? in udhcpc_start()
110 // manage IPv6??? in udhcpc_start()
116 …* The main aim of this function is offload ip management to script, CM has not interest in manage
/OK3568_Linux_fs/kernel/Documentation/driver-api/usb/
H A Ddma.rst19 manage dma mappings for existing dma-ready buffers (see below).
27 don't manage dma mappings for URBs.
41 IOMMU to manage the DMA mappings. It can cost MUCH more to set up and
129 The calls manage ``urb->transfer_dma`` for you, and set
/OK3568_Linux_fs/kernel/drivers/thermal/
H A DKconfig116 Select this if you want to let the user space manage the
132 Enable this to manage platform thermals using fair-share governor.
137 Enable this to manage platform thermals using a simple linear
144 Enable this to manage platform thermals using bang bang governor.
153 Enable this to let the user space manage the platform thermals.
159 Enable this to manage platform thermals by dynamically
/OK3568_Linux_fs/kernel/sound/soc/
H A Dsoc-devres.c19 * @dev: Device used to manage component
58 * @dev: Device used to manage component
96 * @dev: Device used to manage card
/OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/tests/browser/
H A DREADME53 …44/wd/hub TOASTER_TESTS_URL=http://172.17.0.1:8000 ./bitbake/lib/toaster/manage.py test --liveserv…
54 …te TOASTER_REMOTE_HUB=http://127.0.0.1:4444/wd/hub ./bitbake/lib/toaster/manage.py test --liveserv…
74 PATH=/home/me/apps/phantomjs/bin:$PATH TOASTER_TESTS_BROWSER=phantomjs manage.py test tests.browser
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-connectivity/libqrtr-glib/
H A Dlibqrtr-glib_git.bb1 SUMMARY = "library to use and manage the QRTR bus"
2 DESCRIPTION = "libqrtr-glib is a glib-based library to use and manage the QRTR (Qualcomm IPC Router…
/OK3568_Linux_fs/buildroot/package/tpm2-tools/
H A DConfig.in14 API of TPM2-TSS. These tools can be used to manage keys,
16 and manage non-volatile storage through a TPM2.0 HW
/OK3568_Linux_fs/kernel/arch/powerpc/platforms/cell/
H A DMakefile19 spu-manage-$(CONFIG_PPC_CELL_COMMON) += spu_manage.o
25 $(spu-manage-y) \
/OK3568_Linux_fs/kernel/drivers/firmware/broadcom/
H A DKconfig31 This module help to manage firmware on Broadcom BNXT device. The module
32 registers on tee bus and invoke calls to manage firmware on BNXT device.
/OK3568_Linux_fs/buildroot/support/testing/tests/package/
H A Dtest_python_django.py14 cmd = "cd /opt/testsite && " + self.interpreter + " ./manage.py migrate"
19 cmd = "cd /opt/testsite && " + self.interpreter + " ./manage.py runserver 0.0.0.0:1234 & "
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/cfengine/
H A Dcfengine-masterfiles_3.15.0.bb8 in an IT system to manage and understand IT infrastructure throughout \
9 its lifecycle. CFEngine takes systems from Build to Deploy, Manage and Audit. \
H A Dcfengine_3.15.0.bb8 in an IT system to manage and understand IT infrastructure throughout \
9 its lifecycle. CFEngine takes systems from Build to Deploy, Manage and Audit."
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/gcc/gcc/
H A D0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch19 # for target_alias and gcc doesn't manage it consistently.
32 # for target_alias and gcc doesn't manage it consistently.
/OK3568_Linux_fs/kernel/arch/powerpc/platforms/powernv/
H A Dopal-flash.c31 /* Manage image status values */
40 /* Manage operation tokens */
223 * Manage flash routine
233 * Show manage flash status
248 * Manage operations:
/OK3568_Linux_fs/external/xserver/Xext/
H A Dxselinuxint.h171 "manage", /* DixManageAccess */
354 "manage", /* DixManageAccess */
382 "manage", /* DixManageAccess */
412 "manage", /* DixManageAccess */
442 "manage", /* DixManageAccess */
/OK3568_Linux_fs/kernel/arch/alpha/include/asm/
H A Dpci.h13 * The following structure is used to manage multiple PCI busses.
19 /* A controller. Used to manage multiple PCI busses. */
/OK3568_Linux_fs/kernel/drivers/misc/sgi-gru/
H A Dgrutables.h70 * to manage user contexts and to perform functions such as TLB dropin and
87 * GMS - GRU Memory Struct - Used to manage TLB shootdowns. Tracks GRUs
91 * GS - GRU State - Used to manage the state of a GRU chiplet
92 * BS - Blade State - Used to manage state of all GRU chiplets
424 unsigned long gs_context_map; /* bitmap to manage
426 unsigned long gs_cbr_map; /* bitmap to manage CB
428 unsigned long gs_dsr_map; /* bitmap used to manage
/OK3568_Linux_fs/kernel/arch/arc/boot/dts/
H A Dabilis_tb10x.dtsi220 tb100-mdscr-manage-tsin;
229 tb100-mdscr-manage-tsin;
234 tb100-mdscr-manage-tsin;
/OK3568_Linux_fs/kernel/drivers/infiniband/hw/i40iw/
H A Di40iw_vf.c45 * i40iw_manage_vf_pble_bp - manage vf pble
76 i40iw_debug_buf(cqp->dev, I40IW_DEBUG_WQE, "MANAGE VF_PBLE_BP WQE", wqe, I40IW_CQP_WQE_SIZE * 8); in i40iw_manage_vf_pble_bp()
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/location/maps/
H A Dqgeocodingmanager.cpp58 QGeoCodeReply objects, which manage these operations and report on the
144 A QGeoCodeReply object will be returned, which can be used to manage the
181 A QGeoCodeReply object will be returned, which can be used to manage the
221 A QGeoCodeReply object will be returned, which can be used to manage the

12345678910>>...51