From owner-freebsd-current  Sun Apr 20 15:43:15 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA23291
          for current-outgoing; Sun, 20 Apr 1997 15:43:15 -0700 (PDT)
Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23282
          for <freebsd-current@freebsd.org>; Sun, 20 Apr 1997 15:43:12 -0700 (PDT)
Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com (8.8.2/8.8.2) with SMTP id PAA08141; Sun, 20 Apr 1997 15:36:06 -0700 (PDT)
Date: Sun, 20 Apr 1997 15:47:54 -0700 (PDT)
From: Tom Samplonius <tom@uniserve.com>
To: Brian Tao <taob@nbc.netcom.ca>
cc: freebsd-current@freebsd.org
Subject: Re: "Data overrun" with 3.0-SNAP, 2940UW controllers
In-Reply-To: <Pine.GSO.3.95.970420150258.11036T-100000@tor-adm1.nbc.netcom.ca>
Message-ID: <Pine.NEB.3.95.970420154641.11865P-100000@haven.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Sun, 20 Apr 1997, Brian Tao wrote:

> On Sun, 20 Apr 1997, Tom Samplonius wrote:
> > 
> > I don't know where you heard that, but the newest ahc rev has fixed
> > all the problems I had, and several others as well.
> 
>     I've heard lots of grumbling about 2.2 and 2.2.1 in freebsd-scsi,
> which Justin has already fixed.  My original plan was to find an older
> release with stable ahc support, and several people indicated that
> 2.1.6/2.1.7.1 and early 2.2 snapshots seemed to do the trick.

  You should get on the csv-commit-sys list.  The driver in 2.2.1 and
2.1.7.1 are nearly the same (if not identical).  The ahc changes were a
major reason why these releases were made.

Tom