Searched refs:accelerated (Results 1 – 7 of 7) sorted by relevance
91 This is the s390 hardware accelerated implementation of the99 This is the s390 hardware accelerated implementation of the110 This is the s390 hardware accelerated implementation of the124 This us the s390 hardware accelerated implementation of the133 This is the s390 hardware accelerated implementation of the
292 int accelerated; member387 int (*accelerated)(struct nes_cm_core *, struct nes_cm_node *); member
897 (!cm_node->accelerated)) { in mini_cm_dec_refcnt_listen()966 cm_node->accelerated = 1; in mini_cm_accelerated()1148 if (!cm_node->accelerated && cm_node->accept_pend) { in rem_ref_cm_node()2728 cm_node->cm_core->api->accelerated(cm_node->cm_core, cm_node); in nes_accept()3137 cm_node->cm_core->api->accelerated(cm_node->cm_core, cm_node); in cm_event_connected()
37 memory, or don't use any of the accelerated features.
53 (e.g. an accelerated X server) and that are not frame buffer94 (accelerated) version.102 This is used by drivers that don't provide their own (accelerated)112 (accelerated) version.130 (accelerated) version and the framebuffer is in system RAM.138 This is used by drivers that don't provide their own (accelerated)148 (accelerated) version and the framebuffer is in system RAM.1256 head is not compatible with accelerated XFree 3.3.x SVGA servers -1289 If you said M to "Matrox unified accelerated driver" and N here, you1616 Character imageblit, copyarea and rectangle fill are hw accelerated,
306 tristate "WM97xx Mainstone accelerated touch"
432 for ECP ports, since they can all do hardware accelerated