|
|
 |
Published by Michael Lotz
Click here for more information about this publisher...
|
|
|
Date Posted: |
December 1st, 2005
|
|
|
Last Updated: |
December 1st, 2005
|
|
|
License: |
Freeware |
|
|
Downloads: |
189 total; 1 recently |
|
|
Page Views: |
6,256 total |
|
|
User Rating: |
awaiting 10 votes |
 |
|
Jump to the Downloads section |
|
|
|
About system_time_patch:
The system_time_patch patchs the kernel and libroot of R5 and BONE systems to always use the kernel version of system_time(). This patch is not needed on Dano based systems.
What exactly does it do?
It replaces parts of the BeOS kernel and libroot.so. The new code that is inserted rerouts the userspace system_time() function to the one of the kernel that can be fixed by cpu_fix.
Why would I need this?
You only need this if you have to adjust your CPU frequency after booting your system. For example if you want to use the SpeedStep driver to change the frequency of your CPU at runtime.
But isn't this slow?
Yes, it's slower than the original implementation. This is the price for dynamic CPU clocks under BeOS R5. But the impact on performance should be barely noticable, really.
What else do I need?
You will need a cpu_fix driver above version 1.4. After you changed your CPU frequency, your system will be slower or faster than before and not have correct timings anymore. Use a Terminal to do a "rescan cpu_fix". This should fix the kernel variables for the new CPU frequency.
I've got a Dano based system!
Then you don't need this patch. Dano, unlike BeOS R5, shares the timing factors between kernel and userspace. After they are fixed in the kernel (by cpu_fix) they are reexported to this shared area and also apply for all running applications.
Is it risky to apply this patch?
Yes, it can be risky to apply this patch. Not only are the two most central files in your system altered, but also the communication between the kernel and libroot is changed. This means that if the patch does not work for either of the files, your system will be rendered unbootable.
The patch will only be applied if it finds what it expects. It automatically picks either the Plain R5 or the BONE patch.
What to do if it doesn't work?
For this case you should have a bootable BeOS CD or some other BeOS installation around. From there you can unzip the backupfile in the home directory (/yourpartition/home/system_time_patch_somenumber.zip) and move the kernel_intel back to /yourpartition/beos/system and libroot.so back to /yourpartition/beos/system/lib. This should restore the previous state.
|
|
Like this app? Have questions or comments?
Why not tell the author? Use the "e-mail publisher" link to get in touch with the publisher; they usually love getting feedback.
|
|
|
