From owner-freebsd-current@FreeBSD.ORG Sun Aug 2 10:00:15 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5004B1065673 for ; Sun, 2 Aug 2009 10:00:15 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) by mx1.freebsd.org (Postfix) with ESMTP id 24B308FC1B for ; Sun, 2 Aug 2009 10:00:15 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-240-232.hsd1.ms.comcast.net [75.65.240.232]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id B5BA337B54E; Sun, 2 Aug 2009 05:00:12 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id EADA761C41; Sun, 2 Aug 2009 05:00:11 -0500 (CDT) Date: Sun, 2 Aug 2009 05:00:11 -0500 From: "Matthew D. Fuller" To: Joerg Schilling Message-ID: <20090802100011.GB62454@over-yonder.net> References: <4a755d11.YH68jo2T1j3qYokP%Joerg.Schilling@fokus.fraunhofer.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4a755d11.YH68jo2T1j3qYokP%Joerg.Schilling@fokus.fraunhofer.de> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.20-fullermd.4 (2009-06-14) X-Virus-Scanned: clamav-milter 0.95.2 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: RFC: ATA to CAM integration patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Aug 2009 10:00:15 -0000 On Sun, Aug 02, 2009 at 11:32:01AM +0200 I heard the voice of Joerg Schilling, and lo! it spake thus: > > Did someone iomplement a CAM driver that does not support the ioctl > for sending SCSI commands, or do you have different problems? Well, being as the failure is now that I upgraded and am using the CAM AHCI driver, and it worked before [via ATAPICAM], I'm guessing it's the former (hence posting it in the thread on that driver :). Though I guess there's always the chance that other -CURRENT changes since my last (early June) kernel ate it. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.