Re: [PATCH] Longhaul - Use information from Longhaul

["Rafał Bilski" <rafalbilski@interia.pl>]

>  > 
>  > I don't know how to explain this properly in English. I will use example.
>  > This is from my Nehemiah:
>  > min f = 433MHz = 6.5 * 66MHz
>  > max f = 999MHz = 7.5 * 133MHz
>  > but this is Nehemiah "C" and it is working downto 4.0 multiplier.
>  > 
>  > This is Ezra that I have found in Google (output from Your program):
>  > min f = 300MHz = 3.0 * 100MHz
>  > max f = 864MHz = 6.5 * 133MHz
> 
> But this is only true IFF we scale the FSB, which we don't.
> The above scenarios will not happen for as long as that is true.

Yes.

> 
>  > I'm trying to be more compatible with information from Longhaul MSR. Even if 
>  > this register is broken for my CPU, using min frequency insteed of min 
>  > multiplier is fixing this.
> 
> when you say 'min frequency', which MSR bits are you talking about?
> 
> 		Dave
> 

I mean that
min frequency = MinMHzFSB * MinMHzBR
of course values from multipliers and fsb tables.

This is big patch, but change I want to do is in this:

 		ratio = clock_ratio[j];
 		if (ratio == -1)
 			continue;
-		if (ratio > maxmult || ratio < minmult)
+		speed = calc_speed(ratio, fsb);
+		if (speed > highest_speed || speed < lowest_speed)
 			continue;
-		longhaul_table[k].frequency = calc_speed(ratio);
+		longhaul_table[k].frequency = speed;

If I would blindly read MinMHzBR for my CPU then minimal multiplier 
would be 6.5, but in fact this processor is capable of 4.0.

Rafa³


------------------------------------------------------------------------
Wyjezdzasz na wakacje? Zaplanuj trase z map24. 
http://map24.interia.pl/