From owner-freebsd-hackers@freebsd.org Thu Jan 28 08:53:42 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0017DA71F07 for ; Thu, 28 Jan 2016 08:53:41 +0000 (UTC) (envelope-from nkoch@demig.de) Received: from demig.de (demig.de [81.169.228.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Parallels Panel", Issuer "Parallels Panel" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 498F41EB2 for ; Thu, 28 Jan 2016 08:53:40 +0000 (UTC) (envelope-from nkoch@demig.de) Received: (qmail 18721 invoked from network); 28 Jan 2016 09:45:15 +0100 Received: from b2b-130-180-89-86.unitymedia.biz (HELO firewall.demig.intra) (130.180.89.86) by demig.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 28 Jan 2016 09:45:15 +0100 Received: from SRV-FS-2.Demig.intra (nameserver.demig.intra [192.168.148.248]) by firewall.demig.intra (8.14.4/8.14.4) with ESMTP id u0S8iuBS028950 for ; Thu, 28 Jan 2016 09:44:56 +0100 (CET) (envelope-from nkoch@demig.de) Received: from [192.168.148.83] (192.168.148.83) by SRV-FS-2 (192.168.148.248) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 28 Jan 2016 09:44:50 +0100 From: Norbert Koch Subject: impossible to set pata dma mode? To: X-Enigmail-Draft-Status: N1110 Message-ID: <56A9D502.7010809@demig.de> Date: Thu, 28 Jan 2016 09:44:50 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 192.168.148.235 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2016 08:53:42 -0000 Hello. I have to reduce dma mode from udma to wdma2 for a flash device. In the past this was easy using atacontrol but, afaiks it seems to be impossible using camcontrol. camcontrol negotiate ada0 -M wdma ...You can only modify user parameters camcontrol negotiate ada0 -NM wdma Works, but I see no way how those user parameters become active parameters as the driver only reads then in attach as far as I can see. It seems like the ata driver's interface allows to change the current settings (XPT_SET_TRAN_SETTINGS/CTS_TYPE_CURRENT_SETTINGS) so, why is camcontrol so restrictive? Thank you, Norbert Koch