#1823: On some systems (real hardware) any direct drawing to framebuffer is really slow ---------------------------+------------------------------------------------ Reporter: stippi | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/pre-alpha1 Keywords: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by bonefish): Replying to [comment:16 michael.weirauch]: > Replying to [comment:14 bonefish]: > > [...] Since that is not the only problem of the current algorithm -- it also computes an incorrect (slightly too large) setup for the RAM and has exponential (!) complexity by design -- I'm rewriting the whole MTRR handling. > > That sentence makes me whonder if that "slightly too large" might be a reason for me having to limit the availbale memory to 3067 MB in order to not having the system freeze? c.f. #3772 (also includes MTRR setup listings) If a memory range containing hardware registers is accidentally set to write-back, that might indeed not be healthy. Would be interesting to see the RAM ranges and the MTRR setup. -- Ticket URL: <http://dev.haiku-os.org/ticket/1823#comment:17> Haiku <http://dev.haiku-os.org> Haiku - the operating system.