[haiku-development] Re: cpu_clock_speed -- why gone?

  • From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sat, 18 Mar 2017 23:15:45 +0100

Am 18.03.2017 um 22:42 schrieb Pete Goodeve:

Ah, that's the reason...  Seems a little odd, though.  I can understand
CPUs and GPUs having different clocks ,but multiple CPUs running the
same instruction set?  Are there any machines on the market that
have such chips?

The big/little model used in some ARM based cell phones already have CPUs with different clock speeds in a single system.

I did some more experiments with a large canvas, and it looks like
the original ArtPaint scheme is somewhat important.  It nicely
degraded the dynamic bitmap enough to keep things smooth.
[I'm rather in awe of Heikke's expertise, here!]  So I think I'll go
with my current plan of get_BeOS_system_info(...) and assume
the compatibilty interface will stay around.

You should just copy the get_rounded_cpu_speed() function out of the private cpu_type.h header, and use that.
While the BeOS interface will stay around for now, it's not clear yet what happens with binary compatibility after R1; different people have different goals/ideas.

Bye,
   Axel.


Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 03-2017