| OSDev.org https://forum.osdev.org/ |
|
| Stupid bicycle vs too large solution. https://forum.osdev.org/viewtopic.php?f=13&t=31325 |
Page 1 of 1 |
| Author: | monobogdan [ Tue Jan 31, 2017 2:28 am ] |
| Post subject: | Stupid bicycle vs too large solution. |
So, now i'm need to repaint some parts of screen every loop pass. And it's blink. So, i'm now have only 640kb of ram, and double buffering is too large for it's(because only binary in memory weight approx 300kb). I'm make for this small bicycle: Pass counter, when it's > 20k then zero it's and redraw part of screen. It's fast and reduce blink. But it's bicycle. What better? Double buffering in 300kb ram or bicycle with high CPU usage? |
|
| Author: | iansjack [ Tue Jan 31, 2017 2:39 am ] |
| Post subject: | Re: Stupid bicycle vs too large solution. |
Best is to use a motorcycle and not restrict yourself to less than 1MB of RAM. |
|
| Author: | alexfru [ Tue Jan 31, 2017 2:49 am ] |
| Post subject: | Re: Stupid bicycle vs too large solution. |
monobogdan wrote: So, i'm now have only 640kb of ram, and double buffering is too large for it Consider protected mode or unreal mode. |
|
| Author: | dchapiesky [ Tue Jan 31, 2017 3:24 pm ] |
| Post subject: | Re: Stupid bicycle vs too large solution. |
Not intending to be facetious.... but this is how the concept of virtual memory and paging was found to be needed..... I will recommend this one thing though: obviously your problem with graphics has been solved at some point in time in the past... it well worth the effort to research how they did it..... if you become well versed in working with resource constrained systems then that is a marketable skill... good luck and keep at it |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group http://www.phpbb.com/ |
|