From owner-freebsd-hackers  Sun Jan 26 19:48:19 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA14704
          for hackers-outgoing; Sun, 26 Jan 1997 19:48:19 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA14696
          for <freebsd-hackers@freebsd.org>; Sun, 26 Jan 1997 19:48:17 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA04555; Sun, 26 Jan 1997 20:31:08 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199701270331.UAA04555@phaeton.artisoft.com>
Subject: Re: CMD640b ide controller bug workarounds?
To: garman@phs.k12.ar.us
Date: Sun, 26 Jan 1997 20:31:08 -0700 (MST)
Cc: terry@lambert.org, freebsd-hackers@freebsd.org
In-Reply-To: <Mutt.19970126171625.garman@jason.garman.net> from "Jason Garman" at Jan 26, 97 05:16:25 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> And as for L*nux, looking through AltaVista's search results for the query
> you gave me, it seems that L*nux _does_ automatically and
> non-destructively detect and work around the CMD 640b bugs. (no
> hda=serialize needed after all, apparently)
> 
> Detecting a VLB board using this chip would be harder (is it even
> possible)?

Well, for PCI, yes.  For VLB, there's no slot identification data
(which is why, like ISA, it sucks).

If the Linux code is working around the hardware problem, it probably
has code to detect it, which you could examine to determine their
algorithm.


					Regards,
					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.