[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug found
- Date: Thu, 11 Jun 2009 11:22:47 +0200
- From: Thomas.Doerfler at embedded-brains.de (Thomas Dörfler)
- Subject: Bug found
Leon,
you are right, the meaning of "clocks_per_usec" may be missleading. But
the bus clock is not the CPU (execution) clock either. Since the 603 has
a CPU internal PLL, the CPU clock is in most cases a (fractional)
multiple of the bus clock. So maybe we should simply add some lines of
comment to the usage of this constant on PPC.
wkr,
Thomas.
Leon Pollak wrote:
> On Tuesday June 9 2009, Thomas D?rfler wrote:
>> Leon,
>>
>> the big question is, what is the definition of "clocks per usec". In
>> your view, this is the bus clock, in the view implemented, it is the
>> Timebase/DEC tick rate directly.
>>
>> Maybe this helps...
> Thomas,
> As all what you say, this definitely helps...:-))
>
> Just, don't you think that the name of the variable is mistaking?
>
> I understand "CPU clocks per usec" as the number of input frequency ticks in
> one micro second.
>
> How one can guess that it should be timebase clock AFTER prescaler?
>
> But many thanks as usual...:-)
--
--------------------------------------------
Embedded Brains GmbH
Thomas Doerfler Obere Lagerstrasse 30
D-82178 Puchheim Germany
email: Thomas.Doerfler at embedded-brains.de
Phone: +49-89-18908079-2
Fax: +49-89-18908079-9
- References:
- Bug found
- From: leonp at plris.com (Leon Pollak)
- Bug found
- From: Thomas.Doerfler at embedded-brains.de (Thomas Dörfler)
- Bug found
- From: leonp at plris.com (Leon Pollak)