From owner-freebsd-hardware Thu Aug 17 23:17:56 1995 Return-Path: hardware-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id XAA03135 for hardware-outgoing; Thu, 17 Aug 1995 23:17:56 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id XAA03124 for ; Thu, 17 Aug 1995 23:17:53 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id XAA24364; Thu, 17 Aug 1995 23:16:46 -0700 From: "Rodney W. Grimes" Message-Id: <199508180616.XAA24364@gndrsh.aac.dev.com> Subject: Re: i82424ZX vs i82424TX cache dram controller To: jmb@kryten.Atinc.COM (Jonathan M. Bresler) Date: Thu, 17 Aug 1995 23:16:46 -0700 (PDT) Cc: freebsd-hardware@freebsd.org In-Reply-To: from "Jonathan M. Bresler" at Aug 17, 95 10:56:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1547 Sender: hardware-owner@freebsd.org Precedence: bulk > > On Wed, 16 Aug 1995, Rodney W. Grimes wrote: > > > > ps. the asus sp3g uses: > > > chip0 on pci0:0 > > > chip1 on pci0:2 > > > > You left out a bit of that string, and it is an important part: > > chip0 rev 4 on pci0:0 > > ^^^^^ > > As far as I can assertain rev 0, 1 and 2 are Saturn I, 3 and 4 > > are Saturn II. Since Intel data books do not publish code names, > > it is very hard to figure these things out at times :-(. > > hmm...looking into pcisupport.c, i see that most printf()'s are > #ifdef'ed PROBE_VERBOSE. with PROBE_VERBOSE defined i get: > > pci0: scanning device 0..15, mechanism=2. > chip0 on pci0:0 > CPU: 486DX2 or 486DX4, bus=33MHz, CPU->Memory posting ON > Warning: NO DRAM parity! > Cache: 256KB writethrough, cache clocks=2-1-1-1 > DRAM: page mode code fetch, read and write, memory clocks=X-1-2-1 > CPU->PCI: posting ON, burst mode OFF > PCI->Memory: posting ON > [snip] > chip1 on pci0:2 > [40] 41e23 [50] 0 [54] 4000000 > > > still no rev message--from looking at source that seems to be in > -current and 2.0.5R but not in 2.0R Oopss.. your running old code :-(... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD