| From: | Sam Jordan |
| Date: | 19 Dec 99 at 17:42:51 |
| Subject: | Re: [warpup] Re: other WarpOS problems |
Am 19-Dez-99 schrieb Franck DEROUAULT:
>>> Maybe I'm wrong. It's just an idea.
>>
>You probably are wrong because the CS 233 are not the only cards involved in
>overclocking but are the only that seem to be affected by the LR bug:
>I own a "BPPC" sold as a 603e+ at 160Mhz and in fact if the processor is
>actually rated at 160 Mhz by motorola, PPCtool on the P-UP side return
>175Mhz and PPC Info gives me 176.6 for Warp up.
I don't know exactly what 'PPC info' means here, but the 'showinfo'
tool basically should never give odd values for the clock frequency.
Does it really?
>In fact I have a 50 Mhz crystal and P5 has set the PLL divisor at 3.5X, so
>they have overclocked my card at 175 without niticing it to me.
>But AFAIK, my card doesn't suffer from the LR bug (but how can I detect it)
>and I don't see the reason why a hardware pb (overheating or whatever you
>want) can affect W-OS and not P-UP.
That's easily possible because both software systems have different
architectures. The one architecture might lead to more load on memory/bus/
processor as it is for the other architecture. It might as well be,
that a specific code sequence might trigger such errors, maybe it's
some special sequence of instructions or memory accesses or whatever.
At least everything is possible.
bye