What's the current Llano APU vantage wr?

[chew*]

Ok what I am going to show today does not apply to current cpu's. This will only work on future unlocked models.

There will be a simple program that will be public most likely in time for or prior to unlocked models being released so don't get your panties in a bunch.........It will be shared with the public.

How it works.

Default multi range is 16x-47x for unlocked parts. If we change something we can shift the multi range, now i'm not 100% sure of the impacts this can have on total platform performance however cpu intensive multithreaded shows no gains or losses.

So to sum up lets call this Mode 0 = 16X-47x.

Mode 1 = 32x-63x (lower than 32X will not be available)

Applying Mode 1 with an already high clock say 3700mhz will result it 16X higher so 3700+ 16X will = 5300 and most certainly a crash. In order to counter this multi should be dropped in K10 to lowest setting so when applied frequency will be 32X = 3200 which just about any LLano cpu can do on air.

Will this be usefull for air users? Not likely unless the process improves drastically.

Will it be usefull for ln2? Yes, it will help find the max limits of cpu without board or ram as part of the equasion.

I have tested k10 stat K10153 version and it works fine. Unfortunately at this time cpu-z does not recognize the shift so I will have to contact frank to see if he can get it working.

I used Wprime to first measure performance at a given clock and also show the speeds are "REAL" not bugged.

First a Base line run at lowest multi 16x Mode 0



Second Base line run at 42X Mode 0



Mode 1 = cpuz reported + 1600mhz As we see the time is cut in half compared to the above 1600mhz run.



Mode 1 = cpuz reported + 1600 mhz As we can see the time is identical to the above run at 4200mhz.

[El Gappo]

Ok what I am going to show today does not apply to current cpu's. This will only work on future unlocked models.

Can you not use it for down-clocking on locked samples? Custom P-states would be nice

[chew*]

Couldn't get any more on air

That score is nothing to be ashamed of alex.

Can you not use it for down-clocking on locked samples? Custom P-states would be nice

The problem with that would be the entire multi range is shifted elgappo from 16-47 to 32-63 and models that don't support upwards multi adjust won't apply. I tried this at ASUS on another ES sample and the old claim ( ES is all unlocked is bullocks ), it didn't work on their chip.

I would imagine with K10 stat you can already do custom pstates however.