From owner-freebsd-current Wed Feb 26 10:56: 5 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3848137B401; Wed, 26 Feb 2003 10:56:04 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44C4A43FA3; Wed, 26 Feb 2003 10:56:03 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.6/8.12.6) with ESMTP id h1QIu1BV023367 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 26 Feb 2003 13:56:02 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h1QItu060918; Wed, 26 Feb 2003 13:55:56 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15965.3516.794342.137264@grasshopper.cs.duke.edu> Date: Wed, 26 Feb 2003 13:55:56 -0500 (EST) To: sos@freebsd.org Cc: current@freebsd.org Subject: UDMA66 vs ATAPI_DEVICE(atadev)? X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Soren, After recent ATA commits, my Promise UDMA66 controller is now running its drives in PIO4 mode. Previously, UDMA66 was working fine. Here's a dmesg snippet: atapci0: port 0xdf00-0xdf3f,0xdfe0-0xdfe3,0xdfa8-0xd faf,0xdfe4-0xdfe7,0xdff0-0xdff7 mem 0xfc8a0000-0xfc8bffff irq 2 at device 2.0 on pci0 ata2: at 0xdff0 on atapci0 ata3: at 0xdfa8 on atapci0 <..> ad4: 19092MB [38792/16/63] at ata2-master PIO4 The controller itself looks like this: atapci0@pci0:2:0: class=0x018000 card=0x4d33105a chip=0x4d38105a rev=0x01 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20262 FastTrak66 EIDE Controller' class = mass storage I've found that I can recover from this problem by forcing ATAPI_DEVICE() to always return 1. It seems to want to return 0 for devices not on the primary ata controller. I'm confused.. What's the point of ATAPI_DEVICE()? Am I not allowed to use extra controllers anymore? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message