Searched refs:backend (Results 1 - 7 of 7) sorted by relevance

/drivers/xen/xenbus/
H A Dxenbus_probe_frontend.c135 return xenbus_read_otherend_details(xendev, "backend-id", "backend");
300 printk(KERN_DEBUG "XENBUS: backend %s %s\n",
311 printk(KERN_INFO "XENBUS: backend %s timed out.\n", be);
316 * Wait for backend to catch up.
323 printk(KERN_DEBUG "XENBUS: backend %s %s\n",
337 /* fall through to forward backend to state XenbusStateInitialising */
360 char *backend, *frontend; local
375 backend = xenbus_read(XBT_NIL, frontend, "backend", NUL
[all...]
/drivers/char/agp/
H A DMakefile1 agpgart-y := backend.o frontend.o generic.o isoch.o
/drivers/char/pcmcia/
H A DKconfig31 or via the cm4000 backend of OpenCT (http://www.opensc-project.org/opensc).
/drivers/net/ethernet/seeq/
H A Dsgiseeq.c629 struct sgiseeq_tx_desc *backend; local
631 backend = &sp->tx_desc[PREV_TX(sp->tx_new)];
632 dma_sync_desc_cpu(dev, backend);
633 backend->tdma.cntinfo &= ~HPCDMA_EOX;
634 dma_sync_desc_dev(dev, backend);
/drivers/vhost/
H A Dnet.c661 /* special case to disable backend */
813 struct vhost_vring_file backend; local
819 if (copy_from_user(&backend, argp, sizeof backend))
821 return vhost_net_set_backend(n, backend.index, backend.fd);
/drivers/block/
H A DKconfig502 tristate "Xen block-device backend driver"
505 The block-device backend driver allows the kernel to export its
512 The backend driver attaches itself to a any block device specified
516 If you are compiling a kernel to run in a Xen block backend driver
/drivers/net/
H A DKconfig308 The corresponding Linux backend driver is enabled by the
316 tristate "Xen backend network device"
327 The backend driver presents a standard network device

Completed in 779 milliseconds