Searched refs:engines (Results 1 – 10 of 10) sorted by relevance
36 $(ROOTPLUGINLIBDIR)/scsi/engines: $(ROOTPLUGINLIBDIR)/scsi39 $(ROOTPLUGINLIBDIR)/scsi/engines/$(MACH64): $(ROOTPLUGINLIBDIR)/scsi/engines
51 ROOTPROG = $(ROOTPLUGINLIBDIR)/scsi/engines/$(PROG)52 ROOTPROG64 = $(ROOTPLUGINLIBDIR)/scsi/engines/$(MACH64)/$(PROG)
29 engines
211 usb_audio_eng_t engines[USB_AC_ENG_MAX]; member287 _NOTE(DATA_READABLE_WITHOUT_LOCK(usb_ac_state_t::engines))
3146 engine = &(uacp->engines[0]); in usb_ac_stop_play()4506 engp = &statep->engines[i]; in usb_restore_engine()4618 engp = &(uacp->engines[0]); in usb_ac_add_eng()4620 engp = &(uacp->engines[1]); in usb_ac_add_eng()5201 if (statep->engines[0].af_engp) { in usb_ac_add_controls()5203 format = &(statep->engines[0].fmt); in usb_ac_add_controls()5206 statep->engines[0].af_defgain); in usb_ac_add_controls()5209 statep->engines[0].af_defgain); in usb_ac_add_controls()5215 if (statep->engines[1].af_engp) { in usb_ac_add_controls()5216 format = &(statep->engines[1].fmt); in usb_ac_add_controls()[all …]
111 * single-bit errors, but via separate serd engines to allow distinct129 * SERD engines which diagnose fault.memory.page_sb if they trip.132 * into additional per-rank SERD engines which diagnose fault.memory.page_ck136 * counted in stat engines for each type. These are used in deciding239 * Implementation: we maintain parallel SERD engines to the page_sb and240 * page_ck engines, which trip in unison. On trip it generates a distinct
101 and the existing relocation engines:111 may require you to also modify the existing relocation engines, and120 the engine, examine the code for the existing engines.
1027 dir path=usr/lib/scsi/plugins/scsi/engines1028 dir path=usr/lib/scsi/plugins/scsi/engines/$(ARCH64)1029 file path=usr/lib/scsi/plugins/scsi/engines/$(ARCH64)/uscsi.so1030 file path=usr/lib/scsi/plugins/scsi/engines/uscsi.so
462 …initializing the common blocks [i.e., the HW blocks shared between the 2 engines], but the driver …463 …ialized port [FUNCTION]\footnote{Initialization which is common for both engines will be performed…935 From pci standpoint, the distinction between the HW functions (and thus the HW engines) is done via…956 …W-functions under the devices and iterates when needed to configure both engines correctly (where …977 …ks for your queues, do recall that the MSI-X table is shared between the engines, as explained in …1727 …he test. This test is performed via MFW and accesses registers from both engines as well as regist…
5832 to engines in 100g device.