search for: defio

...dow buffer. Cirrus is an example of that. It uses shmem buffer objects as shadow fbs and internally updates the device frame buffer in its dirty callback. Using dirty() to select the shadow fbdev adds another buffer (and another memcpy) for no reason. Best regards Thomas > The thing with fbdev defio is that it only supports kmalloc and vmalloc > allocated memory (page->lru is avail.). This means that only the CMA > drivers can use defio without shadow memory. To keep things simple > everyone with a dirty() callback gets a shadow buffer. > > Noralf. > >> Best regard...

...dow buffer. Cirrus is an example of that. It uses shmem buffer objects as shadow fbs and internally updates the device frame buffer in its dirty callback. Using dirty() to select the shadow fbdev adds another buffer (and another memcpy) for no reason. Best regards Thomas > The thing with fbdev defio is that it only supports kmalloc and vmalloc > allocated memory (page->lru is avail.). This means that only the CMA > drivers can use defio without shadow memory. To keep things simple > everyone with a dirty() callback gets a shadow buffer. > > Noralf. > >> Best regard...

...ple of that. It uses shmem buffer objects as shadow fbs and > internally updates the device frame buffer in its dirty callback. Using > dirty() to select the shadow fbdev adds another buffer (and another > memcpy) for no reason. Cirruc uses shmem buffers and they won't work with fbdev defio (both use page->lru). shmem is the reason I added shadow buffering to generic fbdev in the first place. It will now work with whatever backing buffer the driver uses, as long as it can provide a virtual address on the dumb buffer (not the case with rockchip for instance, due to limited virtual a...

...the fb name from "nouveaufb" to "nouveaudrmfb". Aside: I wonder whether the in_interrupt() check is good enough for the nouveau acceleration. Cargo-cult says drm_can_sleep() is needed, which isn't actually working if you pick a .config without PREEMPT. For the generic fbdev defio support we've gone with offloading everything to a worker. For the non-accel callbacks (set_par, blank and friends) checking for oops_in_progress is good enough to catch all the evil calling contexts. v2: Rebase Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> Cc: Ben Skeggs &l...

Hi Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes: > > > Den 03.07.2019 10.32, skrev Thomas Zimmermann: >> DRM client buffers are permanently mapped throughout their lifetime. This >> prevents us from using generic framebuffer emulation for devices with >> small dedicated video memory, such as ast or mgag200. With fb buffers >> permanently mapped, such devices

Hi Am 03.07.19 um 21:27 schrieb Noralf Tr?nnes: > > > Den 03.07.2019 10.32, skrev Thomas Zimmermann: >> DRM client buffers are permanently mapped throughout their lifetime. This >> prevents us from using generic framebuffer emulation for devices with >> small dedicated video memory, such as ast or mgag200. With fb buffers >> permanently mapped, such devices

...-186,6 +186,8 @@ struct drm_fb_helper { * See also: @deferred_setup */ int preferred_bpp; + + bool use_shadow; }; static inline struct drm_fb_helper * > > I'm not sure if we should check for the dirty() callback at all. > Hm, why do you think that? The thing with fbdev defio is that it only supports kmalloc and vmalloc allocated memory (page->lru is avail.). This means that only the CMA drivers can use defio without shadow memory. To keep things simple everyone with a dirty() callback gets a shadow buffer. Noralf. > Best regards > Thomas > >> Reall...

...the fb name from "nouveaufb" to "nouveaudrmfb". Aside: I wonder whether the in_interrupt() check is good enough for the nouveau acceleration. Cargo-cult says drm_can_sleep() is needed, which isn't actually working if you pick a .config without PREEMPT. For the generic fbdev defio support we've gone with offloading everything to a worker. For the non-accel callbacks (set_par, blank and friends) checking for oops_in_progress is good enough to catch all the evil calling contexts. Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> Cc: Ben Skeggs <bskeggs at...

...use > the same drm_gem_fb_create_handle to match drm_gem_fb_funcs. > - I don't know why qxl_fb_find_or_create_single used to check for an > existing framebuffer and removed that check to match other drivers. > - Use of drm_fb_helper_fbdev_teardown also requires "info->fbdefio" to > be dynamically allocated. Replace the existing defio config by > drm_fb_helper_defio_init to accomodate this. > > Testing results: startx with fbdev, modesetting and qxl all seems to > work. Tested also with CONFIG_DRM_FBDEV_EMULATION=n, fbdev obviously > fails but...

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started