From owner-freebsd-ports Wed Nov 20 21: 3: 3 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D43737B401; Wed, 20 Nov 2002 21:03:02 -0800 (PST) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E86043E42; Wed, 20 Nov 2002 21:02:57 -0800 (PST) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from m2a2.yi.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 84C33A3841; Thu, 21 Nov 2002 06:02:55 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id E81D1694D4; Thu, 21 Nov 2002 06:02:51 +0100 (CET) To: Nate Lawson Cc: Kris Kennaway , ports@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: HEADSUP - change in CDRIOC.*SPEED ioctl units References: In-Reply-To: (Nate Lawson's message of "Tue, 19 Nov 2002 18:26:59 -0800 (PST)") From: Matthias Andree Date: Thu, 21 Nov 2002 06:02:51 +0100 Message-ID: User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i586-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Nate Lawson writes: > I have examined many common ports including cdrecord, tosha, dagrab and am > reasonably certain no one is using the CDRIOC*SPEED ioctls outside of > cdcontrol and burncd. Since they are only found in FreeBSD, the only > problem may be a 3rd-party commercial application (if there is one). A > possible workaround would be to specify speed as 177 for 1x, etc. > > The reason this was MFCd is that it is impossible to tell the drive to use > the max speed by sending 0xffff since the kernel was multiplying by 177. > See the PR referenced in the original commit. This limited functionality > in the MMC command set. There are still limitations (only one of READ, > WRITE speed may be set and the other is automatically set to max) but that > would break the API to change. You must be kidding. Let the kernel figure 0xffff is magic and be done, one line of code. No need to make dozens of maintainers change their applications. Why does the application have to deal with raw kB/s rates at all? -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message