Home
last modified time | relevance | path

Searched refs:driver (Results 1 – 25 of 34) sorted by relevance

12

/xen/xen/drivers/char/
A Dserial.c107 port->driver->putc( in serial_tx_interrupt()
206 if ( !port->driver || !port->driver->putc ) in serial_putc()
221 if ( port->driver->flush ) in serial_putc()
236 if ( !port->driver || !port->driver->putc ) in serial_puts()
272 if ( !port->driver || !port->driver->getc ) in serial_getc()
504 if ( com[i].driver && com[i].driver->init_preirq ) in serial_init_preirq()
513 if ( com[i].driver && com[i].driver->init_irq ) in serial_init_irq()
534 if ( com[i].driver && com[i].driver->endboot ) in serial_endboot()
541 com[idx].driver && com[idx].driver->irq ) in serial_irq()
550 com[idx].driver && com[idx].driver->vuart_info ) in serial_vuart_info()
[all …]
A DKconfig2 bool "NS16550 UART driver" if ARM
8 bool "Xilinx Cadence UART driver"
16 bool "Marvell MVEBU UART driver"
24 bool "Amlogic MESON UART driver"
32 bool "ARM PL011 UART driver"
40 bool "Samsung Exynos 4210 UART driver"
48 bool "Texas Instruments OMAP UART driver"
56 bool "SuperH SCI(F) UART driver"
/xen/docs/misc/
A Dvtd.txt15 4 ) change XEN->"PCI-device backend driver" from "M" to "*".
31 a) check if the driver has binded to the device
32 ls -l /sys/bus/pci/devices/0000:01:00.0/driver
34 b) if yes, then unload the driver first
52 4 ) change Bus options (PCI etc.)->"PCI Stub driver" to "*".
231 device's view and driver's view are different. Similarly, the
233 driver's view are different. As a result, device can't access to the
234 buffer specified by driver.
264 Kernel driver in use: igb
302 The Virtual Function only appears after the Physical Function driver
[all …]
A Dhvm-emulated-unplug.pandoc55 It is still permitted for a driver to use this logging feature if it
62 xenstore. A driver version is considered to be blacklisted if
63 `/mh/driver-blacklist/{product_name}/{build_number}` exists and is
A Dblock-scripts.txt94 blkback driver.
98 going through loopback; so its driver will consume
A Dgrant-tables.txt10 whilst retaining ownership. The block front driver uses this to grant memory
11 access to the block back driver, so that it may read or write as requested.
21 domB. The net front and back driver will use this for packet tx/rx. This
/xen/docs/man/
A Dxen-vtpmmgr.7.pod39 the mini-os tpm_tis driver.
121 Choose the driver used for communication with the hardware TPM. Values
142 The following options only apply to the tpm_tis driver:
335 Linux kernel virtual TPM frontend driver. This driver
340 Mini-os TPM backend driver. The Linux frontend driver
341 connects to this backend driver to facilitate
343 driver is also used by vtpmmgr-stubdom to communicate with
355 Mini-os TPM frontend driver. The vTPM mini-os domain
356 vtpm-stubdom uses this driver to communicate with
357 vtpmmgr-stubdom. This driver could also be used separately to
[all …]
A Dxen-vtpm.7.pod80 Linux kernel virtual TPM frontend driver. This driver
85 Mini-os TPM backend driver. The Linux frontend driver
86 connects to this backend driver to facilitate
88 driver is also used by vtpmmgr-stubdom to communicate with
100 Mini-os TPM frontend driver. The vTPM mini-os domain
101 vtpm-stubdom uses this driver to communicate with
102 vtpmmgr-stubdom. This driver could also be used separately to
117 driver. This driver used by vtpmmgr-stubdom to talk directly to
163 driver. It can be built directly into the kernel or as a module; however, some
228 driver. Add the following line:
[all …]
A Dxl-disk-configuration.5.pod222 driver domain which is outside the scope of this document.
248 which software implementation of the Xen backend driver is used.
287 There is a memory lifetime bug in some driver domain (dom0) kernels
340 An advisory setting for the backend driver, specifying whether to
A Dxen-pci-device-reservations.7.pod58 driver binding:
A Dxl.1.pod.in398 Set the target for the domain's balloon driver.
407 driver to reach the target amount of memory. The guest may fail to
414 The guest doesn't have a balloon driver installed
418 The guest's balloon driver is buggy
422 The guest's balloon driver cannot create free guest memory due to
427 The guest's balloon driver cannot allocate memory from Xen because of
432 The guest administrator has disabled the balloon driver
1603 backend driver in domain 0 rather than a real driver.
1609 "quarantine domain". If it is already bound to a driver, it will
1610 first be unbound, and the original driver stored so that it can be
[all …]
A Dxen-pv-channel.7.pod111 driver will generate a hotplug event
/xen/docs/designs/
A Ddmop.pandoc17 the idea place to do this is within the privcmd driver, without privcmd
23 The privcmd driver implements a new restriction ioctl, which takes a domid
25 on the privcmd driver will cease to function, including regular hypercalls.
63 Validation by privcmd driver
66 If the privcmd driver has been restricted to specific domain (using a
A Dnon-cooperative-migration.md27 The PV driver model consists of a *frontend* and a *backend*. The frontend
74 by the frontend driver) will update the backend state node to 2
78 Upon seeing a backend state value of 2, the frontend driver will then read
82 Upon see this frontend state, the backend driver will then read the grant
96 Moreover the backend-id value will be used by the frontend driver in
102 drivers, without the co-operation of the frontend driver code, the paths and
178 They are an important part of post PV protocols. Normally a frontend driver
184 in Xenstore. The backend driver then reads this port number and *binds* to
215 driver to the backend driver by allocating *grant entries* in the guest’s
/xen/xen/include/xen/
A Dserial.h45 struct uart_driver *driver; member
153 void serial_register_uart(int idx, struct uart_driver *driver, void *uart);
/xen/tools/hotplug/Linux/systemd/
A Dxendriverdomain.service.in2 Description=Xen driver domain device daemon
/xen/
A DSUPPORT.md178 ### libvirt driver for xl
382 ## Virtual driver support, guest side
386 Guest-side driver capable of speaking the Xen PV block protocol
412 Guest-side driver capable of speaking the Xen PV display protocol
446 Guest-side driver capable of speaking the Xen PV TPM protocol
452 Guest-side driver capable of speaking the Xen 9pfs protocol
458 Guest-side driver capable of making pv system calls
464 Guest-side driver capable of speaking the Xen PV sound protocol
566 to a hostile driver domain (either compromised or untrusted)
621 with dom0, driver domains, stub domains, domUs, and so on.
[all …]
A Dconfig.guess111 for driver in cc gcc c89 c99 ; do
112 if ($driver -c -o "$dummy.o" "$dummy.c") >/dev/null 2>&1 ; then
113 CC_FOR_BUILD="$driver"
/xen/docs/misc/arm/
A Dearly-printk.txt13 set other options, which depends on the driver selected.
18 Other options depends on the driver selected:
/xen/docs/figs/
A Dnetwork-bridge.fig104 4 0 0 50 -1 0 20 0.0000 4 285 3330 990 3420 Backend (driver) domain\001
A Dnetwork-basic.fig68 4 0 0 50 -1 0 20 0.0000 4 285 3330 990 3420 Backend (driver) domain\001
/xen/docs/misc/arm/device-tree/
A Dpassthrough.txt5 DOM0 and therefore no driver will be loaded.
/xen/xen/drivers/passthrough/
A DKconfig7 bool "ARM SMMUv1 and v2 driver"
/xen/tools/firmware/vgabios/
A DREADME37 You have to register the "unmapped" device driver in plex86 or bochs, and make
206 by the unknown-ioport driver of plex/bochs (port 0xfff0 is used)
/xen/stubdom/grub.patches/
A D00cvs518 + Subject: Re: [Etherboot-developers] cs89x0 driver in etherboot
530 /* cs89x0.c: A Crystal Semiconductor CS89[02]0 driver for etherboot. */
532 Permission is granted to distribute the enclosed cs89x0.[ch] driver
543 + Subject: Re: [Etherboot-developers] cs89x0 driver in etherboot
675 * network device driver which uses this chip

Completed in 34 milliseconds

12