From owner-freebsd-current Tue Mar 14 7:54: 5 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 DD1B837B729 for ; Tue, 14 Mar 2000 07:53:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA83093; Tue, 14 Mar 2000 16:53:54 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200003141553.QAA83093@freebsd.dk> Subject: Re: CMD640 and ATA drivers In-Reply-To: from Thomas Veldhouse at "Mar 14, 2000 09:25:27 am" To: veldy@visi.com (Thomas Veldhouse) Date: Tue, 14 Mar 2000 16:53:54 +0100 (CET) Cc: 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 Thomas Veldhouse wrote: > Are there any plans to support the buggy CMD640 interface in the future > now that 4.0-RELEASE has come and gone? I have a box that is running 3.4 > happily, and it has this interface. I really would like the chance to use > some of the 4.0 features, but I can not while support for this interface > lacks. > > Right now, the code does identify the controller and give a warning about > a buggy interface. It then proceeds to choke and die on the CD-ROM probe. > I will gladly post more accurate details (I have already in the past) if > such support will eventually be [re]added. It worked until the latest newbus changes, I'm looking at it, but havn't found anything obvious yet. But seriously you want to get another ATA interface, the CMD640 is _broken_ and no software can help that, you are playing russian roulette with your data. Get a promise, abit or siig controller and use that instead... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message