From owner-freebsd-hackers Sat Aug 10 22:04:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA10148 for hackers-outgoing; Sat, 10 Aug 1996 22:04:21 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA10141 for ; Sat, 10 Aug 1996 22:04:13 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id WAA09575; Sat, 10 Aug 1996 22:03:12 -0700 (PDT) Message-Id: <199608110503.WAA09575@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: compland@ism.com.br (Helio Coelho Jr. - CompuLand Informatica) cc: freebsd-hackers@freebsd.org Subject: Re: EDO Ram In-reply-to: Your message of Sat, 10 Aug 96 20:39:38 -0300. <199608102339.UAA01306@unix1.ism.com.br> Date: Sat, 10 Aug 1996 22:03:12 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I would like to know if there is any probe that I can do to check >with a FreeBSD machine is using EDO RAM or not. > Please e-mail direct to me cause I'm not in the hackers list. You would have to probe the BIOS or the support chipset directly. There are two problems with this. 1) The BIOS has no standard place to store this information, although some BIOS' may store it in a proprietary extended location. And, 2) you would have to first determine which support chipset you had, because they are all slightly (or in some cases, vastly) different, and only some of them will give you the information you're after (and possibly in different ways). So, there is no _easy_ way to do this. You could add code to the kernel startup, where it is probing other hardware values, but it would be messy. You might also be able to write a driver to access this information from the support chipset, but that too would be awkward. Why not just check your BIOS messages at boot time? I would think any decent motherboard would be able to tell you whether it's using EDO RAM or not (my ASUS does). If it doesn't say anything, chances are that 1) it doesn't have EDO RAM installed, or 2) it wouldn't know what EDO was even if you had it. (Remember, a motherboard has to have explicite support for EDO for it to work any different from normal memory.) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. -----------------------------------------------------------------------------