From owner-freebsd-hackers Fri Sep 1 9: 8:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 07C8537B423; Fri, 1 Sep 2000 09:08:50 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e81G8mN29951; Fri, 1 Sep 2000 18:08:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Soren Schmidt Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Tagged queuing for ATA drives, patches up for testing In-Reply-To: Your message of "Thu, 31 Aug 2000 13:58:46 +0200." <200008311158.NAA75155@freebsd.dk> Date: Fri, 01 Sep 2000 18:08:48 +0200 Message-ID: <29949.967824528@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I've put the latest patches for tagged queueing on ATA disks up >for ftp on: > > ftp://freebsd.dk/pub/ATA/ATA-tagged-queueing-diff-0831.gz On my testmachine: atapci0: port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ad0: 17206MB [34960/16/63] at ata0-master UDMA66 ad1: 14664MB [29795/16/63] at ata1-master tagged UDMA66 If I enable it on ad0, without without enabling it on ad1 it chokes. ad1 seems to be stable. Is there any way to read the firmware rev on ATA disks ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message