#5085: Poor vesa performance on NVidia Quadro FX770M ---------------------------+------------------------------------------------ Reporter: PieterPanman | Owner: bonefish Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/Development Keywords: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:6 PieterPanman]: > Is there something I can hack in the kernel to get this to work for my case specifically? In src/system/kernel/arch/x86/arch_vm.cpp:arch_vm_init_post_modules() you could comment out the loop calling add_memory_type_range() and add a single call to add_memory_type_range() instead. I would first try the following: {{{ add_memory_type_range(-1, 0, 0xbe000000, B_MTR_WB); }}} If the holes in the RAM memory ranges are locations where device registers are mapped, this could cause problems, though. Then I would try a smaller range -- replace the 0xbe000000 e.g. by 0xbc000000 -- and also limit the used RAM size to that amount (LIMIT_AVAILABLE_MEMORY in the kernel_debug_config.h header). Your frame buffer range will still be too complex to be fully covered, but that should only concern the last 12 KB, i.e. only the last few rows. -- Ticket URL: <http://dev.haiku-os.org/ticket/5085#comment:7> Haiku <http://dev.haiku-os.org> Haiku - the operating system.