From owner-freebsd-current Thu Oct 5 13:26:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 38B9037B503; Thu, 5 Oct 2000 13:26:22 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA47742; Thu, 5 Oct 2000 22:32:57 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200010052032.WAA47742@freebsd.dk> Subject: Re: ATA DMA support is broken In-Reply-To: from John Baldwin at "Oct 5, 2000 01:07:23 pm" To: jhb@FreeBSD.ORG (John Baldwin) Date: Thu, 5 Oct 2000 22:32:57 +0200 (CEST) Cc: valentin@valcho.net (Valentin Chopov), sos@FreeBSD.ORG, freebsd-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 John Baldwin wrote: > > On 03-Oct-00 Valentin Chopov wrote: > > After last changes ata DMA support is not workind and atapicd is not > > recognized on Toshiba Tecra-8100 (FreeBSD-5.0-CURRENT) > > Yes, I've currently got the last round of ATA commits backed out in > sys/dev/ata on my machine as well. The problem seems to be that the > atapci driver is not attaching the ata child devices. Normal dmesg > output: > > atapci0: port 0x1050-0x105f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > ad0: 17301MB [35152/16/63] at ata0-master UDMA33 > > Bad dmesg output: > > atapci0: port 0x1050-0x105f at device 7.1 on pci0 I fixed this ~20 hours after that commit, blunder on my part, sorry... Use ata-all.c rev 1.73 or later... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message