From owner-freebsd-current  Mon Dec  6 11:17:34 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id B7E7214FA0; Mon,  6 Dec 1999 11:17:25 -0800 (PST)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id UAA13093;
	Mon, 6 Dec 1999 20:17:06 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199912061917.UAA13093@freebsd.dk>
Subject: Re: ATA driver as the default
In-Reply-To: <19991206064628.G44207@tar.com> from "Richard Seaman, Jr." at "Dec 6, 1999 06:46:28 am"
To: dick@tar.com (Richard Seaman, Jr.)
Date: Mon, 6 Dec 1999 20:17:06 +0100 (CET)
Cc: vallo@matti.ee (Vallo Kallaste),
	obrien@FreeBSD.ORG (David O'Brien), sos@FreeBSD.ORG,
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Richard Seaman, Jr. wrote:
> On Mon, Dec 06, 1999 at 12:19:16PM +0200, Vallo Kallaste wrote:
> 
> > It doesn't know about SiS 5591 PCI IDE controller, the wdc controller
> > knows. I'm speaking about boot messages, nothing else. Furthermore the
> > wdc driver sets up UDMA mode on my UDMA capable disks, ata driver
> > doesn't. It claims that busmastering DMA is supported and sets up WDMA2
> > mode instead, I think it's normal as it currently doesn't know about
> > 5591. The WDMA2 isn't really that bad and otherwise I'm using ata driver
> > quite happily. Just FYI.
> 
> The one time I tried ata with my SiS 5591 board I got PIO, no
> DMA at all.  With wd I get UDMA.  This was about 2-3 weeks ago.

The SiS is supported, depending on how the BIOS sets up the chip
the ata driver will do at max wdma2 transfers.

I hope to have support before 4.0, are you guys willing to test
some patches, they might hose your disks, you have been warned :)

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message