search for: drm_addmap_core

...Aug 6 21:11:29 localhost [drm] Initialized nouveau 0.0.10 20060213 on minor 0 Aug 6 21:11:29 localhost [drm] Used old pci detect: framebuffer loaded Aug 6 21:11:46 localhost [drm:drm_stub_open] Aug 6 21:11:46 localhost [drm:drm_open_helper] pid = 6567, minor = 0 Aug 6 21:11:46 localhost [drm:drm_addmap_core] offset = 0x00000000, size = 0x00002000, type = 2 Aug 6 21:11:46 localhost [drm:drm_addmap_core] 8192 13 ffffc2000003b000 Aug 6 21:11:46 localhost [drm:drm_setup] Aug 6 21:11:46 localhost [drm:drm_unlocked_ioctl] pid=6567, cmd=0xc0406400, nr=0x00, dev 0xe200, auth=1 Aug 6 21:11:46 localhost [d...

http://bugs.freedesktop.org/show_bug.cgi?id=11918 Summary: drmMap of framebuffer failed Product: Mesa Version: CVS Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: pmandin at

Hi, Please find attached the patches which I currently use on my desktop machine for dual head with the randr branch to fix the issues which I found. They may help others as well but may e.g. also disable the Xv blitter which might be working for some (but didn't on my card) - more information is found in the text comments in the patches. I have to hurry so this is short, will be back.

I've been doing some testing and it seems that glyphs (typically smaller than a page size on nv50) render slow'ish sometimes, mostly due to the many trips to the kernel (drm_addmap_core is the symbol that shows up). Ofcource this was a benchmark, but it does leave me wondering, do we really need need to call the kernel for every little pixmap? Also from a memory point of view, because a single page can theoretically contain 32 pixmaps. Is it problematic to combine small allocation...