Newest Files
 Nov.20
Driver for Broadcom 570x 10/100 Ethernet Driver.
 Nov.16
This is a 650mb raw disk image that will eventually ...
 Nov.12
About Photograbber:
PhotoGrabber ha...
 Nov.11
Driver for Broadcom 440x 10/100 Ethernet Driver.
 Nov.09
This is a 10gb expanding VMWare disk image. I plan t...
 Nov.09
About IPW2100:
Driver for Intel(R) PRO/Wireless...
 Nov.09
Attansic L2 FastEthernet adapter:
Driver for At...
 Nov.09
About Pegasus BeOS Driver:
Pegasus BeOS driver....
 Nov.08
SLFFEA stands for San Le's Free Finite Element Ana...
 Nov.08
Aladdin is a computational toolkit for the interac...
 Oct.28
Qonk is a small space build-and-conquer strategy gam...
 Oct.25
This port is based on the work done by Takashi Toyos...
 Oct.25
These are the icons Haiku comes with converted from ...
 Oct.17
This project was based on the popular weekly superpa...
 Oct.16
The MUSCLE system is a robust, somewhat scalable, cr...
|
- Description:
-

About cpu_fix:
This is the cpu_fix driver that fixes timing and CPU reporting issues
under BeOS R5 with CPUs faster than 2.1GHz.
What can it do for me?
The driver can fix problems with clocks / videos / sounds running too
fast. It can also help you if audio is playing fine, but the ends of
songs are choped off. This is a problem mainly seen with P4 processors.
The reporting fix does patch the kernel so it reports the correct CPU
speed to applications. This is useful on CPUs faster than 2.1GHz (P4s /
Athlons) and fixes the display of negative CPU speeds. This also
resolves the problem with the Media-Preference panel, where you can't
select real-time audio and video because it thinks the system is
running below 200MHz for example.
What version of this driver do I need?
If you run BeOS R5 (with or without BONE) you will need the normal "Binary for R5" version below.
For users of Dano based systems like Dano itself, Zeta and maybe PhOS, take the variation titled "Binary for Dano".
How did this driver get made?
This driver is based on two main sources:
The idea was derived from vwware_timer by François Revol.
The CPU detection routine was taken from the Haiku tree.
For the reporting patch, I was just diving into the kernel to identify
the get_cpu_info function as being the one where the reporting error
comes from. Then I had to refresh my knowledge of assembler to find an
option to correct this error. It was a bit time consuming, but here you
have the result: a mostly working and somewhat kernel independant patch.
How does it work?
If enabled, the driver fixes the cv_factor of the kernel by generating
a correct one with the CPU detection function of the Haiku/NewOS
kernel. The kernel variable holding the cv_factor is simply overwritten
with the new value.
If the reporting patch is enabled, the driver patchs the get_cpu_info
function by overwriting it with a version that handles the 64bit CPU
speed value correctly.
Is it risky to install the driver?
The whole patching actually takes place at runtime and not like with
other kernel patches directly on the binary. The kernel_intel file is
not modified at all.
When the driver is loaded by the kernel, it simply overwrites some bytes in the RAM where the kernel is loaded.
That means it is not really risky to install this driver. If your
system hangs or crashes, you can just select "Disable user add-ons" in
the "Fail safe options" at the bootmenu (hit space as soon as you see
the BeOS booting to get there).
How can I get rid of the driver?
If your system does not boot anymore, see the paragraph above on how to boot into safemode.
To uninstall the driver you can just delete the cpu_fix file in "/boot/home/config/add-ons/kernel/drivers/dev/disk" and reboot.
Details about this version:
Additionally fixes the system_time_base to avoid jumps in time.
- License:
-
BSD/MIT
- Submitted On:
-
27 Dec 2007
- Submitted By:
-
Karl vom Dorff (karl)
- File Date:
-
27 Dec 2007
- File Author:
-
Michael Lotz
- File Version:
-
1.4
- File Size:
-
6.27 Kb
- File Type:
-
zip
- File HomePage:
- Click to visit site
- Downloads:
-
9
- Rating:
-
 Total Votes:0
|
|