Date: Fri, 30 Apr 2004 22:34:19 -0700 (PDT)
From: Gregg Eshelman <[EMAIL PROTECTED]>
Subject: Re: Daystar Turbo 040/40 - overclocked?
In-Reply-To: <[EMAIL PROTECTED]>
--- Mark Benson <[EMAIL PROTECTED]> wrote:
Looking at John's post and looking again at my
Turbo040 I real
--- Mark Benson <[EMAIL PROTECTED]> wrote:
> Looking at John's post and looking again at my
> Turbo040 I really can't
> see it having been re-soldered. There are a lot of
> SMT components
> around it that have not been so much as even
> disturbed. There are no
> burn marks or signs of heat. If
On Apr 30, 2004, at 05:09 pm, J.S. Garrison wrote:
on 4/30/04 6:53 AM, Mark Benson at [EMAIL PROTECTED] wrote:
I have a turbo040 card in my Performa 600 that I am trying to build
into a Super 68k Nubus machine. It registers in every info tool I've
tried in Mac OS as 40MHz, even in the QuadControl 2
on 4/30/04 6:53 AM, Mark Benson at [EMAIL PROTECTED] wrote:
> I have a turbo040 card in my Performa 600 that I am trying to build
> into a Super 68k Nubus machine. It registers in every info tool I've
> tried in Mac OS as 40MHz, even in the QuadControl 2.2 panel. The CPU is
> clearly a XC68040HRC3
I've got exactly one of those too! I had the same thought, DayStar
where pushing it :-)
The internal cpu clock runs at twice the speed of the external clock.
I've worked in the semiconductor industry for 25 years, and can tell
you that speed "binning" is done this way:
1) Us engineers devise th
I have a turbo040 card in my Performa 600 that I am trying to build
into a Super 68k Nubus machine. It registers in every info tool I've
tried in Mac OS as 40MHz, even in the QuadControl 2.2 panel. The CPU is
clearly a XC68040HRC33M however - a 33MHz chip. The Oscillator can is
20MHz and I have